klaerik

We've experienced this issue too with connector-x. More complex queries might fully execute during the `limit 1` step if they contain a lot of CTEs/aggregations/etc. and the database can't push...

The behavior does depend on whether or not the Class is instantiated, but I don't see that there is a way to get _both_ the commands (methods) and flags (arguments)...

Ran into this issue and was able to work around it with some line exclusions. Beyond the hash fields there's also the need to exclude the base64-encoded images and ids....

The non-duplex version of the 2240 also works. ```bash $ sudo lpinfo --include-schemes usb -l -v | sed 's/serial=.*$/serial=XXXXXXX/' Device: uri = usb://Brother/HL-2240%20series?serial=XXXXXXX class = direct info = Brother HL-2240...

I was using `0.3.1` and didn't see this behavior, so it is something new with `0.3.2`. It's an issue with `arrow2` and `polars` output. This seems similar to the issue...

Looking into this a little further, it appears that this was already an issue in earlier versions with timestamp fields - nanosecond precision failing for large/small dates. It was just...

We're seeing this too with connectorx to Pandas return type. The returned dataframe includes the default Pandas datetime precision: `datetime64[ns]`, which is not capable of expressing a date in the...

After some more research, the issue with nanosecond precision affects all timestamps in connectorx. We just weren't seeing it due to conversion of Oracle DATE datatypes, which are really timestamps,...