Unintended external_term.start_date and end_date data type change in SQLServer
Description
Also affects 2.7.0 and 2.4.3, which are unreleased, so by convention aren't listed above.
The problem is with i000062.xml which in https://apereo.atlassian.net/browse/SSP-2847#icft=SSP-2847 added a not-null constraint to external_term.start_date and end_date but specified the wrong data type, which changed the column from a date to a datetime. This only appears to have affected SQLServer. The application appears to be able to survive this change, but it can have severe consequences for external data ETL jobs.
Also affects 2.7.0 and 2.4.3, which are unreleased, so by convention aren't listed above.
The problem is with
i000062.xmlwhich in https://apereo.atlassian.net/browse/SSP-2847#icft=SSP-2847 added a not-null constraint toexternal_term.start_dateandend_datebut specified the wrong data type, which changed the column from adateto adatetime. This only appears to have affected SQLServer. The application appears to be able to survive this change, but it can have severe consequences for external data ETL jobs.