You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
The problem for timestamp still exists, in #95 (comment)@son-phamngoc recommends me exclude code about timestamp from that PR as a code not about UUID and as untested line.
Column option
column_type
exists fortimestamp
anduuid
PostgreSQL data types where there is some mixed affinity support.SQLite, SQL
CREATE TABLE (i int, t timestamp);
PosgtreSQL, foreign table with key
i
and timestampt
withcolumn_type
=int
.Near
sqlite_fdw/deparse.c
Line 2373 in d6387a8
constant expressions always deparsed by default algorithm. For
timestamp
this istext
affinity value. Seesqlite_fdw/deparse.c
Line 2576 in d6387a8
But in
UPDATE
context there is nocomplementarynode
or something similarsqlite_fdw/deparse.c
Line 2652 in d6387a8
With UUID support in my PR there is similar tested problem after
sqlite_fdw/expected/12.15/type.out
Line 805 in d6387a8
sqlite_fdw/expected/12.15/type.out
Line 813 in d6387a8
My solution:
strftime
if we needinteger
affinitycolumn_type
option and PostgreSQL data type for updatable attribute of foreign table.Corresponding PR yet drafted and planned after
bit/varbit
support,bool
mixed affinity support andfloat
mixed affinity support.The text was updated successfully, but these errors were encountered: