Files
turso/testing
themixednuts b6e64587cb fix: jsonb functions to check if binary is json string
chore: match sqlite error

chore: use existing slice variable

add better parsing logic, and validation

see sqlite source code @ sqlite/src/json.c -> static int jsonArgIsJsonb

chore: clippy
2025-09-01 19:52:57 -05: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-08-29 20:58:43 -04:00
2025-07-24 19:19:48 -05:00
2025-02-09 22:01:33 +04:00
2025-01-19 00:39:10 +05:30
2025-01-21 00:29:23 +05:30
2025-08-01 15:44:56 +03:00
2025-08-05 21:18:52 -07:00
2025-06-20 15:59:03 -03:00
2025-08-01 15:44:56 +03:00
2025-06-11 18:39:06 +02:00
2025-08-26 09:21:58 +03:00
2025-05-08 22:22:55 +08:00
2025-09-01 11:39:43 -04:00
2025-08-28 09:49:55 +02:00
2025-08-11 12:13:47 -04:00
2025-08-01 15:44:56 +03:00
2025-02-04 21:02:51 +05:30
2025-08-01 15:44:56 +03:00
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-08-21 16:31:12 +03:00
2025-07-18 10:39:02 -05:00
2025-08-13 14:14:03 -05:00
2025-08-15 21:06:30 +02:00
2025-08-01 15:44:56 +03: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.