sqlite: less-than-useful error reporting when using SQLTagStore queries

SQL error reporting when using the SQLTagStore methods is extremely truncated, compared to conventional statement execution.

const sqlite = require('node:sqlite')
const db = new sqlite.DatabaseSync(':memory:')
const tagStore = db.createTagStore()

db.prepare('SELECT * FROM does_not_exist').all()
// Uncaught [Error: no such table: does_not_exist] {
//   code: 'ERR_SQLITE_ERROR',
//   errcode: 1,
//   errstr: 'SQL logic error'
// }

tagStore.all`SELECT * FROM does_not_exist`
// Uncaught [Error: Failed to prepare statement] { code: 'ERR_SQLITE_ERROR' }

cc: @nodejs/sqlite

sqlite: improve error reporting for prepared statements in SQLTagStore

It's not just when preparing queries, it's also when running queries.

Hey there. Is this on the roadmap for before reaching stable?

This issue has been marked as stale due to 90 days of inactivity.
It will be automatically closed in 30 days if no further activity occurs. If this is still relevant, please leave a comment or update it to keep it open.

sqlite: improve error reporting for prepared statements in SQLTagStore

This was fixed in #61096

Navigation Menu

Repository navigation

sqlite: less-than-useful error reporting when using SQLTagStore queries #60198

Metadata

Assignees

Labels

Type

Projects

Milestone

Relationships

Development

sqlite: less-than-useful error reporting when using SQLTagStore queries #60198

Description

Activity

louwers commented on Dec 1, 2025

sebastiancarlos commented on Apr 3, 2026

github-actions commented on Jul 20, 2026

trivikr commented on Aug 31, 2026

Metadata

Metadata

Assignees

Labels

Type

Projects

Milestone

Relationships

Development

Issue actions