tursodatabase/turso

In the Github actions workflow, we keep downloading the dist tool all the time, which often results in network timeouts. Let's vendor or cache the dependency instead.

The docs provide two distinct ways of using uuid in tables for a PK. The first is to have a STRICT table with uuid defined as the column type (what I would ideally love to have): https://docs.turso.tech/sql-reference/data-types CREATE TABLE events ( id uuid PRIMARY KEY, name varchar(100), event_date date, is_active boolean DEFAULT 1, metadata json ) STRICT; INSERT INTO events VALUES ( uuid4(), 'Product Launch', '2025-03-15', 1, '{"venue": "online"}' ); This example does not work as of version 0.5.1. I get the following error: Error: Runtime error: cannot store BLOB value in TEXT column events.id (19) The docs also don't state how I would reference this ID as a FK in another table. Would it be BLOB, TEXT or UUID? In the second example in the docs, the table is STRICT and the id PK is typed as BLOB. https://docs.turso.tech/sql-reference/extensions#examples -- Generate UUIDs SELECT uuid4_str(); -- '550e8400-e29b-41d4-a716-446655440000' SELECT uui

Those introduced here: #5254 and #5729. The types are quite rich, support a lot of things. We must ensure vacuum into supports all these. While at it, we must also make sure that vector types work with vacuum into if they work out of the box, lets add tests.

The source db can be either encrypted or non encrypted. If the destination URI mentions encryption params, then it should produce an encrypted db. The tests also should make sure that db hash matches post vacuum. If the source is already encrypted, then we should also that we are able to vacuum into another encrypted db but with different cipher settings. The URI params should be like existing one: ?cipher=aegis256&hexkey=b1bbfda4f589dc9daaf004fe21111e00dc00c98237102f5c7002a5669fc76327

Description PRAGMA table_info strips parenthesized type parameters from column type declarations. SQLite preserves the complete type string exactly as written. Reproducer CREATE TABLE t( a VARCHAR(100), b CHAR(50), c DECIMAL(10,2), d NUMERIC(5,3), e FLOAT(24), f NVARCHAR(200) ); PRAGMA table_info(t); -- Turso type column: VARCHAR, CHAR, DECIMAL, NUMERIC, FLOAT, NVARCHAR -- SQLite type column: VARCHAR(100), CHAR(50), DECIMAL(10,2), NUMERIC(5,3), FLOAT(24), NVARCHAR(200) Per SQLite documentation: the "type" column reports the declared type of the column. The schema parser or column metadata storage strips the parenthesized parameters. This issue brought to you by Mikaël and Claude Code.