Using SQLite with Chrome 119

From NSB App Studio
Jump to navigation Jump to search

Starting with Chrome 119, Google has deprecated SQlite, also referred to as WebSQL. They have been warning of this for a while. (If you're interested in why they are doing this, check out this post).

There are several workarounds:

Workaround 1. Set a flag in Chrome

  1. Open chrome://flags/ in Chrome
  2. Search for web-sql-access
  3. Enable it
  4. relaunch browser

This is probably the quickest solution for most users. It will probably only work until Chrome 124 is released - by that time, you will need a more permanent solution in place.

Workaround 2. Register your site for an Origin Trial

You can register your site for an Origin Trial, which restores the functionality until May 28, 2024 when Chrome 124 is scheduled to appear. The advantage of this solution is that you only have to do this once: your users do not have to make any changes at their end.

  1. Go to this page: Register to WebSQL Trial
  2. Fill in the URL for your site in the Web Origin. For example:
  3. Check the 4 square disclosure boxes.
  4. You may also need to Sign In into Google.
  5. You will then see a screen like this:
  1. Copy the Token from that screen.
  2. In AppStudio Project Properties, go to ExtraHeaders and add this line:
<meta http-equiv="origin-trial" content="Avihurku4HHj...">
  1. Your app should work properly now.

Workaround 3. SQLite3 WASM (AppStudio 9)

A permanent solution is to include the SQLite3 library with your project. A library has been developed which provides the SQLite3 functionality for JavaScript.

AppStudio makes this easy. To enable it, select SQLite WASM in the Libraries section of your Project Properties:

If you're using AppStudio's Sql and SqlOpenDatabase, only your SqlOpenDatabase statement will need to be changed: your database name should be localStorage or sessionStorage. It is based on kvvfs. SqlImport and sqlExport are not supported yet.

DB = SqlOpenDatabase("localStorage")
DB = SqlOpenDatabase("sessionStorage")

The samples SQLSample1, SQLSample2 and SQLSample3 have been updated with to use SQLite WASM.

The data saved in localStorage is persistent. Data saved in sessionStorage is cleared when the page session ends.

The Sql function is now synchronous - meaning it executes completely before the next statement is executed. In most cases, this will make no difference to your code. We did find an error in one of our samples:

// No longer works as expected
  sqlList[0]=["SELECT orderno, customer FROM tabOrders;",showOrderSuccess, sqlErr]
  sqlList = []

// Proper way to do this
  sqlList = []
  sqlList[0]=["SELECT orderno, customer FROM tabOrders;",showOrderSuccess, sqlErr]

There are restrictions to keep in mind:

  1. The limit on localStorage is 10 megs (currently; on Chrome).
  2. You can only have one database. (2 if you can use sessionStorage - but it's not persistent)
  3. You cannot use SQLite WASM and native WebSQL at the same time.
  4. You will have to export your old database and import it to the new one yourself. There is no way to do this automatically.
  5. The library adds about 1.4 megs to your app.
  6. SQLImport and SQLExport are not supported yet.

This workaround continues to evolve and is subject to change.

Workaround 4. (under construction)