You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
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:
Ensure appropriate C++'ified definitions of these types are available.
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?
The text was updated successfully, but these errors were encountered:
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:
Notes:
mtime.h
andmtime.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?The text was updated successfully, but these errors were encountered: