TIMESTAMP parameters dropped for PostgreSQL
Description
Environment
PostgreSQL (any version)
Activity
Show:
Nathan Voxland June 19, 2015 at 9:52 PM
This has been resolved in 3.4.0
Fixed
Details
Details
Reporter
Former user
Former user(Deactivated)Components
Fix versions
Priority
Created February 4, 2015 at 11:26 PM
Updated June 19, 2015 at 9:52 PM
Resolved June 19, 2015 at 9:52 PM
When specifying a column data type like "TIMESTAMP(3)", liquibase converts it internally into "TIMESTAMP WITHOUT TIME ZONE", dropping the precision parameter.
This leads to problems when OR-Mappers try to figure out how to round timestamp values containing higher precision for correct query values.