mkleinbort-wl

This would be nice.

explain_plan() without where clause: ``` ProjectionExec: expr=[_companyid@0 as _companyid] GlobalLimitExec: skip=0, fetch=100 LanceRead: uri=lancedb/tb_company_reference_for_entity_search_v1.lance/data, projection=[_companyid, _companyname], num_fragments=1, range_before=None, range_after=None, row_id=true, row_addr=false, full_filter=_companyname = LargeUtf8("Apple"), refine_filter=_companyname = LargeUtf8("Apple") ``` explain_plan() with...

Separately... it looks like .where() is modifying the query in-place - I would say this is not desirable: ```python s:LanceEmptyQueryBuilder = ... print(s.explain_plan()) print(s.where('_companyid!=0').explain_plan()) print(s.explain_plan()) ``` Results in: ```raw ProjectionExec:...

For completeness, the table has indices - the relevant ones being: ```python [ Index(FTS, columns=["_companyname"], name="_companyname_idx"), Index(BTree, columns=["_companyid"], name="_companyid_idx"), ] ```

Found the issue... the query (`s` in my example already had a where clause) My problem was that I was effectively doing: ```python tb.search(...).where(''' text = 'aa zz' ''').where(''' text...

Also, this "only-one-predicate" behaviour is not documented [here](https://lancedb.github.io/lancedb/sql/#sql-filters) nor [here](https://lancedb.github.io/lancedb/js/classes/Query/#where).

It's a valid challenge, and I admit the main driver is that we use `.pipe` pattern constantly, and it was a surprise that it was missing from `LanceTable`. We could...

Thank you, I was on an old version of Polars and had not noticed. Adding it to the eager methods would be nice.

Yes, that was the question. I'll have a look - if Descope can redirect to the right IdP based on a user's email, that'd solve the problem. There's a question...

I'm on: polars = `1.32.3` lancedb = `0.25.0` pylance (lance) = `0.35.0`