Repository navigation
data-table-sqlite v1.1.0
Minor Changes
-
Query builder results now decode values SQLite stores in another form:
json()columns are parsed withJSON.parse(),boolean()columns read astrueorfalseinstead of1or0, andtimestamp()columns stored in SQLite'scurrent_timestampformat, with optional milliseconds, read asDateobjects. Timestamp text in another format and text in ajson()column that is not valid JSON are returned unchanged, anddb.exec()results keep the stored values. Code that compared these columns against1,0, or JSON text should compare against the decoded values instead. (#12337)let settings = await db.query(userSettings).find(userId) -if (settings.enabled === 1) applyTheme(JSON.parse(settings.data)) +if (settings.enabled) applyTheme(settings.data)
Patch Changes
-
Bind
Dateand boolean parameters consistently. Previously, aDatein the first parameter position was read as a named-bindings object in Node.js, shifting the remaining values, and aDateanywhere else failed, which broketimestampcolumn writes, including the defaultcreated_atandupdated_atvalues. Dates are now bound as UTC strings in SQLite'scurrent_timestampformat, such as'2026-06-01 12:00:00'(with milliseconds only when they are nonzero), and booleans in rawsqlstatements are bound as1or0like query builder values. Invalid dates are rejected. (#12335)Object and array parameters other than typed arrays are now rejected in both Node.js and Bun. In Bun, an object parameter was previously read as a set of named bindings; pass each value positionally instead.
-
Bumped
@remix-run/*dependencies: