# SQLite

SQLite is a C-language library that implements a self-contained SQL database engine.

This is one page of public article previews, not the complete archive. Follow Next page to continue. Summaries are not the original full articles.

## Bun v1.4.5

DevFeed: [Bun v1.4.5](<https://devfeed.tech/articles/bun-v1-4-5-144005.md>)

Original publisher: [Read original article](<https://bun.com/blog/bun-v1.4.5>)

Author: Dylan Conway

Published: 2026-11-19T07:10:25Z

Content type: release

Language: en

Sources: [Bun](<https://devfeed.tech/sources/bun-com.md>)

Topics: [Bun](<https://devfeed.tech/topics/bun.md>), [Security](<https://devfeed.tech/topics/security.md>), [SQLite](<https://devfeed.tech/topics/sqlite.md>)

Tags: [blog](<https://devfeed.tech/tags/blog.md>), [bun](<https://devfeed.tech/tags/bun.md>), [crypto](<https://devfeed.tech/tags/crypto.md>), [dns](<https://devfeed.tech/tags/dns.md>), [fetch](<https://devfeed.tech/tags/fetch.md>), [fixed](<https://devfeed.tech/tags/fixed.md>), [has](<https://devfeed.tech/tags/has.md>), [http-3](<https://devfeed.tech/tags/http-3.md>), [node](<https://devfeed.tech/tags/node.md>), [node-js](<https://devfeed.tech/tags/node-js.md>), [quic](<https://devfeed.tech/tags/quic.md>), [release](<https://devfeed.tech/tags/release.md>), [root-certificates](<https://devfeed.tech/tags/root-certificates.md>), [security](<https://devfeed.tech/tags/security.md>), [security-fixes](<https://devfeed.tech/tags/security-fixes.md>), [sqlite](<https://devfeed.tech/tags/sqlite.md>), [sqlite-3-54](<https://devfeed.tech/tags/sqlite-3-54.md>), [tls](<https://devfeed.tech/tags/tls.md>), [updates](<https://devfeed.tech/tags/updates.md>), [v1](<https://devfeed.tech/tags/v1.md>), [zstandard](<https://devfeed.tech/tags/zstandard.md>)

### AI overview

Bun v1.4.5 is a security release updating lsquic, c-ares, SQLite, llhttp, and BoringSSL, with fixes affecting HTTP/3, HTTP/1.1, TLS, DNS, Zstandard, and related Bun and Node.js APIs. It also addresses HTTP/3 and `node:quic` stability, RSA signature handling in `node:crypto`, and certificate error and trust-chain behavior to match Node.js in specified cases. Custom root certificates are validated more strictly, which can reject some legacy certificates; Bun's bundled roots are unaffected. SQLite 3.54 restricts `ALTER TABLE` changes to columns named `rowid`, `oid`, or `_rowid_`, and invokes `setAuthorizer()` for functions in `DEFAULT` expressions. On macOS, Bun uses system SQLite. Install with `curl -fsSL https://bun.sh/install | bash`; upgrade with `bun upgrade`.

### Source excerpt

This is a security release. It updates lsquic, c-ares, SQLite, llhttp and BoringSSL.

## llm 0.37.3

DevFeed: [llm 0.37.3](<https://devfeed.tech/articles/llm-0-37-3-136597.md>)

Original publisher: [Read original article](<https://simonwillison.net/2026/Nov/16/llm/>)

Author: Simon Willison

Published: 2026-11-16T23:57:26Z

Content type: release

Language: en

Sources: [Simon Willison's Weblog](<https://devfeed.tech/sources/simon-willison-s-weblog.md>)

Topics: [Release notes](<https://devfeed.tech/topics/release-notes.md>), [SQLite](<https://devfeed.tech/topics/sqlite.md>), [Homebrew](<https://devfeed.tech/topics/homebrew.md>), [version](<https://devfeed.tech/topics/version.md>), [Large Language Model](<https://devfeed.tech/topics/llm.md>)

Tags: [ai](<https://devfeed.tech/tags/ai.md>), [ai-2-326](<https://devfeed.tech/tags/ai-2-326.md>), [bug-fix](<https://devfeed.tech/tags/bug-fix.md>), [d-richard-hipp](<https://devfeed.tech/tags/d-richard-hipp.md>), [d-richard-hipp-21](<https://devfeed.tech/tags/d-richard-hipp-21.md>), [documentation](<https://devfeed.tech/tags/documentation.md>), [generative-ai](<https://devfeed.tech/tags/generative-ai.md>), [generative-ai-2-064](<https://devfeed.tech/tags/generative-ai-2-064.md>), [homebrew](<https://devfeed.tech/tags/homebrew.md>), [json](<https://devfeed.tech/tags/json.md>), [json-array](<https://devfeed.tech/tags/json-array.md>), [json-object](<https://devfeed.tech/tags/json-object.md>), [llm](<https://devfeed.tech/tags/llm.md>), [llm-654](<https://devfeed.tech/tags/llm-654.md>), [llms](<https://devfeed.tech/tags/llms.md>), [llms-2-028](<https://devfeed.tech/tags/llms-2-028.md>), [logging](<https://devfeed.tech/tags/logging.md>), [release](<https://devfeed.tech/tags/release.md>), [software](<https://devfeed.tech/tags/software.md>), [sql](<https://devfeed.tech/tags/sql.md>), [sqlite](<https://devfeed.tech/tags/sqlite.md>), [sqlite-491](<https://devfeed.tech/tags/sqlite-491.md>), [webassembly](<https://devfeed.tech/tags/webassembly.md>), [webassembly-135](<https://devfeed.tech/tags/webassembly-135.md>), [workaround](<https://devfeed.tech/tags/workaround.md>)

### AI overview

LLM 0.37.3 fixes a logging problem exposed by Homebrew's SQLite 3.54.1. A nested `json_array` passed directly to `json_object` now becomes SQL text, so the result is `{"a":"[1]"}`; SQLite 3.54.0 had returned `{"a":[1]}` because of a bug. The documented workaround is to wrap the subquery in `json(...)`, which marks its text as JSON: `json_object('a', json((select json_array(1))))`. The excerpt describes this fix but does not specify other release changes.

### Source excerpt

Release: llm 0.37.3 A bug fix release for LLM, mainly to cover a problem with the most recent Homebrew package of the software. Homebrew now ships the latest SQLite, 3.54.1, which includes a fix that broke LLM's logging code. Short version: in SQLite 3.54.0 the following SQL: select json_object('a', (select json_array(1))) Returns this: {"a":[1]} But in 3.54.1 the same query returns this: {"a":"[1]"} According to D. Richard Hipp: That was a bug fix. Per the documentation, (SELECT json_array(...)) returns SQL text, not JSON. Hence the 3.54.1 behavior is correct and 3.54.0 was a bug. The workaround looks like this: select json_object('a', json((select json_array(1)))) Tags: llm, webassembly, sqlite, generative-ai, ai, llms, d-richard-hipp

## funkycache: a Python library to cache functions in SQLite

DevFeed: [funkycache: a Python library to cache functions in SQLite](<https://devfeed.tech/articles/funkycache-a-python-library-to-cache-functions-in-sqlite-136003.md>)

Original publisher: [Read original article](<https://alexwlchan.net/2026/funkycache/>)

Published: 2026-11-16T08:01:35Z

Content type: article

Language: en

Sources: [alexwlchan](<https://devfeed.tech/sources/alexwlchan.md>)

Topics: [Cache](<https://devfeed.tech/topics/cache.md>), [Python](<https://devfeed.tech/topics/python.md>), [SQLite](<https://devfeed.tech/topics/sqlite.md>), [cache-invalidation](<https://devfeed.tech/topics/cache-invalidation.md>), [Pydantic](<https://devfeed.tech/topics/pydantic.md>), [Library](<https://devfeed.tech/topics/library.md>)

Tags: [airflow](<https://devfeed.tech/tags/airflow.md>), [api](<https://devfeed.tech/tags/api.md>), [blogging-about-blogging](<https://devfeed.tech/tags/blogging-about-blogging.md>), [cache](<https://devfeed.tech/tags/cache.md>), [cache-invalidation](<https://devfeed.tech/tags/cache-invalidation.md>), [caching](<https://devfeed.tech/tags/caching.md>), [dag](<https://devfeed.tech/tags/dag.md>), [dependencies](<https://devfeed.tech/tags/dependencies.md>), [functions](<https://devfeed.tech/tags/functions.md>), [library](<https://devfeed.tech/tags/library.md>), [python](<https://devfeed.tech/tags/python.md>), [sqlite](<https://devfeed.tech/tags/sqlite.md>)

### AI overview

funkycache caches Python function outputs in SQLite through a decorator modeled on functools.cache. It normalizes calls, including positional arguments and defaults, into cache keys; JSON-encodes and XXH64-hashes those keys. Return values are JSON-serialized and restored with Pydantic based on the function's return type annotation, so this approach requires typed functions. Cache entries can be invalidated when the function's source, declared files or folders, or static dependency values change. Generators are materialized into lists for storage, subject to a soft memory budget; oversized outputs bypass caching and continue to the caller. The author reports a warm site build of about half a second, with filesystem traversal taking a significant share. The excerpt describes the author's use case and design choices, not comparative performance across general workloads.

### Source excerpt

Why did I write a new caching library, and how does it work?

## parse\_number() as a SQLite extension: C vs Rust

DevFeed: [parse\_number() as a SQLite extension: C vs Rust](<https://devfeed.tech/articles/parse-number-as-a-sqlite-extension-c-vs-rust-122821.md>)

Original publisher: [Read original article](<https://simonwillison.net/2026/Nov/8/sqlite-parse-number-c-vs-rust/>)

Author: Simon Willison

Published: 2026-11-08T22:26:00Z

Content type: article

Language: en

Sources: [Simon Willison's Weblog](<https://devfeed.tech/sources/simon-willison-s-weblog.md>)

Topics: [SQLite](<https://devfeed.tech/topics/sqlite.md>), [Rust](<https://devfeed.tech/topics/rust.md>), [AI Chat](<https://devfeed.tech/topics/ai-chat.md>)

Tags: [c](<https://devfeed.tech/tags/c.md>), [c-55](<https://devfeed.tech/tags/c-55.md>), [claude](<https://devfeed.tech/tags/claude.md>), [claude-325](<https://devfeed.tech/tags/claude-325.md>), [function](<https://devfeed.tech/tags/function.md>), [parsing](<https://devfeed.tech/tags/parsing.md>), [performance](<https://devfeed.tech/tags/performance.md>), [research](<https://devfeed.tech/tags/research.md>), [research-12](<https://devfeed.tech/tags/research-12.md>), [rust](<https://devfeed.tech/tags/rust.md>), [rust-116](<https://devfeed.tech/tags/rust-116.md>), [sqlite](<https://devfeed.tech/tags/sqlite.md>), [sqlite-490](<https://devfeed.tech/tags/sqlite-490.md>)

### AI overview

The reported C SQLite extension was much smaller than the Rust versions (14 KB versus 321 KB with Rusqlite and 298 KB with sqlite-loadable-rs), but initially slower. Replacing C's strtod-based parsing with a custom parser using "Clinger's fast path" improved its reported net cost per row over two million rows: 19 ns on mixed data, 16 ns on integers, and 18 ns on decimals, compared with 46/36/55 ns for Rusqlite and 41/32/47 ns for sqlite-loadable-rs. The supplied excerpt describes the experiment and results but does not include implementation details or the full report.

### Source excerpt

Research: parse_number() as a SQLite extension: C vs Rust I was out walking the dog when I got curious about how easy/difficult it would be to write a SQLite C extension that adds a parse_number() function for turning strings like -$1,234.56 or '12.5%' into numeric values that could be summed and sorted. I fired up regular Claude chat (Opus 5.5) and prompted: I'm thinking about a SQLite custom function 'parse_number(value)' that strips ',', '$', 'GBP ' and '%', handles a leading '-', and returns 'NULL' for anything it can't parse Explore the difference between building this as a SQLite extension in C v.s. in Rust - I want to compare performance and code complexity and size of the resulting.so(or whatever) file This gave me a solid starting point - the Rust extension was 321 KB (using Rusqlite) and 298 KB (using sqlite-loadable-rs), while the C extension was 14 KB. But the Rust extension was faster! Turns out that's because the Rust equivalent of C's strtod is "twice as fast". So I prompted: Try writing your own C function for parsing text into a decimal number that catches up to or beats the Rust implementation And it did, using "Clinger's fast path": Net cost per row over 2 million rows, lower is better: first C new C rusqlite sqlite-loadable Mixed data 67 ns 19 ns 46 ns 41 ns Integers only 25 ns 16 ns 36 ns 32 ns Decimals only 106 ns 18 ns 55 ns 47 ns Finally, I had it rewrite the prototype as a research report to match the others in simonw/research by prompting this: Clone simonw/research from GitHub and turn your above investigation into a research report as seen in that repository - you can give me a zip file to download that contains your new folder Here's the resulting report. Tags: c, research, sqlite, rust, claude

## Introduction to Python SQL Libraries

DevFeed: [Introduction to Python SQL Libraries](<https://devfeed.tech/articles/introduction-to-python-sql-libraries-121711.md>)

Original publisher: [Read original article](<https://realpython.com/python-sql-libraries/>)

Author: Usman Malik

Published: 2026-11-06T14:00:00Z

Content type: tutorial

Language: en

Sources: [Real Python](<https://devfeed.tech/sources/real-python.md>)

Topics: [Python](<https://devfeed.tech/topics/python.md>), [SQL](<https://devfeed.tech/topics/sql.md>), [SQLite](<https://devfeed.tech/topics/sqlite.md>), [MySQL](<https://devfeed.tech/topics/mysql.md>), [SQLAlchemy](<https://devfeed.tech/topics/sqlalchemy.md>)

Tags: [17](<https://devfeed.tech/tags/17.md>), [2](<https://devfeed.tech/tags/2.md>), [3](<https://devfeed.tech/tags/3.md>), [about](<https://devfeed.tech/tags/about.md>), [addition](<https://devfeed.tech/tags/addition.md>), [all](<https://devfeed.tech/tags/all.md>), [also](<https://devfeed.tech/tags/also.md>), [application](<https://devfeed.tech/tags/application.md>), [connect](<https://devfeed.tech/tags/connect.md>), [databases](<https://devfeed.tech/tags/databases.md>), [introduction](<https://devfeed.tech/tags/introduction.md>), [libraries](<https://devfeed.tech/tags/libraries.md>), [mysql](<https://devfeed.tech/tags/mysql.md>), [postgresql](<https://devfeed.tech/tags/postgresql.md>), [python](<https://devfeed.tech/tags/python.md>), [queries](<https://devfeed.tech/tags/queries.md>), [run](<https://devfeed.tech/tags/run.md>), [sql](<https://devfeed.tech/tags/sql.md>), [sqlite](<https://devfeed.tech/tags/sqlite.md>), [with](<https://devfeed.tech/tags/with.md>)

### AI overview

The tutorial builds a small social media database in SQLite, MySQL, and PostgreSQL using Python, then demonstrates table creation and common insert, select, update, and delete queries. SQLite uses the built-in `sqlite3` module and creates a database file when connecting to a path. MySQL requires a third-party driver such as `mysql-connector-python`; creating a database takes a separate server connection and `CREATE DATABASE` query. PostgreSQL uses `psycopg2` (the text says Psycopg 3 may suit new projects) and likewise requires creating the database before connecting to it. Query execution generally uses cursors; MySQL examples show both SQL strings and `executemany()` with placeholders, while the PostgreSQL examples pass placeholder-based records to `execute()`. The tutorial notes database-specific syntax for auto-incrementing IDs and foreign keys, and uses `fetchall()` to read rows and joins across related tables. MySQL and PostgreSQL servers must be running to follow those sections.

### Source excerpt

Connect to SQLite, MySQL, and PostgreSQL databases with Python SQL libraries, then run common queries from a single Python application.

## Change Data Capture in SQLite, Without the Triggers

DevFeed: [Change Data Capture in SQLite, Without the Triggers](<https://devfeed.tech/articles/change-data-capture-in-sqlite-without-the-triggers-121133.md>)

Original publisher: [Read original article](<https://turso.tech/blog/change-data-capture-in-sqlite-without-the-triggers>)

Author: Jeff Olson

Published: 2026-11-05T00:00:00Z

Content type: article

Language: en

Sources: [Turso](<https://devfeed.tech/sources/turso-blog.md>)

Topics: [Turso](<https://devfeed.tech/topics/turso.md>), [SQLite](<https://devfeed.tech/topics/sqlite.md>), [Event-Streaming](<https://devfeed.tech/topics/event-streaming.md>), [event-driven data processing](<https://devfeed.tech/topics/event-driven-data-processing.md>), [transaction-log](<https://devfeed.tech/topics/transaction-log.md>), [Publish-subscribe pattern](<https://devfeed.tech/topics/pubsub.md>), [Debezium Connector](<https://devfeed.tech/topics/debezium-connector.md>)

Tags: [2](<https://devfeed.tech/tags/2.md>), [built-in](<https://devfeed.tech/tags/built-in.md>), [capture](<https://devfeed.tech/tags/capture.md>), [cdc](<https://devfeed.tech/tags/cdc.md>), [change](<https://devfeed.tech/tags/change.md>), [change-data-capture](<https://devfeed.tech/tags/change-data-capture.md>), [consumer](<https://devfeed.tech/tags/consumer.md>), [data](<https://devfeed.tech/tags/data.md>), [database](<https://devfeed.tech/tags/database.md>), [delete](<https://devfeed.tech/tags/delete.md>), [engineering](<https://devfeed.tech/tags/engineering.md>), [here](<https://devfeed.tech/tags/here.md>), [how-to](<https://devfeed.tech/tags/how-to.md>), [insert](<https://devfeed.tech/tags/insert.md>), [records](<https://devfeed.tech/tags/records.md>), [software-architecture](<https://devfeed.tech/tags/software-architecture.md>), [sqlite](<https://devfeed.tech/tags/sqlite.md>), [triggers](<https://devfeed.tech/tags/triggers.md>), [turso](<https://devfeed.tech/tags/turso.md>), [update](<https://devfeed.tech/tags/update.md>), [works](<https://devfeed.tech/tags/works.md>), [write](<https://devfeed.tech/tags/write.md>)

### AI overview

Turso Database adds built-in SQLite CDC that records committed inserts, updates, and deletes in `turso_cdc` without per-table triggers. Consumers can poll the ordered stream, group records by transaction, and resume from a saved watermark; they should make processing idempotent because crashes can replay already-applied changes. Modes retain primary keys, before or after images, or full details, and schema changes are recorded. The feature is actively developed: pin versions, and snapshot column lists before migrations because decoding old records with today's columns can misalign them. CDC captures row facts, not domain meaning or user identity; those require application-side context. The excerpt also cautions that retention cleanup on synced databases may remove changes Sync has not pushed.

### Source excerpt

Built-in CDC in Turso Database records every insert, update, and delete for you. Here is how it works, where it is rough, and how to write a consumer that survives restarts.

## A Symbolic-Neural Framework for Context-Aware Evidence Extraction from Mobile SQLite Databases

DevFeed: [A Symbolic-Neural Framework for Context-Aware Evidence Extraction from Mobile SQLite Databases](<https://devfeed.tech/articles/a-symbolic-neural-framework-for-context-aware-evidence-extraction-from-mobile-sqlite-databases-114095.md>)

Original publisher: [Read original article](<https://arxiv.org/abs/2611.03323>)

Author: Jeel Piyushkumar Khatiwala (University of Baltimore), Divyangkumar Patel (Cox Automotive Inc), Dianxiang Xu (University of Missouri-Kansas City), Weifeng Xu (University of Baltimore)

Published: 2026-11-03T05:00:00Z

Content type: article

Language: en

Sources: [arXiv: Cryptography and Security](<https://devfeed.tech/sources/arxiv-cryptography-and-security.md>)

Topics: [Digital forensics](<https://devfeed.tech/topics/digital-forensics.md>), [SQLite](<https://devfeed.tech/topics/sqlite.md>), [Artificial Intelligence](<https://devfeed.tech/topics/ai.md>), [Android](<https://devfeed.tech/topics/android.md>), [iOS](<https://devfeed.tech/topics/ios.md>)

Tags: [android](<https://devfeed.tech/tags/android.md>), [cs-cr](<https://devfeed.tech/tags/cs-cr.md>), [databases](<https://devfeed.tech/tags/databases.md>), [framework](<https://devfeed.tech/tags/framework.md>), [ios](<https://devfeed.tech/tags/ios.md>), [language-model](<https://devfeed.tech/tags/language-model.md>), [metadata](<https://devfeed.tech/tags/metadata.md>), [mobile](<https://devfeed.tech/tags/mobile.md>), [neural](<https://devfeed.tech/tags/neural.md>), [sqlite](<https://devfeed.tech/tags/sqlite.md>)

### AI overview

SNEEF addresses brittle, schema-specific forensic extraction from mobile SQLite databases by representing rows as context-value pairs with column labels and standardized provenance metadata. A language model recognizes nine forensic entity types, and the PA-EEP protocol links accepted entities to their source table and row. Across five examiner-verified corpora from public Android and iOS device images and multiple app versions, SNEEF achieved an F1 score of 0.967 on SQLite row-content entities, excluding application names, versus 0.728 for a context-free configuration, with gains across all corpora. The authors also introduce a taxonomy of extraction failure modes.

### Source excerpt

arXiv:2611.03323v1 Announce Type: new Abstract: Reliable forensic evidence extraction from mobile SQLite databases is challenging because application schemas are undocumented, evolve across releases, and differ across operating systems, making schema-specific methods brittle and difficult to maintain. We present SNEEF, a symbolic-neural framework for context-aware evidence extraction that encodes each SQLite row as context-value pairs with standardized provenance metadata and column labels, uses a language model to recognize nine forensic entity types, and binds each accepted entity to its source table and row through the PA-EEP provenance protocol. We evaluate SNEEF against examiner-verified ground truth from five corpora built from public Android and iOS device images, spanning multiple application versions. SNEEF achieves an F1 score of 0.967 for evidence entities extracted from SQLite row content, excluding application names, compared with 0.728 for a context-free configuration, with consistent gains across all corpora. We also introduce an Evidence Failure Mode taxonomy to characterize why extraction errors occur.

## CVE-2026-119379 - SQLite before 3.54.0 Heap Buffer Overflow via Session Extension sessionUpdateFind()

DevFeed: [CVE-2026-119379 - SQLite before 3.54.0 Heap Buffer Overflow via Session Extension sessionUpdateFind()](<https://devfeed.tech/articles/cve-2026-119379-sqlite-before-3-54-0-heap-buffer-overflow-via-session-extension-sessionupdatefind-107797.md>)

Original publisher: [Read original article](<https://cvefeed.io/vuln/detail/CVE-2026-119379>)

Author: CVEFEED.io; vulncheck.com

Published: 2026-10-30T12:16:36Z

Content type: article

Language: en

Sources: [Latest High/Critical Vulnerabilitiy Feed](<https://devfeed.tech/sources/latest-high-critical-vulnerabilitiy-feed.md>)

Topics: [heap overflow](<https://devfeed.tech/topics/heap-overflow.md>), [SQLite](<https://devfeed.tech/topics/sqlite.md>)

Tags: [2026](<https://devfeed.tech/tags/2026.md>), [buffer](<https://devfeed.tech/tags/buffer.md>), [buffer-overflow](<https://devfeed.tech/tags/buffer-overflow.md>), [cve](<https://devfeed.tech/tags/cve.md>), [cve-2026-119379](<https://devfeed.tech/tags/cve-2026-119379.md>), [extension](<https://devfeed.tech/tags/extension.md>), [heap](<https://devfeed.tech/tags/heap.md>), [sqlite](<https://devfeed.tech/tags/sqlite.md>)

### AI overview

SQLite versions before 3.54.0 built with the session extension have a heap buffer overflow in `sqlite3changeset_apply()`. A crafted changeset can repeat a table name in a later block with a larger column count, causing `sessionUpdateFind()` to write past the undersized `aUpdateMask` allocation. The source rates the vulnerability 8.5 (High); it provides no remediation details in the excerpt.

### Source excerpt

CVE ID :CVE-2026-119379 Published : Oct. 30, 2026, 12:16 p.m. | 1 hour, 32 minutes ago Description :SQLite before 3.54.0 built with the session extension contains a heap buffer overflow vulnerability in sqlite3changeset_apply() that allows attackers to corrupt heap memory by supplying crafted changesets. Attackers can repeat a table name in a second changeset block with a larger column count, causing sessionUpdateFind() to memset past the undersized aUpdateMask allocation. Severity: 8.5 | HIGH Visit the link for more details, such as CVSS details, affected products, timeline, and more...

## PicPeak: Self-Hosted Photo Galleries That Make Sharing Easy

DevFeed: [PicPeak: Self-Hosted Photo Galleries That Make Sharing Easy](<https://devfeed.tech/articles/picpeak-self-hosted-photo-galleries-that-make-sharing-easy-107002.md>)

Original publisher: [Read original article](<https://noted.lol/picpeak/>)

Author: Jeremy

Published: 2026-10-29T11:39:23Z

Content type: article

Language: en

Sources: [Noted](<https://devfeed.tech/sources/noted.md>)

Topics: [Self-hosted](<https://devfeed.tech/topics/self-hosted.md>), [Image](<https://devfeed.tech/topics/image.md>), [Homelab](<https://devfeed.tech/topics/homelab.md>), [SQLite](<https://devfeed.tech/topics/sqlite.md>)

Tags: [contribute](<https://devfeed.tech/tags/contribute.md>), [events](<https://devfeed.tech/tags/events.md>), [gallery](<https://devfeed.tech/tags/gallery.md>), [guests](<https://devfeed.tech/tags/guests.md>), [photo](<https://devfeed.tech/tags/photo.md>), [self-hosted](<https://devfeed.tech/tags/self-hosted.md>), [self-hosted-photo-galleries](<https://devfeed.tech/tags/self-hosted-photo-galleries.md>), [sharing](<https://devfeed.tech/tags/sharing.md>)

### AI overview

PicPeak is an open-source, self-hosted gallery platform built around sharing event albums rather than managing an entire photo library. Hosts can customize galleries, add passwords and expiration dates, and let visitors view or download images without accounts. Guest uploads and a live slideshow help collect and display photos during events; photographers can also use favorites and client feedback. Deployment options include an all-in-one Docker image with SQLite or a Docker Compose stack with PostgreSQL and Redis. It supports local or S3-compatible storage and can reference photos in an external media directory without moving originals. The text also notes that customer management and invoicing are in beta.

### Source excerpt

PicPeak is a self-hosted photo gallery platform for sharing events and letting guests contribute their own pictures.

## Back to the Future: Rethinking EDA Infrastructure for Agentic Systems in Chip Design Verification

DevFeed: [Back to the Future: Rethinking EDA Infrastructure for Agentic Systems in Chip Design Verification](<https://devfeed.tech/articles/back-to-the-future-rethinking-eda-infrastructure-for-agentic-systems-in-chip-design-verification-99843.md>)

Original publisher: [Read original article](<https://arxiv.org/abs/2610.06790>)

Author: Je Yang, Ivan Lobov, Thomas Karpati

Published: 2026-10-26T04:00:00Z

Content type: article

Language: en

Sources: [arXiv: Artificial Intelligence](<https://devfeed.tech/sources/arxiv-artificial-intelligence.md>)

Topics: [Chip design](<https://devfeed.tech/topics/chip-design.md>), [text2sql](<https://devfeed.tech/topics/text2sql.md>), [AI for SQL query generation](<https://devfeed.tech/topics/ai-for-sql-query-generation.md>), [Agentic AI](<https://devfeed.tech/topics/what-is-agentic-ai.md>), [Multi Agent Systems](<https://devfeed.tech/topics/multi-agent-systems.md>), [Artificial Intelligence](<https://devfeed.tech/topics/ai.md>), [SQLite](<https://devfeed.tech/topics/sqlite.md>)

Tags: [agent-orchestration](<https://devfeed.tech/tags/agent-orchestration.md>), [agentic](<https://devfeed.tech/tags/agentic.md>), [agentic-systems](<https://devfeed.tech/tags/agentic-systems.md>), [artificial-intelligence](<https://devfeed.tech/tags/artificial-intelligence.md>), [automation](<https://devfeed.tech/tags/automation.md>), [autonomous](<https://devfeed.tech/tags/autonomous.md>), [benchmark](<https://devfeed.tech/tags/benchmark.md>), [chip](<https://devfeed.tech/tags/chip.md>), [chip-design](<https://devfeed.tech/tags/chip-design.md>), [code-generation](<https://devfeed.tech/tags/code-generation.md>), [cs-ai](<https://devfeed.tech/tags/cs-ai.md>), [database](<https://devfeed.tech/tags/database.md>), [debugging](<https://devfeed.tech/tags/debugging.md>), [design](<https://devfeed.tech/tags/design.md>), [design-automation](<https://devfeed.tech/tags/design-automation.md>), [design-verification](<https://devfeed.tech/tags/design-verification.md>), [eda](<https://devfeed.tech/tags/eda.md>), [electronic-design-automation](<https://devfeed.tech/tags/electronic-design-automation.md>), [framework](<https://devfeed.tech/tags/framework.md>), [infrastructure](<https://devfeed.tech/tags/infrastructure.md>), [verification](<https://devfeed.tech/tags/verification.md>)

### AI overview

BTTF targets post-simulation verification and waveform debugging, areas the abstract says are largely overlooked by LLM work focused on static RTL generation. It converts unstructured simulation dumps into a normalized relational SQLite database, then uses a collaborative multi-agent engine to turn natural-language verification queries into schema-aware SQL and correlate signal anomalies with versioned RTL repositories. On a 150-query benchmark, it reports 95.33% execution accuracy. The excerpt does not specify benchmark setup or comparisons.

### Source excerpt

arXiv:2610.06790v2 Announce Type: replace Abstract: The unprecedented computational scale of modern artificial intelligence depends on complex, multi-billion-transistor Systems-on-Chip, yet the workflows that verify these chips remain stubbornly manual. Although Large Language Models (LLMs) have made rapid inroads into Electronic Design Automation (EDA), approximately 74.6% of existing studies target static Register-Transfer Level (RTL) code generation, leaving post-simulation verification and interactive waveform debugging largely untouched. We introduce Back-to-the-Future (BTTF), an end-to-end agentic framework that closes this infrastructural gap. BTTF distills massive, unstructured simulation dumps into a normalized relational SQLite database and couples it with a collaborative multi-agent orchestration engine that translates natural-language verification queries into schema-aware SQL while correlating signal anomalies with versioned RTL repositories. Across a 150-query benchmark, BTTF attains 95.33% execution accuracy, charting a practical path toward autonomous EDA verification.

## Can You Build an Agent Entirely in SQL? Almost

DevFeed: [Can You Build an Agent Entirely in SQL? Almost](<https://devfeed.tech/articles/can-you-build-an-agent-entirely-in-sql-almost-98770.md>)

Original publisher: [Read original article](<https://hackernoon.com/can-you-build-an-agent-entirely-in-sql-almost?source=rss>)

Author: Nicholas Lisac

Published: 2026-10-23T22:25:09Z

Content type: article

Language: en

Sources: [HackerNoon](<https://devfeed.tech/sources/hackernoon.md>)

Topics: [Agent Harness](<https://devfeed.tech/topics/agent-harness.md>), [SQL](<https://devfeed.tech/topics/sql.md>), [SQLite](<https://devfeed.tech/topics/sqlite.md>), [AI Agent](<https://devfeed.tech/topics/ai-agent.md>), [Python](<https://devfeed.tech/topics/python.md>)

Tags: [agent](<https://devfeed.tech/tags/agent.md>), [agent-harness](<https://devfeed.tech/tags/agent-harness.md>), [ai](<https://devfeed.tech/tags/ai.md>), [ai-agent](<https://devfeed.tech/tags/ai-agent.md>), [ai-agents](<https://devfeed.tech/tags/ai-agents.md>), [harness](<https://devfeed.tech/tags/harness.md>), [react-loop](<https://devfeed.tech/tags/react-loop.md>), [react-loop-explained](<https://devfeed.tech/tags/react-loop-explained.md>), [sql](<https://devfeed.tech/tags/sql.md>), [sqlite](<https://devfeed.tech/tags/sqlite.md>), [tables](<https://devfeed.tech/tags/tables.md>)

### AI overview

Tables demonstrates an AI agent harness whose state and control flow live in a single SQLite file, with small external wrappers for the web app or Python CLI and an HTTPS call to a model. SQLite triggers create the ReAct loop: inserting a message sends active context to the model, records its reply, runs requested tools, and repeats until no more tools are requested. The main tool lets the model execute SQL; others support web search, URL fetching, JSON materialization, and document search and ingestion through FTS5. Messages, sessions, tools, approvals, and compacted context are stored in database tables or views. The author describes portable cartridges, per-machine API key pairing, journaled writes, and sandboxing to the database file, except for web access. Tables cannot access other local files or install software and is explicitly not a coding agent; users must provide their own model API key, and performance or success is not guaranteed.

### Source excerpt

Can you write an AI Agent harness in SQLite?

## sparqlite: SPARQL 1.1 inside SQLite, written in Rust

DevFeed: [sparqlite: SPARQL 1.1 inside SQLite, written in Rust](<https://devfeed.tech/articles/sparqlite-sparql-1-1-inside-sqlite-written-in-rust-92991.md>)

Original publisher: [Read original article](<https://simonwillison.net/2026/Oct/16/sqlite-sparql-rust/>)

Author: Simon Willison

Published: 2026-10-16T01:58:00Z

Content type: opinion

Language: en

Sources: [Simon Willison's Weblog](<https://devfeed.tech/sources/simon-willison-s-weblog.md>)

Topics: [Claude Code](<https://devfeed.tech/topics/claude-code.md>), [Rust](<https://devfeed.tech/topics/rust.md>), [RDF (Resource Description Framework)](<https://devfeed.tech/topics/rdf.md>), [SQLite](<https://devfeed.tech/topics/sqlite.md>)

Tags: [ai](<https://devfeed.tech/tags/ai.md>), [ai-2-288](<https://devfeed.tech/tags/ai-2-288.md>), [claude-code](<https://devfeed.tech/tags/claude-code.md>), [claude-code-133](<https://devfeed.tech/tags/claude-code-133.md>), [cli](<https://devfeed.tech/tags/cli.md>), [coding-agents](<https://devfeed.tech/tags/coding-agents.md>), [coding-agents-262](<https://devfeed.tech/tags/coding-agents-262.md>), [database](<https://devfeed.tech/tags/database.md>), [documentation](<https://devfeed.tech/tags/documentation.md>), [extension](<https://devfeed.tech/tags/extension.md>), [generative-ai](<https://devfeed.tech/tags/generative-ai.md>), [generative-ai-2-030](<https://devfeed.tech/tags/generative-ai-2-030.md>), [javascript](<https://devfeed.tech/tags/javascript.md>), [llms](<https://devfeed.tech/tags/llms.md>), [llms-1-996](<https://devfeed.tech/tags/llms-1-996.md>), [prompt](<https://devfeed.tech/tags/prompt.md>), [rdf](<https://devfeed.tech/tags/rdf.md>), [rdf-7](<https://devfeed.tech/tags/rdf-7.md>), [readme](<https://devfeed.tech/tags/readme.md>), [review](<https://devfeed.tech/tags/review.md>), [rust](<https://devfeed.tech/tags/rust.md>), [rust-115](<https://devfeed.tech/tags/rust-115.md>), [script](<https://devfeed.tech/tags/script.md>), [semantic-web](<https://devfeed.tech/tags/semantic-web.md>), [semantic-web-17](<https://devfeed.tech/tags/semantic-web-17.md>), [sqlite](<https://devfeed.tech/tags/sqlite.md>), [sqlite-489](<https://devfeed.tech/tags/sqlite-489.md>), [subagents](<https://devfeed.tech/tags/subagents.md>), [tutorial](<https://devfeed.tech/tags/tutorial.md>), [vibe-coding](<https://devfeed.tech/tags/vibe-coding.md>), [workflows](<https://devfeed.tech/tags/workflows.md>)

### AI overview

The author used Claude Code for web in "Ultracode" mode to build what appears to be a Rust implementation of SPARQL inside a SQLite extension. An initial prompt led the system to work for more than 12 hours; a follow-up requested READMEs for each crate, a tutorial covering installation, SQLite CLI use and SPARQL, and a script to populate realistic tutorial data. The author says the resulting code is not feasible for them to review and that understanding its documentation would take substantial effort, leaving the project's value uncertain. The article describes an experiment and the author's concerns; it does not establish the implementation's completeness, speed, or reliability.

### Source excerpt

Research: sparqlite: SPARQL 1.1 inside SQLite, written in Rust This research task is really an experiment in running Claude Code for web in "Ultracode" mode, as described in Orchestrate subagents at scale with dynamic workflows in the Claude Code documentation. With Ultracode turned on, Claude Code makes aggressive use of dynamic workflows - it generates JavaScript that defines and coordinates a network of subagents to take on complex problems. My initial prompt was this - I meant "hit the rows directly", the word "delete" was an accidental typo on my phone: Write a SQLite extension in Rust that implants SPARQL and runs really fast because it can hit the delete rows directly This caused Claude Code for web to churn for over 12 hours. I checked in on its progress the next day and sent a single follow-up prompt when I noticed how many Rust crates it had built: Every folder in the crates/ directory needs a README Include a tutorial.md teaching users how to install the extension and how to run it in the SQLite CLI and then teaching them SPARQL in addition to how to use the SQLite extension Include a script with the tutorial for populating a SQLite database with useful and realistic example data for that tutorial This project feels like next-level vibe coding - it's not remotely feasible to review the code that was produced here, and even following the documentation is a significant investment in work. I'm not entirely sure what to do with this - I appear to have a full SPARQL implementation in Rust inside SQLite now, but how valuable is that if I created it on a whim and can't (or won't) invest the necessary time to understand what it can do? Tags: rdf, semantic-web, sqlite, ai, rust, generative-ai, llms, coding-agents, claude-code

## This Week in Rails: performance gains, SQLite rollback fixes, and more

DevFeed: [This Week in Rails: performance gains, SQLite rollback fixes, and more](<https://devfeed.tech/articles/faster-blank-checks-safer-sqlite-rollbacks-and-more-88986.md>)

Original publisher: [Read original article](<https://rubyonrails.org/2026/10/16/this-week-in-rails>)

Author: vipulnsward

Published: 2026-10-16T00:00:00Z

Content type: news

Language: en

Sources: [Ruby on Rails](<https://devfeed.tech/sources/ruby-on-rails-compress-the-complexity-of-modern-web-apps.md>)

Topics: [Ruby on Rails](<https://devfeed.tech/topics/ruby-on-rails.md>), [SQLite](<https://devfeed.tech/topics/sqlite.md>), [API Logging](<https://devfeed.tech/topics/api-logging.md>)

Tags: [active-record](<https://devfeed.tech/tags/active-record.md>), [activerecord](<https://devfeed.tech/tags/activerecord.md>), [it](<https://devfeed.tech/tags/it.md>), [news](<https://devfeed.tech/tags/news.md>), [rails](<https://devfeed.tech/tags/rails.md>), [sqlite](<https://devfeed.tech/tags/sqlite.md>)

### AI overview

This week's Rails changes include faster ASCII String#blank? checks, shared read-only Active Record defaults, and fewer intermediate objects when rendering collections. The updates also address SQLite rollback errors, schema dumps for PostgreSQL extensions, eager loading and CTE issues, job retry payloads, composite-key queries, thread isolation, and JavaScript package manager detection.

### Source excerpt

Hi, it's Vipul. Let's explore this week's changes in the Rails codebase.

## Scaling Android Search: Room @Fts4 vs SQL LIKE

DevFeed: [Scaling Android Search: Room @Fts4 vs SQL LIKE](<https://devfeed.tech/articles/scaling-android-search-room-fts4-vs-sql-like-84568.md>)

Original publisher: [Read original article](<https://proandroiddev.com/scaling-android-search-room-fts4-vs-sql-like-b2a8232cbd12?source=rss----c72404660798---4>)

Author: Oğuzhan Aslan

Published: 2026-10-10T17:27:22Z

Content type: tutorial

Language: en

Sources: [ProAndroidDev](<https://devfeed.tech/sources/proandroiddev-medium.md>)

Topics: [SQLite](<https://devfeed.tech/topics/sqlite.md>), [Android](<https://devfeed.tech/topics/android.md>), [SQL](<https://devfeed.tech/topics/sql.md>)

Tags: [android](<https://devfeed.tech/tags/android.md>), [android-development](<https://devfeed.tech/tags/android-development.md>), [benchmarks](<https://devfeed.tech/tags/benchmarks.md>), [full-text-search](<https://devfeed.tech/tags/full-text-search.md>), [indexing](<https://devfeed.tech/tags/indexing.md>), [programming](<https://devfeed.tech/tags/programming.md>), [room](<https://devfeed.tech/tags/room.md>), [software-development](<https://devfeed.tech/tags/software-development.md>), [software-engineering](<https://devfeed.tech/tags/software-engineering.md>)

### AI overview

The tutorial compares SQL LIKE substring searches with SQLite FTS4 token searches in Android Room. It demonstrates external-content FTS entities, index synchronization, DAO queries, and token-prefix matching. Its reported benchmark at 5,000 emails shows FTS4 taking 6.811 ms versus 63.762 ms for LIKE, while discussing differences in search behavior and indexing overhead.

### Source excerpt

A practical deep-dive into full-text search indexing, inverted indices, and microsecond query benchmarks using Android Jetpack Room. When building search into an Android application -- whether querying an offline-first inbox, notes catalog, documentation cache, or e-commerce catalog -- almost every developer starts with the same query: SELECT * FROM mails WHERE subject LIKE '%' || :query || '%' OR body LIKE '%' || :query || '%' It is intuitive, requires zero schema alterations, and works out-of-the-box. During early development, when your local database contains 25 dummy rows, search queries return instantly. Tests pass, the UI feels snappy, and the feature gets shipped. Then reality strikes. As users accumulate months of multiline emails, notes, or cached payloads (climbing from hundreds to thousands of records), complaints begin rolling in: Keystroke lag when typing in search fields. Skipped frames and main-thread micro-stutters. Noticeable battery drain during heavy search workflows. Why does an operation that felt blazing fast in development fall apart under real-world volume? To understand this, we have to look under the hood of SQLite's query planner. Why SQL LIKE Fails at Scale In relational databases, developers rely on indices (B-Trees) to keep lookups at O(log N) time. If you query: WHERE sender LIKE 'alice%' SQLite can utilize a standard B-Tree index on sender because it knows the prefix. However, users rarely search by prefix alone. Real-world full-text search requires substring matching: finding a word anywhere within a subject or paragraph. This forces the query into a leading wildcard: WHERE body LIKE '%architecture%'WARNING: The moment a query contains a leading wildcard (%query%), standard B-Tree indices are completely bypassed. SQLite is forced to execute a sequential full table scan O(N). In a full table scan: SQLite reads every single row off the storage layer into memory. The query engine steps through every single byte of text sequentially, compa

## SQLite 3.54 Released With Faster Performance, Drops Windows XP Support

DevFeed: [SQLite 3.54 Released With Faster Performance, Drops Windows XP Support](<https://devfeed.tech/articles/sqlite-3-54-released-with-faster-performance-drops-windows-xp-support-84455.md>)

Original publisher: [Read original article](<https://www.phoronix.com/news/SQLite-3.54-Released>)

Author: Michael Larabel

Published: 2026-10-10T00:41:04Z

Content type: news

Language: en

Sources: [Phoronix](<https://devfeed.tech/sources/phoronix.md>)

Topics: [SQLite](<https://devfeed.tech/topics/sqlite.md>), [Windows](<https://devfeed.tech/topics/windows.md>)

Tags: [database](<https://devfeed.tech/tags/database.md>), [desktop-linux](<https://devfeed.tech/tags/desktop-linux.md>), [embedded](<https://devfeed.tech/tags/embedded.md>), [linux-benchmarking](<https://devfeed.tech/tags/linux-benchmarking.md>), [linux-hardware-benchmarks](<https://devfeed.tech/tags/linux-hardware-benchmarks.md>), [linux-hardware-reviews](<https://devfeed.tech/tags/linux-hardware-reviews.md>), [linux-how-to](<https://devfeed.tech/tags/linux-how-to.md>), [linux-performance](<https://devfeed.tech/tags/linux-performance.md>), [linux-server-benchmarks](<https://devfeed.tech/tags/linux-server-benchmarks.md>), [microsoft-windows](<https://devfeed.tech/tags/microsoft-windows.md>), [open-source-graphics](<https://devfeed.tech/tags/open-source-graphics.md>), [phoronix](<https://devfeed.tech/tags/phoronix.md>), [phoronix-test-suite](<https://devfeed.tech/tags/phoronix-test-suite.md>), [sqlite](<https://devfeed.tech/tags/sqlite.md>), [ubuntu-benchmarks](<https://devfeed.tech/tags/ubuntu-benchmarks.md>), [ubuntu-hardware](<https://devfeed.tech/tags/ubuntu-hardware.md>), [windows](<https://devfeed.tech/tags/windows.md>)

### AI overview

SQLite 3.54 removes support for Windows XP and earlier Windows versions, including Windows CE, while maintaining support for Windows Vista and newer. The release also improves Windows performance and adds command-line interface enhancements, query planner improvements, and support for O_TMPFILE on compatible systems. SQLite reports performance gains of about 4% over its benchmark on Linux x64 and 7.5% over SQLite 3.51.

### Source excerpt

SQLite 3.54 released today for this wildly popular embedded SQL database engine used by countless applications and other software. With SQLite 3.54, support for Microsoft Windows XP and older is finally removed...

## Let's build a database!

DevFeed: [Let's build a database!](<https://devfeed.tech/articles/let-s-build-a-database-113332.md>)

Original publisher: [Read original article](<https://stack.convex.dev/lets-build-a-database>)

Author: Stack

Published: 2026-10-09T15:00:37Z

Content type: tutorial

Language: en

Sources: [Stack](<https://devfeed.tech/sources/stack.md>)

Topics: [Database](<https://devfeed.tech/topics/database.md>), [SQLite](<https://devfeed.tech/topics/sqlite.md>), [transaction-log](<https://devfeed.tech/topics/transaction-log.md>), [Transactions](<https://devfeed.tech/topics/transactions.md>), [acid](<https://devfeed.tech/topics/acid.md>), [database-consistency](<https://devfeed.tech/topics/database-consistency.md>), [Heroku Postgres](<https://devfeed.tech/topics/heroku-postgres.md>)

Tags: [build](<https://devfeed.tech/tags/build.md>), [convex](<https://devfeed.tech/tags/convex.md>), [database](<https://devfeed.tech/tags/database.md>), [file](<https://devfeed.tech/tags/file.md>), [fundamentals](<https://devfeed.tech/tags/fundamentals.md>), [json](<https://devfeed.tech/tags/json.md>), [postgres](<https://devfeed.tech/tags/postgres.md>), [sqlite](<https://devfeed.tech/tags/sqlite.md>), [wrapper](<https://devfeed.tech/tags/wrapper.md>)

### AI overview

Convex's SQLite or Postgres layer stores bytes; the article attributes its transactional and reactive behavior to Convex's own backend. It builds a model from an append-only transaction log, a committer that validates read sets and retries conflicts, timestamps and versioned indexes for snapshot reads, and subscriptions that rerun queries after relevant commits. Mutations must be deterministic and side effect free so retries are safe; actions handle external effects, while a scheduler can enqueue them atomically with a successful mutation. Inspection of a local SQLite deployment shows document versions stored as timestamped rows linked to prior versions, with indexes also persisted in tables. The article presents this as an explanatory model and notes that other Convex features are outside its scope.

### Source excerpt

Is Convex just a Postgres wrapper? To answer that we build a database from scratch with the same properties as Convex, starting from a single JSON file, then crack open the SQLite file Convex uses to see what it's actually doing.

## SQLite Change Column Type Without Losing Data: The Safe Rebuild Guide

DevFeed: [SQLite Change Column Type Without Losing Data: The Safe Rebuild Guide](<https://devfeed.tech/articles/sqlite-change-column-type-without-losing-data-the-safe-rebuild-guide-63263.md>)

Original publisher: [Read original article](<https://www.sitepoint.com/sqlite-change-column-type-without-losing-data/>)

Author: SitePoint Team

Published: 2026-10-01T16:16:53Z

Content type: tutorial

Language: en

Sources: [SitePoint](<https://devfeed.tech/sources/sitepoint.md>)

Topics: [SQLite](<https://devfeed.tech/topics/sqlite.md>), [Disaster Recovery](<https://devfeed.tech/topics/disaster-recovery.md>)

Tags: [backup](<https://devfeed.tech/tags/backup.md>), [data-loss](<https://devfeed.tech/tags/data-loss.md>), [databases](<https://devfeed.tech/tags/databases.md>), [indexes](<https://devfeed.tech/tags/indexes.md>), [programming](<https://devfeed.tech/tags/programming.md>), [sqlite](<https://devfeed.tech/tags/sqlite.md>), [triggers](<https://devfeed.tech/tags/triggers.md>)

### AI overview

SQLite requires a table rebuild to change a column's declared type. This guide walks through exporting the schema, checking data and foreign key risks, backing up the database, copying values with explicit CAST(), restoring indexes and triggers, and verifying the result. It warns that nonnumeric text can silently convert to 0.0 and emphasizes testing against the actual data.

### Source excerpt

SQLite does not support altering a column type directly. Learn the safe table rebuild procedure to migrate column types, preserve data, restore indexes and triggers, and avoid silent data loss from foreign key cascades. Continue reading SQLite Change Column Type Without Losing Data: The Safe Rebuild Guide on SitePoint.

## Quiz: Enhance Your Flask Web Project With a Database

DevFeed: [Quiz: Enhance Your Flask Web Project With a Database](<https://devfeed.tech/articles/quiz-enhance-your-flask-web-project-with-a-database-60537.md>)

Original publisher: [Read original article](<https://realpython.com/quizzes/flask-database/>)

Author: Real Python

Published: 2026-09-27T12:00:00Z

Content type: tutorial

Language: en

Sources: [Real Python](<https://devfeed.tech/sources/real-python.md>)

Topics: [Flask](<https://devfeed.tech/topics/flask.md>), [Database](<https://devfeed.tech/topics/database.md>), [SQLite](<https://devfeed.tech/topics/sqlite.md>)

Tags: [database](<https://devfeed.tech/tags/database.md>), [environment-variables](<https://devfeed.tech/tags/environment-variables.md>), [flask](<https://devfeed.tech/tags/flask.md>), [how-to](<https://devfeed.tech/tags/how-to.md>), [python](<https://devfeed.tech/tags/python.md>), [server](<https://devfeed.tech/tags/server.md>), [sqlite](<https://devfeed.tech/tags/sqlite.md>)

### AI overview

An interactive 10-question quiz tests knowledge of adding a database to a Flask project, including environment variables, database schemas, SQLite connections, and storing user-submitted posts. It has no time limit and awards a score of up to 100%.

### Source excerpt

Test your understanding of Flask databases, environment variables, blueprints, SQLite schemas, and storing posts from a form.

## JPA Inspired ORM from SQLite to PostgreSQL

DevFeed: [JPA Inspired ORM from SQLite to PostgreSQL](<https://devfeed.tech/articles/jpa-inspired-orm-from-sqlite-to-postgresql-60466.md>)

Original publisher: [Read original article](<https://www.codenameone.com/blog/orm-session-from-phone-to-server/>)

Author: Shai Almog

Published: 2026-09-27T00:00:00Z

Content type: tutorial

Language: en

Sources: [CodeName One](<https://devfeed.tech/sources/codename-one.md>)

Topics: [Object-relational mapping](<https://devfeed.tech/topics/orm.md>), [Hibernate](<https://devfeed.tech/topics/hibernate.md>), [SQLite](<https://devfeed.tech/topics/sqlite.md>), [PostgreSQL](<https://devfeed.tech/topics/postgresql.md>)

Tags: [backend](<https://devfeed.tech/tags/backend.md>), [client](<https://devfeed.tech/tags/client.md>), [hibernate](<https://devfeed.tech/tags/hibernate.md>), [java](<https://devfeed.tech/tags/java.md>), [jpa](<https://devfeed.tech/tags/jpa.md>), [locking](<https://devfeed.tech/tags/locking.md>), [mariadb](<https://devfeed.tech/tags/mariadb.md>), [mysql](<https://devfeed.tech/tags/mysql.md>), [optimistic-locking](<https://devfeed.tech/tags/optimistic-locking.md>), [orm](<https://devfeed.tech/tags/orm.md>), [postgresql](<https://devfeed.tech/tags/postgresql.md>), [queries](<https://devfeed.tech/tags/queries.md>), [relationships](<https://devfeed.tech/tags/relationships.md>), [sqlite](<https://devfeed.tech/tags/sqlite.md>)

### AI overview

This tutorial introduces managed ORM sessions for shared Java entities used on a client and backend. It explains relationship mappings, persistence and transactions, generated metadata, session behavior, and optimistic locking, with client-side SQLite and backend support for SQLite, PostgreSQL, MySQL, and MariaDB.

### Source excerpt

Use managed ORM sessions, relationships, lazy loading, JPQL queries, and optimistic locking with shared Java entities on the client and backend.

## Building Multi-Tier AI Agent Memory with TypeScript and SQLite-vec

DevFeed: [Building Multi-Tier AI Agent Memory with TypeScript and SQLite-vec](<https://devfeed.tech/articles/building-multi-tier-ai-agent-memory-with-typescript-and-sqlite-vec-59913.md>)

Original publisher: [Read original article](<https://www.sitepoint.com/multi-tier-ai-agent-memory-typescript-sqlite-vec/>)

Author: SitePoint Team

Published: 2026-09-25T14:51:34Z

Content type: tutorial

Language: en

Sources: [SitePoint](<https://devfeed.tech/sources/sitepoint.md>)

Topics: [AI Agent](<https://devfeed.tech/topics/ai-agent.md>), [SQLite](<https://devfeed.tech/topics/sqlite.md>), [TypeScript](<https://devfeed.tech/topics/typescript.md>), [Node.js](<https://devfeed.tech/topics/node-js.md>), [Database](<https://devfeed.tech/topics/database.md>), [Local-First](<https://devfeed.tech/topics/local-first.md>), [AI search](<https://devfeed.tech/topics/ai-search.md>), [Persistence](<https://devfeed.tech/topics/persistence.md>)

Tags: [agent](<https://devfeed.tech/tags/agent.md>), [ai](<https://devfeed.tech/tags/ai.md>), [ai-agent](<https://devfeed.tech/tags/ai-agent.md>), [database](<https://devfeed.tech/tags/database.md>), [databases](<https://devfeed.tech/tags/databases.md>), [embeddings](<https://devfeed.tech/tags/embeddings.md>), [guides](<https://devfeed.tech/tags/guides.md>), [local-first](<https://devfeed.tech/tags/local-first.md>), [node-js](<https://devfeed.tech/tags/node-js.md>), [persistence](<https://devfeed.tech/tags/persistence.md>), [programming](<https://devfeed.tech/tags/programming.md>), [semantic](<https://devfeed.tech/tags/semantic.md>), [sqlite](<https://devfeed.tech/tags/sqlite.md>), [typescript](<https://devfeed.tech/tags/typescript.md>)

### AI overview

A tutorial for building a local, multi-tier memory system for AI agents with TypeScript, SQLite, better-sqlite3, and sqlite-vec. It implements episodic, semantic, and procedural memory in one database and connects the stores to an agent loop.

### Source excerpt

Architect a tiered local memory system for AI agents using TypeScript, better-sqlite3, and sqlite-vec across episodic, semantic, and procedural stores. Continue reading Building Multi-Tier AI Agent Memory with TypeScript and SQLite-vec on SitePoint.

## Designing a Production-Ready Agent Harness With Persistence and Checkpointing

DevFeed: [Designing a Production-Ready Agent Harness With Persistence and Checkpointing](<https://devfeed.tech/articles/designing-a-production-ready-agent-harness-with-persistence-and-checkpointing-59909.md>)

Original publisher: [Read original article](<https://www.sitepoint.com/designing-a-production-ready-agent-harness-with-persistence-and-checkpointing/>)

Author: SitePoint Team

Published: 2026-09-24T18:20:16Z

Content type: tutorial

Language: en

Sources: [SitePoint](<https://devfeed.tech/sources/sitepoint.md>)

Topics: [Agent Harness](<https://devfeed.tech/topics/agent-harness.md>), [Persistence](<https://devfeed.tech/topics/persistence.md>), [Code](<https://devfeed.tech/topics/code.md>), [distributed-systems](<https://devfeed.tech/topics/distributed-systems.md>), [Python](<https://devfeed.tech/topics/python.md>), [SQLite](<https://devfeed.tech/topics/sqlite.md>), [Orchestration](<https://devfeed.tech/topics/orchestration.md>)

Tags: [agent-harness](<https://devfeed.tech/tags/agent-harness.md>), [checkpoint](<https://devfeed.tech/tags/checkpoint.md>), [cloud](<https://devfeed.tech/tags/cloud.md>), [code](<https://devfeed.tech/tags/code.md>), [databases](<https://devfeed.tech/tags/databases.md>), [devops](<https://devfeed.tech/tags/devops.md>), [distributed-systems](<https://devfeed.tech/tags/distributed-systems.md>), [orchestration](<https://devfeed.tech/tags/orchestration.md>), [persistence](<https://devfeed.tech/tags/persistence.md>), [python](<https://devfeed.tech/tags/python.md>)

### AI overview

A tutorial on building a production-ready agent harness that preserves agent run state across process interruptions and pod rescheduling. It explains durable state, checkpointing, repeat-safe tool calls, worker coordination, and debugging records, with a Python standard-library implementation using SQLite and a design that can carry over to Postgres.

### Source excerpt

null Continue reading Designing a Production-Ready Agent Harness With Persistence and Checkpointing on SitePoint.

## Using Local RAG and Room SQLite for On-Device Android Agents

DevFeed: [Using Local RAG and Room SQLite for On-Device Android Agents](<https://devfeed.tech/articles/building-on-device-ai-agents-on-android-with-google-adk-part-4-local-rag-on-android-storing-59096.md>)

Original publisher: [Read original article](<https://proandroiddev.com/building-on-device-ai-agents-on-android-with-google-adk-part-4-local-rag-on-android-storing-6f6d8947899d?source=rss----c72404660798---4>)

Author: Pankaj Rai

Published: 2026-09-24T08:18:29Z

Content type: tutorial

Language: en

Sources: [ProAndroidDev](<https://devfeed.tech/sources/proandroiddev-medium.md>)

Topics: [Retrieval Augmented Generation (RAG)](<https://devfeed.tech/topics/retrieval-augmented-generation-rag.md>), [google-adk](<https://devfeed.tech/topics/google-adk.md>), [Android](<https://devfeed.tech/topics/android.md>), [On-device AI](<https://devfeed.tech/topics/on-device-ai.md>), [SQLite](<https://devfeed.tech/topics/sqlite.md>)

Tags: [android](<https://devfeed.tech/tags/android.md>), [google-adk](<https://devfeed.tech/tags/google-adk.md>), [on-device-ai](<https://devfeed.tech/tags/on-device-ai.md>), [retrieval-augmented-generation-rag](<https://devfeed.tech/tags/retrieval-augmented-generation-rag.md>), [sqlite](<https://devfeed.tech/tags/sqlite.md>)

### AI overview

This tutorial explains using Google ADK and Room SQLite to give an on-device Android agent persistent memory and local retrieval-augmented generation. It describes avoiding large prompts by retrieving relevant notes from a structured local database.

### Source excerpt

Combine Google ADK with Android's Room database to give your on-device agent permanent memory and local Retrieval-Augmented Generation. Continue reading on ProAndroidDev "

## Embedded Graphs in Node.js: Comparing Kùzu and SQLite Recursive CTEs

DevFeed: [Embedded Graphs in Node.js: Comparing Kùzu and SQLite Recursive CTEs](<https://devfeed.tech/articles/embedded-graphs-in-node-js-comparing-kuzu-and-sqlite-recursive-ctes-59031.md>)

Original publisher: [Read original article](<https://www.sitepoint.com/embedded-graphs-nodejs-kuzu-sqlite-recursive-ctes/>)

Author: SitePoint Team

Published: 2026-09-23T18:17:27Z

Content type: comparison

Language: en

Sources: [SitePoint](<https://devfeed.tech/sources/sitepoint.md>)

Topics: [graph-database](<https://devfeed.tech/topics/graph-database.md>), [Node.js](<https://devfeed.tech/topics/node-js.md>), [SQLite](<https://devfeed.tech/topics/sqlite.md>), [Database](<https://devfeed.tech/topics/database.md>), [Graphs](<https://devfeed.tech/topics/graphs.md>)

Tags: [comparison](<https://devfeed.tech/tags/comparison.md>), [cypher](<https://devfeed.tech/tags/cypher.md>), [database](<https://devfeed.tech/tags/database.md>), [databases](<https://devfeed.tech/tags/databases.md>), [developers](<https://devfeed.tech/tags/developers.md>), [graph-database](<https://devfeed.tech/tags/graph-database.md>), [graphs](<https://devfeed.tech/tags/graphs.md>), [node](<https://devfeed.tech/tags/node.md>), [programming](<https://devfeed.tech/tags/programming.md>), [sqlite](<https://devfeed.tech/tags/sqlite.md>)

### AI overview

A comparison of Kùzu, an embedded graph database with native Cypher support, and SQLite recursive CTEs for handling connected and hierarchical data in Node.js and TypeScript applications. It explains the embedded architecture and demonstrates query patterns with code.

### Source excerpt

Compare lightweight embedded graph storage using Kùzu Cypher queries against SQLite recursive CTEs in Node.js applications. Continue reading Embedded Graphs in Node.js: Comparing Kùzu and SQLite Recursive CTEs on SitePoint.

## The agent coordination protocol hiding in plain sight: GitHub issues

DevFeed: [The agent coordination protocol hiding in plain sight: GitHub issues](<https://devfeed.tech/articles/the-agent-coordination-protocol-hiding-in-plain-sight-github-issues-57856.md>)

Original publisher: [Read original article](<https://www.infoworld.com/article/4224587/the-agent-coordination-protocol-hiding-in-plain-sight-github-issues.html>)

Author: Jon Udell

Published: 2026-09-22T09:00:00Z

Content type: article

Language: en

Sources: [InfoWorld](<https://devfeed.tech/sources/infoworld.md>)

Topics: [Agent Harness](<https://devfeed.tech/topics/agent-harness.md>), [GitHub Issues](<https://devfeed.tech/topics/github-issues.md>), [Claude Code](<https://devfeed.tech/topics/claude-code.md>), [codex](<https://devfeed.tech/topics/codex.md>), [GitHub](<https://devfeed.tech/topics/github.md>), [Git](<https://devfeed.tech/topics/git.md>), [Command-line interface](<https://devfeed.tech/topics/cli.md>), [SQLite](<https://devfeed.tech/topics/sqlite.md>), [GUI](<https://devfeed.tech/topics/gui.md>), [Code](<https://devfeed.tech/topics/code.md>)

Tags: [agent](<https://devfeed.tech/tags/agent.md>), [agent-harness](<https://devfeed.tech/tags/agent-harness.md>), [agents](<https://devfeed.tech/tags/agents.md>), [artificial-intelligence](<https://devfeed.tech/tags/artificial-intelligence.md>), [artificial-intelligence-development-tools-generative-ai-github-software-development-version-con](<https://devfeed.tech/tags/artificial-intelligence-development-tools-generative-ai-github-software-development-version-con.md>), [claude-code](<https://devfeed.tech/tags/claude-code.md>), [cli](<https://devfeed.tech/tags/cli.md>), [codex](<https://devfeed.tech/tags/codex.md>), [development-tools](<https://devfeed.tech/tags/development-tools.md>), [generative-ai](<https://devfeed.tech/tags/generative-ai.md>), [git](<https://devfeed.tech/tags/git.md>), [github](<https://devfeed.tech/tags/github.md>), [github-issues](<https://devfeed.tech/tags/github-issues.md>), [gui](<https://devfeed.tech/tags/gui.md>), [software-development](<https://devfeed.tech/tags/software-development.md>), [sqlite](<https://devfeed.tech/tags/sqlite.md>), [version-control-systems](<https://devfeed.tech/tags/version-control-systems.md>), [workflows](<https://devfeed.tech/tags/workflows.md>)

### AI overview

The article describes Bram, an agent harness that uses Git, GitHub CLI, GitHub Issues, Claude Code, and Codex to coordinate software work. It covers switching agents, sharing work context, reviewing each other's work, and using SQLite full-text search across sessions, commits, worklists, and issues.

### Source excerpt

The agent harness I'm building, Bram, launches in a local git repository and requires that both git and gh (GitHub's CLI) be installed. Agents can wield both tools far more capably than we humans can. In the Before Time I knew it was possible to perform a git bisect or use hunk staging to separate entangled files, but it was a huge struggle to do those things. We've always known git needed a better user interface, and we've long imagined that a more rational set of commands or a stronger GUI would be the answer. Nope. The answer turned out to be directing agents to use the tools on our behalf. We know what needs doing, they know how. You may have felt the power that flows from delegating git syntax and workflows to agents. A complementary power flows from asking agents to use gh to write, read, and reply to GitHub issues. Here are some of the coordination scenarios that enables. Cross-agent coordination The GUI that Bram wraps around Claude Code and Codex enables you to switch agents with one click. Each agent wakes up with access to four buckets of context: 1) the worklist (items planned, in progress, or committed), 2) sessions (both Claude's and Codex's), 3) commits, and 4) issues. When an item is in progress I routinely switch agents and direct them to review each other's work. Three heads are better than one for both planning and execution. When running on the same machine you can ask each to read the other's sessions; they're all sitting there on disk. Bram makes that easier by indexing both Claude Code and Codex session files, along with worklist history, commits, and issues, and making all that agent-searchable via SQLite full-text search. What about collaboration across machines? Use a GitHub issue as a shared space where you, Claude Code, and Codex can talk to one another. Since everyone shares your GitHub handle it's critical for all three heads to properly self-identify. Bram's harness tells agents to sign their messages like this: Jon's Claude (main thre

[Next page](<https://devfeed.tech/topics/sqlite.md?cursor=WyIyMDI2LTA5LTIyVDA5OjAwOjAwKzAwOjAwIiwgImQyMTEwZDExLTI5YzEtNGFjYy1iMjBjLWM5NGYyYWVlMWY2YSJd>)