mirror of
https://github.com/aljazceru/turso.git
synced 2025-12-25 03:54:21 +01:00
91cff65e44
fixes #1976 and #1605 ```zsh turso> DROP TABLE IF EXISTS t; CREATE TABLE t ( id INTEGER PRIMARY KEY AUTOINCREMENT, name TEXT ); turso> INSERT INTO t (name) VALUES ('A'); SELECT * FROM sqlite_sequence; ┌──────┬─────┐ │ name │ seq │ ├──────┼─────┤ │ t │ 1 │ └──────┴─────┘ turso> DROP TABLE IF EXISTS t; CREATE TABLE t ( id INTEGER PRIMARY KEY AUTOINCREMENT, name TEXT ); turso> INSERT INTO t (name) VALUES ('A'); SELECT * FROM sqlite_sequence; ┌──────┬─────┐ │ name │ seq │ ├──────┼─────┤ │ t │ 1 │ └──────┴─────┘ turso> INSERT INTO t (name) VALUES ('A'); SELECT * FROM sqlite_sequence; ┌──────┬─────┐ │ name │ seq │ ├──────┼─────┤ │ t │ 2 │ └──────┴─────┘ turso> ``` Reviewed-by: Preston Thorpe <preston@turso.tech> Closes #2983
Turso Testing
Testing Extensions
When adding tests for extensions, please follow these guidelines:
- Tests that verify the internal logic or behavior of a particular extension should go into
cli_tests/extensions.py. - Tests that verify how extensions interact with the database engine, such as virtual table handling, should be written
in TCL (see
vtab.testas an example).
To check which extensions are available in TCL, or to add a new one, refer to the tester.tcl file and look at the extension_map.