Phillip Cloud
Phillip Cloud
@ams1 Thanks for opening an issue! I remember during my graduate school days being incredibly fond of column multiindexes and their ability to allow convenient and fast subsetting for commonly-subsetted...
@ams1 Thanks again for opening this issue! I'm going to close it out for now given that we're unlikely to implement this anytime soon. Keep 'em coming!
Google is maintaining enterprise backends here: https://github.com/GoogleCloudPlatform/professional-services-data-validator/tree/develop/third_party/ibis one of which is a Snowflake backend. There's an exciting Pandora's Box of logistics here: 1. Should these backends be part of `ibis-project`?...
You can now use `con.create_table('my_table', ibis.memtable(rows))` to do this.
This might be a thing that we defer to backends. Some backends let you compare naive and non-naive timestamps.
This can probably be done with a new `rlz` rule, like `if_is_timestamp_both_are_the_same_timezone_awarenessness`
@webmiche Regarding maximum precision/scale, I think the best place for that is https://github.com/ibis-project/ibis/blob/master/ibis/expr/datatypes/core.py#L443 (the `largest` property). The existing logic is designed to support systems that allow arbitrary precision (I believe...
We can ignore the failing coverage check in this case. > Looks quite involved to solve comprehensively... Indeed. This PR is a huge improvement over what was there before so...
@webmiche Thanks for the thoughts. I agree that keeping scale around will likely lead to a better ux than dropping it entirely.