Hey there, just wondering, for highly relational data, how does 10GB size limit make sense? How do p
Hey there, just wondering, for highly relational data, how does 10GB size limit make sense? How do production apps go around that?


D1_ERROR ?
TIMESTAMP is supported?

A column with NUMERIC affinity may contain values using all five storage classes. When text data is inserted into a NUMERIC column, the storage class of the text is converted to INTEGER or REAL (in order of preference) if the text is a well-formed integer or real literal, respectively. If the TEXT value is a well-formed integer literal that is too large to fit in a 64-bit signed integer, it is converted to REAL. For conversions between TEXT and REAL storage classes, only the first 15 significant decimal digits of the number are preserved. If the TEXT value is not a well-formed integer or real literal, then the value is stored as TEXT. For the purposes of this paragraph, hexadecimal integer literals are not considered well-formed and are stored as TEXT. (This is done for historical compatibility with versions of SQLite prior to version 3.8.6 2014-08-15 where hexadecimal integer literals were first introduced into SQLite.) If a floating point value that can be represented exactly as an integer is inserted into a column with NUMERIC affinity, the value is converted into an integer. No attempt is made to convert NULL or BLOB values.a bit messy. There's implicit conversion everywhere so you can get away with a lot


04a58760-3751-4337-bb3f-29a671a98cdd and the worker still connected to it is tiles-dev in our account, specifically deployment 76803c37.D1_ERRORTIMESTAMPCREATE TABLE users(
key TEXT UNIQUE PRIMARY KEY NOT NULL, -- Long Hex String (182 chars)
name TEXT NOT NULL,
role TEXT NOT NULL DEFAULT 'none',
created_at TIMESTAMP DEFAULT CURRENT_TIMESTAMP,
updated_at TIMESTAMP DEFAULT CURRENT_TIMESTAMP
) WITHOUT ROWIDUPDATE "main"."users" SET "role" = 'none' WHERE "key" = '<ID>' RETURNING rowid, *04a58760-3751-4337-bb3f-29a671a98cddtiles-dev76803c37