We read every piece of feedback, and take your input very seriously.
To see all available qualifiers, see our documentation.
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
amadeus-types has three goals:
amadeus-types
DateTime
Value
List<Value>
Vec<u8>
Value::U8
List<Row>
Vec<_>
What other data types are relevant?
Should amadeus_core::file::{PathBuf, OsString} be moved to amadeus-types?
amadeus_core::file::{PathBuf, OsString}
The text was updated successfully, but these errors were encountered:
No branches or pull requests
amadeus-types
has three goals:DateTime
can accept any valid Parquet, Postgres timestamp, while remaining losslessValue
enables dynamic and gradual data typing by not requiring the complete type at compile timeList<Value>
is optimised to be backed byVec<u8>
if all the value areValue::U8
List<Row>
is optimised to be backed by aVec<_>
of each column – i.e. columnar, like Apache ArrowWhat other data types are relevant?
Should
amadeus_core::file::{PathBuf, OsString}
be moved toamadeus-types
?The text was updated successfully, but these errors were encountered: