SQLite vs Supabase

Export SQL Results to CSV and Excel Safely

A technical how-to showing how to export SQL query results to CSV or XLSX without corrupting values (leading zeros, accented characters, dates). The author demonstrates that CSV exports preserve bytes but that damage usually occurs when Excel guesses column types on open. Recommended practices include opening CSVs in Excel via Data → Get Data → From Text/CSV (set File Origin to UTF-8 and mark code columns as Text), adding a UTF-8 byte order mark (BOM) on export (e.g., sqlite3 .once --bom) to avoid accent issues, and generating real .xlsx files (e.g., with pandas.to_excel) when humans will double-click the file. The article also lists quick checks to run after export (row counts, code endpoints, an accent, a date) and details other common CSV pitfalls.

• The author tested exports on 2026-08-08 using SQLite 3.51.1 and inspected files byte-by-byte to show exports themselves are correct.
• Opening a CSV by double-clicking in Excel can silently change data types (e.g., drop leading zeros or mis-interpret character encoding), while importing via Data → Get Data → From Text/CSV lets the user set types and encoding.
• Adding a UTF-8 byte order mark (BOM) at file start (sqlite3 .once --bom results.csv) signals encoding to Excel and prevents accented-character corruption.

Trelix v3.0: Six opt-in features, audit trail added

The article documents trelix releases from v2.11.0 through v3.1.1 (last dated 2026-08-15). v3.0.0 introduced six major, opt-in feature areas: Anthropic extended thinking, a model-aware context token budget, a VS Code extension, a hash-chained append-only SQLite audit trail, OIDC SSO (resource-server mode), and query-conditioned context compression, plus an optional FTS5 declaration boost. Defaults keep all features off so a default v3.0.0 install is byte-identical to v2.12.0. v3.0.1 fixed a parser index bug and requires a full reindex; v3.1.0 and v3.1.1 addressed rendering, symlink handling and safety fixes. The audit trail is a separate opt-in SQLite DB with tamper-evident checks, and the OIDC verifier enforces asymmetric algorithms and forged-token tests.

• v3.0.0 introduces six new, opt-in feature areas: Anthropic extended thinking, model-aware context budget, VS Code extension, hash-chained append-only audit trail, OIDC SSO, and query-conditioned context compression.
• The release span v2.11.0 → v3.1.1 comprises 68 commits, 137 files changed, and +19,829/-1,211 lines; v3.1.1 dated 2026-08-15.
• The audit trail is an opt-in, separate SQLite file (default <cwd>/.trelix/audit.db) and uses sha256(prev_hash || canonical_json(content)) to produce tamper-evident hashes.

Supabase is acquiring Turso

Supabase is acquiring Turso, a serverless SQLite database company, announced on October 2, 2026.

Supabase data exposure: 16,000 databases leaking personal data

Cybersecurity firm UpGuard has discovered that approximately 16,000 databases hosted by Supabase, a popular development platform for AI vibe-coded apps, are exposing sensitive personal data to the public web. The exposed data includes names, addresses, phone numbers, and passwords, some of which are linked to sensitive projects like an Indian adult streaming site, a U.S. valet service, an immigration service, and even an African consulate. While Supabase, which recently reached a $10 billion valuation, has made security improvements, its CISO Bil Harmer emphasized that security is a shared responsibility and that projects are 'secure by default'. The findings highlight the growing risk of data breaches due to misconfigured AI-generated applications, as the ease of building apps with AI tools often leads to security flaws.

• UpGuard found around 16,000 Supabase-hosted databases exposing personal data.
• Exposed data includes names, addresses, phone numbers, and passwords.
• Supabase reached a $10 billion valuation earlier in 2026.

Supabase is now available in Gemini Enterprise

Connect Supabase to Gemini Enterprise and query your Supabase projects with natural language, right inside the platform.