Skip to content
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

Feature: Add Data Types to Support Postgres Migrations Better #16317

Open
inviscid opened this issue Aug 22, 2024 · 0 comments
Open

Feature: Add Data Types to Support Postgres Migrations Better #16317

inviscid opened this issue Aug 22, 2024 · 0 comments
Labels
C-feature Category: feature

Comments

@inviscid
Copy link

inviscid commented Aug 22, 2024

Support Common Datatypes as Aliases or Real

For the most part, migrating from Postgres based syntax to Databend has been pretty straightforward, however there are three data types that would be ideal to support.

UUID - This could be an Alias of STRING but it would be very helpful to have the dtype return as a UUID rather than STRING
DATE - This differs from TIMESTAMP in that all the time information is dropped
TIME - This also differs from TIMESTAMP by truncating the date information

Why separate DATE and TIME types when TIMESTAMP can hold the information? While we have been able to work around storing DATE and TIME information in a TIMESTAMP field, the problem arises when trying to perform operations (add, subtract, etc...) when the value stored contains extraneous information. Unless the user knows how the underlying data is stored they will get unexpected answers. This is obviously less than ideal.

@inviscid inviscid added the C-feature Category: feature label Aug 22, 2024
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
C-feature Category: feature
Projects
None yet
Development

No branches or pull requests

1 participant