mirror of
https://github.com/aljazceru/turso.git
synced 2025-12-25 12:04:21 +01:00
73571d9c55
fixes #3231 ```zsh ❯ sqlite3 SQLite version 3.50.4 2025-07-30 19:33:53 Enter ".help" for usage hints. Connected to a transient in-memory database. Use ".open FILENAME" to reopen on a persistent database. sqlite> CREATE TABLE t1 (a); ALTER TABLE t1 ADD COLUMN a; Parse error: duplicate column name: a sqlite> ALTER TABLE t1 ADD COLUMN name varchar(255); SELECT sql FROM sqlite_schema WHERE name = 't1'; CREATE TABLE t1 (a, name varchar(255)) sqlite> ``` ```zsh turso> turso> CREATE TABLE t1 (a); ALTER TABLE t1 ADD COLUMN a; x Parse error: duplicate column name: a turso> ALTER TABLE t1 ADD COLUMN name varchar(255); SELECT sql FROM sqlite_schema WHERE name = 't1'; ┌─────────────────────────────────────────┐ │ sql │ ├─────────────────────────────────────────┤ │ CREATE TABLE t1 (a, name varchar (255)) │ └─────────────────────────────────────────┘ turso> ``` Reviewed-by: Pere Diaz Bou <pere-altea@homail.com> Closes #3249
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.