mirror of
https://github.com/dimitri/pgloader.git
synced 2025-08-07 23:07:00 +02:00
When merging catalogs, "float" and "double precision" the same type.
PostgreSQL understands both spellings of the data type name and implements float as being a double precision value, so we should refrain from any warning about that non-discrepency when doing a data-only load. Should fix #746.
This commit is contained in:
parent
67a1b1d408
commit
5e3acbb462
@ -117,14 +117,18 @@
|
||||
(column-name source-column)
|
||||
(column-type-name source-column)
|
||||
(column-type-name target-column)
|
||||
(schema-name (table-schema target-table))
|
||||
(table-name target-table)
|
||||
(column-name target-column))))))
|
||||
(ensure-unquoted
|
||||
(schema-name (table-schema target-table)))
|
||||
(ensure-unquoted
|
||||
(table-name target-table))
|
||||
(ensure-unquoted
|
||||
(column-name target-column)))))))
|
||||
|
||||
(defvar *type-name-mapping*
|
||||
'(("int" "integer")
|
||||
("serial" "integer")
|
||||
("bigserial" "bigint")
|
||||
("float" "double precision")
|
||||
("char" "character")
|
||||
("varchar" "character varying")
|
||||
("timestamp" "timestamp without time zone")
|
||||
|
Loading…
Reference in New Issue
Block a user