-
Schema mapping database value type “date” to wrong data type
Hello everyone.
I created a schema by dragging and dropping a table from my database. All values matched perfectly except the “date” type, which is automatically mapped to a “Character length 10” type (but “datetime” works fine). I manually mapped the data type to “Date Time Short date 1980…2079” in the schema. Despite this, when using list.$definefromsqlclass or a select statement, the “date” type will still be fetched as a “Character length 10” type…
Does anyone know the solution to this problem? Thanks in advance.
Minh Phuong
-
1 Reply
-
Dear Minh Phuong,
I recently had a mis-mapping between a Postgres Servertable and an Omnis Schema on the primary key property.
I don’t know if it was a problem of the Postgres-DAM or of Postgres itself. But when I recreated the Postgres Object (via PGAdmin), in this case the table, the mis-mapping stopped, and primary was primary on both sides.
This is only a workaround, but it could help you to isolate the problem.
Best regards
Uwe
-
This reply was modified 1 year, 3 months ago by Uwe Smidt.
-
This reply was modified 1 year, 3 months ago by
Log in to reply.
