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

Improve "native" support for date and other date/time types #3

Open
eyalroz opened this issue Jul 9, 2019 · 0 comments
Open

Improve "native" support for date and other date/time types #3

eyalroz opened this issue Jul 9, 2019 · 0 comments
Labels
enhancement New feature or request

Comments

@eyalroz
Copy link
Owner

eyalroz commented Jul 9, 2019

We currently support, in principle, two of MonetDB's date/time-related types: "date" and "daytime"; but even that's limited; we're not even dumping these values reasonably in our example program.

We should:

  1. Ensure appropriate C++'ified definitions of these types are available.
  2. Add support for the "timestamp" and "tzone" types.

Notes:

  • For "date" specifically, values are represented as days since the epoch, which is Jan 1st in year -5867411, and skipping year 0 (yes, a little weird).
  • There's a bunch of code we can use in mtime.h and mtime.c which are already part of the repository.

Question: Should we create proxies for / provide makers of std::chrono types, or just provide our own custom types and let the user worry about conversion?

@eyalroz eyalroz added the enhancement New feature or request label Jul 9, 2019
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
enhancement New feature or request
Projects
None yet
Development

No branches or pull requests

1 participant