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
When using data only, create no tables to populate a schema built with schema only, PGLoader emits warnings about the float data type:
2018-02-15T21:53:22.319000Z WARNING Source column "raw_mysql"."matches"."probability" is casted to type "float" which is not the same as "double precision", the type of current target database column "\"raw_mysql\""."\"matches\""."probability".
I was able to silence this warning by adding type float to "double precision" drop typemod to my command.
PostgreSQL also supports the SQL-standard notations float and float(p) for specifying inexact numeric types... float with no precision specified is taken to mean double precision.
There's another facility in pgloader source code that knows some of the type name mappings in between different spellings of the same thing. I've added float and double precision as synonyms on that list, so you shouldn't have a warning anymore.
When using
data only, create no tables
to populate a schema built withschema only
, PGLoader emits warnings about the float data type:I was able to silence this warning by adding
type float to "double precision" drop typemod
to my command.Since PostgreSQL treats these identically:
it seems to me this default rule:
should instead be:
The text was updated successfully, but these errors were encountered: