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

..

dialect

Fixed blog_literal function to make it return UnrecognisedToken error.

2025-01-19 06:11:45 +05:30

lexer

sqlite3-parser: Remove scanner trace-logging

2025-05-22 12:37:28 +03:00

parser

Fix ProgramBuilder::cursor_ref not having unique keys

2025-05-29 00:59:24 +03:00

lib.rs

vendor sqlite3-parser (lemon-rs)

2024-11-16 20:08:59 +02:00