2021-05-24
1332
#js libraries
Elijah Asaolu
50339
May 24, 2021 ⋅ 4 min read

A detailed look at basic SQL.js features

Elijah Asaolu I am a programmer, I have a life.

Recent posts:

Typescript or Zod for Validation?

TypeScript vs Zod: Clearing up validation confusion

Learn when to use TypeScript, Zod, or both for data validation. Avoid redundant checks and build safer, type-sound applications.

Alexander Godwin
Oct 6, 2025 ⋅ 3 min read
Wasm 3 Before GTA 6 LogRocket Article

We got Wasm 3.0 before GTA 6: Meet the web’s new engine

Discover how WebAssembly 3.0’s garbage collector, exception handling, and Memory64 transform Wasm into a true mainstream web platform.

Ikeh Akinyemi
Oct 3, 2025 ⋅ 2 min read

How to use AI to build accurate ShadCN components

AI agents often break shadcn/ui components with outdated docs or made-up props. The MCP server fixes this by giving live access to registries. In this tutorial, we’ll set it up and build a Kanban board to show it in action.

Chizaram Ken
Oct 3, 2025 ⋅ 5 min read
Rust Project for Web Services LogRocket Article

The best way to structure Rust web services

Learn how to structure Rust web services with clean architecture, Cargo workspaces, and modular crates for scalable, maintainable backends.

Jude Miracle
Oct 2, 2025 ⋅ 2 min read
View all posts

6 Replies to "A detailed look at basic SQL.js features"

  1. Too bad it is only saved on the memory
    I have tried something similar called dexie.js, it has the upper hand of saving the data to indexeddb, so the data will persist after each reload

  2. Why storing data in the memory? what’s the benefit ? and what kind of data can be stored in the memory?

  3. Thank you for sharing this information with us , But I have a question with you.
    How safe is it for production?
    Please reply it will helpful for me .
    Really appreciate your work.

  4. Hi Isabella, glad you found the article helpful.

    SQL.js is an open source project, and yes it is safe to use in production

  5. “Getting started with SQL.js is as easy as installing jQuery in an existing HTML project.”

    This is freaking HILARIOUS. Installing jquery was **never** a cut and dried proposition. Between , top of body, or bottom of body, and the various situations that required each, saying the above really made me question if you were being ironic or what.

Leave a Reply