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
I'd be fine with literally just "yyyy-mm-dd" format. I am only running into this in testing, when constructing literals. If someone else has real data they are working with, I think it wouldn't be too much to expect them to either format it that way, or convert it to a numpy datetime or a python datetime or something less ambiguous.
Related to this, but I think worth thinking about, is ideally I want to be able to create all ibis datatypes without needing to import anything. eg using the same logic as used in ibis.date(str), etc:
importibisibis.memtable(
{
"uuid": ["9ff13914-a718-48b3-a746-5114cff95d56"],
# "uuid": [1234], # would be awesome to specify as an int too# "date": ["1970-01-01"], # currently errors# "time": ["12:34:56"], # currently errors# "timestamp": ["2023-01-02T03:04:05"], # currently errors
},
schema={
"uuid": "uuid",
# "date": "date",# "time": "time",# "timestamp": "timestamp",
},
).cache().execute()
Removing the bug label. This isn't broken functionality, it's a feature request for specific new behavior.
cpcloud
added
bug
Incorrect behavior inside of ibis
feature
Features or general enhancements
and removed
bug
Incorrect behavior inside of ibis
labels
Jun 2, 2024
cpcloud
changed the title
bug: memtable(..."1970-01-01"..., schema="date") errors
feat(memtable): handle castable inputs from date-like strings to date
Jun 2, 2024
What happened?
What version of ibis are you using?
main
What backend(s) are you using, if any?
duckdb
Relevant log output
No response
Code of Conduct
The text was updated successfully, but these errors were encountered: