Phillip Cloud
Phillip Cloud
Schema information generally can't be made static in Python. A type checker would need access to information from a running database.
It sounds like you effectively want every type-specific method to exist on `Column`. Is that correct?
In that case a giant `ir.StringColumn | ir.IntegerColum | ...` with every single column subclass as the return value of `Table.__getattr__` would probably suffice for this specific use case. If...
> eg if/after that lands It's been merged into `main`! > our type system doesn't currently allow us to be more specific That is by design. `ir.IntegerColumn` is an implementation...
> Are you sure? Yes. By implementation detail here, I mean that we don't expose those objects as inputs to expression APIs. Casting is an in-database operation, and our backends...
@juraj-juraj Sorry for the delay! Would you mind adding a test case, or describing it here if you don't want to do that?
Ok, I can take a look at the failures.
Ok, I got the tests passing, but I think the rules are incorrect. The rewrite should only apply to `pyi` files, whereas now the patterns apply to every file.
@juraj-juraj can you paste here the following: 1. a proto file you used to trigger the bug 2. the codegen command you ran, e.g., buf/protoc/grpc_tools.protoc invocation 3. the `protol` invocation...
To do this, we'd have to encode the logic of every backend's identifier casing rules inside of Ibis. DuckDB for some reason has decided on this--in my opinion--extremely confusing hybrid...