mirror of
https://github.com/aljazceru/turso.git
synced 2025-12-24 03:34:18 +01:00
bcafb288ad
turso: ```sh turso> CREATE TABLE t (x PRIMARY KEY, y, z); turso> INSERT INTO t VALUES (37, -70, -196792117); turso> SELECT * FROM t WHERE (1 / 0) >= -3289742039 < t.x; ┌────┬─────┬────────────┐ │ x │ y │ z │ ├────┼─────┼────────────┤ │ 37 │ -70 │ -196792117 │ └────┴─────┴────────────┘ turso> ``` sqlite: ```sh sqlite> CREATE TABLE t (x PRIMARY KEY, y, z); sqlite> INSERT INTO t VALUES (37, -70, -196792117); sqlite> SELECT * FROM t WHERE (1 / 0) >= -3289742039 < t.x; sqlite> ``` related: https://github.com/tursodatabase/turso/actions/runs/17765571409 /job/50488042583?pr=3147#step:8:855 Reviewed-by: Jussi Saurio <jussi.saurio@gmail.com> Reviewed-by: Preston Thorpe <preston@turso.tech> Closes #3167
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.