Files
turso/core
Jussi Saurio 77ce4780d9 Fix ProgramBuilder::cursor_ref not having unique keys
Currently we have this:

program.alloc_cursor_id(Option<String>, CursorType)`

where the String is the table's name or alias ('users' or 'u' in
the query).

This is problematic because this can happen:

`SELECT * FROM t WHERE EXISTS (SELECT * FROM t)`

There are two cursors, both with identifier 't'. This causes a bug
where the program will use the same cursor for both the main query
and the subquery, since they are keyed by 't'.

Instead introduce `CursorKey`, which is a combination of:

1. `TableInternalId`, and
2. index name (Option<String> -- in case of index cursors.

This should provide key uniqueness for cursors:

`SELECT * FROM t WHERE EXISTS (SELECT * FROM t)`

here the first 't' will have a different `TableInternalId` than the
second `t`, so there is no clash.
2025-05-29 00:59:24 +03:00
..
2025-05-23 12:37:03 -03:00
2025-05-15 09:59:46 +03:00
2025-05-15 09:59:46 +03:00
2025-03-25 17:13:31 +02:00
2025-04-23 08:34:58 -03:00
2025-05-15 09:59:46 +03:00
2025-01-28 14:55:38 -05:00
2025-05-23 01:32:16 -03:00
2025-04-24 11:05:21 +03:00
2025-01-28 14:55:38 -05:00
2025-05-28 15:54:28 +02:00
2025-05-15 09:59:46 +03:00
wip
2025-03-29 22:02:49 +01:00
2024-12-24 18:04:30 +01:00
2025-05-29 00:22:38 +05:30
2025-05-28 00:33:41 +08:00