Hacktoberfest 2026: the issues maintainers tagged for October, open and beginner-friendly. Browse Hacktoberfest issues

Expose details of result column

Open
#374 9 comments 0 reactions 1 assignee View on GitHub

@charlielidbury is already working on this.

Since Mar 31, 2020.

Assessment

This issue has not been assessed yet.

Description

enhancement

In connectors like better-sqlite3: sqlite3_column_name and the origins of columns are exposed via Statement.columns, this is useful for analysing a statement.

I've written a connector which uses the Statement.columns method to automatically replace forgein key references with getters, I would like to bring this to the browser via sql.js but that information isn't exposed in this API, or in any other wasm API.

Would you be interested in adding a method similar to better-sqlite3's prepared statements? It's quite a niche thing but most server-side connectors impliment it, so people must be using it.

I have looked a little bit at sql.js' source code and I think I'll be able to impliment it myself and make a pull request, but I've never worked on C and JS in tandem so it would be a learning curve, I just haven't gone on that curve yet in case you think it's a dumb idea and you'll never merge it.

Thanks for your time.

Dominant language
JavaScript
Stars
13.7k
Forks
1.1k
No merged PRs in 30d

Contributor guide

Open the contributing guide

First steps

  1. Read the whole issue, then the project's contributing guide.
  2. Comment on the issue to say you are picking it up — it saves two people doing the same work.
  3. Fork the repository and make your change on a branch.
  4. Open a pull request that references the issue number.

More from sql-js/sql.js

All issues in sql-js/sql.js

Similar issues

More JavaScript issues

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.