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.

Sign up for GitHub

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

Jump to bottom

Should we use the ENUM type from DuckDB for the asset type? #717

Open
Tracked by #701
datejada opened this issue Jul 31, 2024 · 0 comments
Open
Tracked by #701

Should we use the ENUM type from DuckDB for the asset type? #717

datejada opened this issue Jul 31, 2024 · 0 comments
Labels
Type: improvement Better way of doing something Zone: data & import Interfacing between database and Julia

Comments

@datejada
Copy link
Member

What and Why

Read more here:
https://duckdb.org/docs/sql/data_types/enum.html

Possible Drawbacks

No response

Related Issues

No response
@datejada datejada added Type: improvement Better way of doing something Zone: data & import Interfacing between database and Julia labels Jul 31, 2024
@abelsiqueira abelsiqueira mentioned this issue Aug 5, 2024
Closed
3 tasks
@datejada datejada mentioned this issue Aug 12, 2024
Open
52 tasks
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Assignees
No one assigned
Labels
Type: improvement Better way of doing something Zone: data & import Interfacing between database and Julia
Projects
None yet
Milestone
No milestone
Development

No branches or pull requests
1 participant
@datejada