-
Notifications
You must be signed in to change notification settings - Fork 17
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
More PostgreSQL datatypes support #180
Conversation
different drivers (fix #176)
best to review by @wonder-sk |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Great stuff. One thing I am wondering about is how we deal with "numeric" columns - we store them as doubles which provide 15 to 17 significant decimal digits, but what if someone stores a decimal number with 20 digits, and we would be loosing precision? I guess for now it would be OK if that would be a known limitation, I am just wondering if we can/should trigger some warnings in case we do a conversion where this would happen (i.e. not warn if someone uses numeric(50)
with small numbers, only warn with numeric(50)
and numbers with 16+ digits?
I was thinking about converting |
1069606
to
e712064
Compare
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Great, thanks!
Adds support for more PostgreSQL datatypes:
character(N)
andchar(N)
(fixes Error when copying DB to GPKG for datatype character(50) #177)numeric(M, N)
uuid
(fixes Support for UUID data type in postgres driver #157)Avoid datatypes conversion while making copy of the database if source and destitation drivers are the same. This allows to use native datatypes and avoid conversion issues (fixes #176).