PostgreSQL DATETIME type mapping change
Conversion of DATETIME type with fractional seconds to PostgreSQL TIME(N)/TIMESTAMP(N) was invalid and has been reviewed.
Before Genero 3.00, the PostgreSQL driver converted DATETIME types as
follows:
- DATETIME HOUR TO MINUTEwas converted to- TIMESTAMP(3) WITHOUT TIME ZONE
- DATETIME HOUR TO SECONDwas converted to- TIME(0) WITHOUT TIME ZONE
- DATETIME HOUR TO FRACTION(n)was converted to- TIME(n+1) WITHOUT TIME ZONE
- DATETIME YEAR TO MINUTEwas converted to- TIMESTAMP(3) WITHOUT TIME ZONE
- DATETIME YEAR TO SECONDwas converted to- TIMESTAMP(3) WITHOUT TIME ZONE
- DATETIME YEAR TO FRACTION(n)was converted to- TIMESTAMP(n+1) WITHOUT TIME ZONE
Starting with Genero 3.00, when creating a table in a BDL program with CREATE TABLE, the types are converted in a different way:
- DATETIME HOUR TO MINUTEis converted to- TIME(0) WITHOUT TIME ZONE(seconds set to 00).
- DATETIME HOUR TO SECONDis converted to- TIME(0) WITHOUT TIME ZONE.
- DATETIME HOUR TO FRACTION(n)is converted to- TIME(n) WITHOUT TIME ZONE.
- DATETIME YEAR TO MINUTEis converted to- TIMESTAMP(0) WITHOUT TIME ZONE(seconds set to 00).
- DATETIME YEAR TO SECONDis converted to- TIMESTAMP(0) WITHOUT TIME ZONE.
- DATETIME YEAR TO FRACTION(n)is converted to- TIMESTAMP(n) WITHOUT TIME ZONE.
This bug fix introduces an incompatibility and can have an impact on applications using
DATETIME HOUR TO MINUTE, DATETIME HOUR TO FRACTION(n) or
DATETIME YEAR TO FRACTION(n). If you are using one of these types, consider
reviewing your database schema, to modify the column types according to the new SQL type conversion
rules.