Files
turso/testing
Jussi Saurio 4e6f373e3d Merge 'Fix: Evaluating expression in LIMIT and OFFSET clauses.' from
Closes #3687 .
Previously, the `try_fold_expr_to_i64` function casted `NULL` as `0`
when evaluating expressions in `LIMIT` or `OFFSET` clauses. I removed
this function since evaluating the expression directly and relying on
the MustBeInt operation for casting seems to handle everything.

Closes #3695
2025-10-15 10:36:36 +03:00
..
2025-09-29 22:33:39 -03:00
2025-08-02 13:00:18 +03:00
2025-07-15 16:44:11 +03:00
2024-08-03 12:16:34 +03:00
2025-09-28 21:16:33 +05:30
2025-10-12 15:58:10 +05:30
2025-10-15 08:51:27 +03:00
2025-02-09 22:01:33 +04:00
2025-10-02 21:49:33 +03:00
2025-01-21 00:29:23 +05:30
2025-10-12 16:38:12 +05:30
2025-08-01 15:44:56 +03:00
2025-08-05 21:18:52 -07:00
2025-10-11 21:39:46 -04:00
2025-06-20 15:59:03 -03:00
2025-06-11 18:39:06 +02:00
2025-09-23 14:22:02 -04:00
2025-05-08 22:22:55 +08:00
2025-09-17 14:50:15 +07:00
2025-09-01 11:39:43 -04:00
2025-10-15 09:41:44 +03:00
2025-08-11 12:13:47 -04:00
2025-08-01 15:44:56 +03:00
2025-10-12 22:23:04 +05:30
2025-08-01 15:44:56 +03:00
2025-08-11 08:42:08 -03:00
2025-06-07 17:37:36 +09:00
2025-09-30 22:39:55 +04:00
2025-10-13 16:14:29 -03:00
2025-10-01 02:12:21 +07:00
2025-08-15 21:06:30 +02:00
2025-09-13 11:12:44 +02:00

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.test as 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.