Support for SQLite - Revision history

Ghenne at 22:24, 26 January 2026

2026-01-26T22:24:35Z

← Older revision		Revision as of 22:24, 26 January 2026
Line 11:		Line 11:
	[[File:Libraries-SQLite WASM.png\|none\|500px]]		[[File:Libraries-SQLite WASM.png\|none\|500px]]

	If you're using AppStudio's [[Sql]] and [[SqlOpenDatabase]], only your SqlOpenDatabase statement will need to be changed: your database name should be localStorage to save your data between runs. It is based on [https://sqlite.org/wasm/doc/trunk/persistence.md#kvvfs kvvfs]~~. [[SqlImport]] and [[sqlExport]] are not supported yet~~.		If you're using AppStudio's [[Sql]] and [[SqlOpenDatabase]], only your SqlOpenDatabase statement will need to be changed: your database name should be localStorage to save your data between runs. It is based on [https://sqlite.org/wasm/doc/trunk/persistence.md#kvvfs kvvfs].
	<pre>		<pre>
	DB = SqlOpenDatabase("localStorage")		DB = SqlOpenDatabase("localStorage")

Ghenne at 15:15, 28 November 2025

2025-11-28T15:15:53Z

← Older revision		Revision as of 15:15, 28 November 2025
Line 1:		Line 1:
	Google has deprecated native SQlite, also referred to as WebSQL. They have been warning of this for a while. (If you're interested in why they did this, [https://groups.google.com/a/chromium.org/g/blink-dev/c/fWYb6evVA-w/m/pziWcvboAgAJ?pli=1 check out this post]).		Google has deprecated native SQlite, also referred to as WebSQL. They have been warning of this for a while. (If you're interested in why they did this, [https://groups.google.com/a/chromium.org/g/blink-dev/c/fWYb6evVA-w/m/pziWcvboAgAJ?pli=1 check out this post]).

	~~However,~~ SQLite can still be used, with the help of a library. There are a couple of methods.		SQLite can still be used with the help of a library. There are a couple of methods.

	=== 1. Use SQLite3 WASM to save to localStorage ===		=== 1. Use SQLite3 WASM to save to localStorage ===

Ghenne at 15:15, 28 November 2025

2025-11-28T15:15:21Z

← Older revision		Revision as of 15:15, 28 November 2025
Line 3:		Line 3:
	However, SQLite can still be used, with the help of a library. There are a couple of methods.		However, SQLite can still be used, with the help of a library. There are a couple of methods.

	1. Use SQLite3 WASM to save to localStorage ===		=== 1. Use SQLite3 WASM to save to localStorage ===

	You can include the SQLite3 libraries with your project. A [https://sqlite.org/wasm/doc/trunk/index.md library] has been developed which provides the SQLite3 functionality for JavaScript.		You can include the SQLite3 libraries with your project. A [https://sqlite.org/wasm/doc/trunk/index.md library] has been developed which provides the SQLite3 functionality for JavaScript.
Line 69:		Line 69:
	This workaround continues to evolve and is subject to change.		This workaround continues to evolve and is subject to change.

	Method 2. OPFS ===		=== Method 2. OPFS ===

	It's possible to use OPFS to save the database to an actual file, which removes the restrictions on database size and number. This is more complex than Method 1, and will not be described in detail here.		It's possible to use OPFS to save the database to an actual file, which removes the restrictions on database size and number. This is more complex than Method 1, and will not be described in detail here.

	If you're using OPFS, there are a couple of utilities which allow you to examine the database. [https://chromewebstore.google.com/detail/opfs-explorer/acndjpgkpaclldomagafnognkcgjignd?pli=1 OPFS Explorer] is a browser extension which can be used to save your database to your computer's file system as an SQLite database. [https://sqlitebrowser.org/ DB Browser for SQlite] is a standalone app which lets you create, search, and edit SQLite database files.		If you're using OPFS, there are a couple of utilities which allow you to examine the database. [https://chromewebstore.google.com/detail/opfs-explorer/acndjpgkpaclldomagafnognkcgjignd?pli=1 OPFS Explorer] is a browser extension which can be used to save your database to your computer's file system as an SQLite database. [https://sqlitebrowser.org/ DB Browser for SQlite] is a standalone app which lets you create, search, and edit SQLite database files.

Ghenne at 15:14, 28 November 2025

2025-11-28T15:14:37Z

← Older revision		Revision as of 15:14, 28 November 2025
Line 1:		Line 1:
	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 did this, [https://groups.google.com/a/chromium.org/g/blink-dev/c/fWYb6evVA-w/m/pziWcvboAgAJ?pli=1 check out this post]).		Google has deprecated native SQlite, also referred to as WebSQL. They have been warning of this for a while. (If you're interested in why they did this, [https://groups.google.com/a/chromium.org/g/blink-dev/c/fWYb6evVA-w/m/pziWcvboAgAJ?pli=1 check out this post]).

	~~Here is how to workaround:~~		However, SQLite can still be used, with the help of a library. There are a couple of methods.

	~~=== Workaround~~ 1. Use SQLite3 WASM to save to localStorage ===		1. Use SQLite3 WASM to save to localStorage ===

	~~This requires AppStudio 9.0.4 or later.~~		You can include the SQLite3 libraries with your project. A [https://sqlite.org/wasm/doc/trunk/index.md library] has been developed which provides the SQLite3 functionality for JavaScript.

	~~The solution is to~~ include the SQLite3 libraries with your project. A [https://sqlite.org/wasm/doc/trunk/index.md 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:		AppStudio makes this easy. To enable it, select SQLite (WASM) in the Libraries section of your Project Properties:
Line 71:		Line 69:
	This workaround continues to evolve and is subject to change.		This workaround continues to evolve and is subject to change.

	~~=== Workaround~~ 2. OPFS ===		Method 2. OPFS ===

	It's possible to use OPFS to save the database to an actual file, which removes the restrictions on database size and number.		It's possible to use OPFS to save the database to an actual file, which removes the restrictions on database size and number. This is more complex than Method 1, and will not be described in detail here.

	If you're using OPFS, there are a couple of utilities which allow you to examine the database. [https://chromewebstore.google.com/detail/opfs-explorer/acndjpgkpaclldomagafnognkcgjignd?pli=1 OPFS Explorer] is a browser extension which can be used to save your database to your computer's file system as an SQLite database. [https://sqlitebrowser.org/ DB Browser for SQlite] is a standalone app which lets you create, search, and edit SQLite database files.		If you're using OPFS, there are a couple of utilities which allow you to examine the database. [https://chromewebstore.google.com/detail/opfs-explorer/acndjpgkpaclldomagafnognkcgjignd?pli=1 OPFS Explorer] is a browser extension which can be used to save your database to your computer's file system as an SQLite database. [https://sqlitebrowser.org/ DB Browser for SQlite] is a standalone app which lets you create, search, and edit SQLite database files.

Ghenne: /* New Features and Notes */

2025-03-24T13:28:43Z

New Features and Notes

← Older revision		Revision as of 13:28, 24 March 2025
Line 26:		Line 26:
	1. <code>DB.clearStorage()</code> wipes out the database you created in localStorage.		1. <code>DB.clearStorage()</code> wipes out the database you created in localStorage.

	2. <code>DB.storageSize()</code> reports how localStorage you are using.		2. <code>DB.storageSize()</code> reports how much localStorage you are using.

	3. Compressing localStorage - The database in localStorage is updated whenever you update the database. However, garbage is not collected. You can clean it up (and save some space) by doing the following:		3. Compressing localStorage - The database in localStorage is updated whenever you update the database. However, garbage is not collected. You can clean it up (and save some space) by doing the following:

Ghenne at 12:28, 9 August 2024

2024-08-09T12:28:11Z

← Older revision		Revision as of 12:28, 9 August 2024
Line 1:		Line 1:
	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, [https://groups.google.com/a/chromium.org/g/blink-dev/c/fWYb6evVA-w/m/pziWcvboAgAJ?pli=1 check out this post]).		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 did this, [https://groups.google.com/a/chromium.org/g/blink-dev/c/fWYb6evVA-w/m/pziWcvboAgAJ?pli=1 check out this post]).

	Here is how to workaround ~~this~~:		Here is how to workaround:

	=== Workaround 1. Use SQLite3 WASM to save to localStorage ===		=== Workaround 1. Use SQLite3 WASM to save to localStorage ===

Ghenne: Ghenne moved page Using SQLite with Chrome 119 to Support for SQLite

2024-08-09T12:27:08Z

Ghenne moved page Using SQLite with Chrome 119 to Support for SQLite

← Older revision		Revision as of 12:27, 9 August 2024
(No difference)

Ghenne at 12:25, 9 August 2024

2024-08-09T12:25:47Z

← Older revision		Revision as of 12:25, 9 August 2024
Line 1:		Line 1:
	~~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, [https://groups.google.com/a/chromium.org/g/blink-dev/c/fWYb6evVA-w/m/pziWcvboAgAJ?pli=1 check out this post]).		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, [https://groups.google.com/a/chromium.org/g/blink-dev/c/fWYb6evVA-w/m/pziWcvboAgAJ?pli=1 check out this post]).

	Here is how to workaround this:		Here is how to workaround this:
Line 71:		Line 71:
	This workaround continues to evolve and is subject to change.		This workaround continues to evolve and is subject to change.

	=== Workaround 2. ~~(coming soon)~~ ===		=== Workaround 2. OPFS ===

	It's possible to use OPFS to save the database to an actual file, which removes the restrictions on database size and number.		It's possible to use OPFS to save the database to an actual file, which removes the restrictions on database size and number.

	If you're using OPFS, there are a couple of utilities which allow you to examine the database. [https://chromewebstore.google.com/detail/opfs-explorer/acndjpgkpaclldomagafnognkcgjignd?pli=1 OPFS Explorer] is a browser extension which can be used to save your database to your computer's file system as an SQLite database. [https://sqlitebrowser.org/ DB Browser for SQlite] is a standalone app which lets you create, search, and edit SQLite database files.		If you're using OPFS, there are a couple of utilities which allow you to examine the database. [https://chromewebstore.google.com/detail/opfs-explorer/acndjpgkpaclldomagafnognkcgjignd?pli=1 OPFS Explorer] is a browser extension which can be used to save your database to your computer's file system as an SQLite database. [https://sqlitebrowser.org/ DB Browser for SQlite] is a standalone app which lets you create, search, and edit SQLite database files.

Ghenne: /* Restrictions */

2024-08-09T12:21:06Z

Restrictions

← Older revision		Revision as of 12:21, 9 August 2024
Line 65:		Line 65:
	# Other databases will be cleared when the page is reloaded.		# Other databases will be cleared when the page is reloaded.
	# You cannot use SQLite WASM and Cordova plugins at the same time: Use SQLite WASM for desktop apps and a Cordova plugin for mobile apps.		# You cannot use SQLite WASM and Cordova plugins at the same time: Use SQLite WASM for desktop apps and a Cordova plugin for mobile apps.
	~~# You will have to export your old database and import it to the new one yourself. There is no way to do this automatically.~~
	# The library adds about 1.4 megs to your app.		# The library adds about 1.4 megs to your app.
	# ~~[[SqlImport\|SQLImport]] and SQLExport are~~ not ~~supported yet~~.		# You can test using '''Start in Desktop Browser''', but not '''Deploy to Local Folder'''.


	This workaround continues to evolve and is subject to change.		This workaround continues to evolve and is subject to change.

Ghenne: /* Workaround 2. (coming soon) */

2024-05-22T13:31:26Z

Workaround 2. (coming soon)

← Older revision		Revision as of 13:31, 22 May 2024
Line 73:		Line 73:
	=== Workaround 2. (coming soon) ===		=== Workaround 2. (coming soon) ===

	~~This will~~ use OPFS to save the database to an actual file, which removes the ~~restriction~~ on database size.		It's possible to use OPFS to save the database to an actual file, which removes the restrictions on database size and number.

	If you're using OPFS, there are a couple of utilities which allow you to examine the database. [https://chromewebstore.google.com/detail/opfs-explorer/acndjpgkpaclldomagafnognkcgjignd?pli=1 OPFS Explorer] is a browser extension which can be used to save your database to your computer's file system as an SQLite database. [https://sqlitebrowser.org/ DB Browser for SQlite] is a standalone app which lets you create, search, and edit SQLite database files.		If you're using OPFS, there are a couple of utilities which allow you to examine the database. [https://chromewebstore.google.com/detail/opfs-explorer/acndjpgkpaclldomagafnognkcgjignd?pli=1 OPFS Explorer] is a browser extension which can be used to save your database to your computer's file system as an SQLite database. [https://sqlitebrowser.org/ DB Browser for SQlite] is a standalone app which lets you create, search, and edit SQLite database files.