Piotr Rzysko 30ae6538ee Treat table-valued functions as tables ...

With this change, the following two queries are considered equivalent:
```sql
SELECT value FROM generate_series(5, 50);
SELECT value FROM generate_series WHERE start = 5 AND stop = 50;
```
Arguments passed in parentheses to the virtual table name are now
matched to hidden columns.

Column references are still not supported as table-valued function
arguments. The only difference is that previously, a query like:
```sql
SELECT one.value, series.value
FROM (SELECT 1 AS value) one, generate_series(one.value, 3) series;
```
would cause a panic. Now, it returns a proper error message instead.

Adding support for column references is more nuanced for two main
reasons:
- We need to ensure that in joins where a TVF depends on other tables,
those other tables are processed first. For example, in:
```sql
SELECT one.value, series.value
FROM generate_series(one.value, 3) series, (SELECT 1 AS value) one;
```
the one table must be processed by the top-level loop, and series must
be nested.
- For outer joins involving TVFs, the arguments must be treated as ON
predicates, not WHERE predicates.

2025-07-14 07:16:53 +02:00

..

dynamic.rs

Rename limbo_ext crate to turso_ext

2025-06-29 12:14:08 +03:00

mod.rs

Treat table-valued functions as tables

2025-07-14 07:16:53 +02:00

vtab_xconnect.rs

make all run_once be run under statement or connection so that rollback is called

2025-07-07 11:51:25 -03:00