Using SQLite - Revision history

Ghenne: /* Asynchronous Results */

2025-11-28T15:25:42Z

Asynchronous Results

← Older revision		Revision as of 15:25, 28 November 2025
Line 28:		Line 28:

	NB: If on this property only the database name is specified that should be included with the application, any changes made during the application run, whilst they will be reflected in your application, the problem is that the next time you start the application, all your updates will not exist.		NB: If on this property only the database name is specified that should be included with the application, any changes made during the application run, whilst they will be reflected in your application, the problem is that the next time you start the application, all your updates will not exist.

	~~=== Asynchronous Results ===~~

	The results of calls to the database are returned asynchronously. That means that after a statement involving the database is executed, the next statement in the program is executed - even though the database operation may not be complete. The database operation continues on its own. When it finishes, it will call a function you specify in your program, depending on the success or failure of the operation. In the meantime, you can do other processing: update controls on the screen or do calculations.

	~~Consider the following code:~~

	~~MsgBox "Before doing call"~~
	~~sqlList="CREATE TABLE myData('name', 'age')"~~
	~~sql(DB, [sqlList, Success_Function, Fail_Function])~~
	~~Msgbox "After doing call"~~

	~~Function Success_Function(transaction, result)~~
	~~Msgbox "Success - result received"~~
	~~End function~~

	~~Function Fail_Function(transaction, result)~~
	~~Msgbox "Fail"~~
	~~End function~~

	~~The result will be 3 messages, in this order:~~

	~~"Before doing call"~~
	~~"After doing call"~~
	~~"Success - result received"~~

	=== Transactions ===		=== Transactions ===

Ghenne: /* Complete Sample */

2024-08-30T14:52:41Z

Complete Sample

Show changes

Ghenne: /* Complete Sample */

2024-08-30T14:47:32Z

Complete Sample

← Older revision		Revision as of 14:47, 30 August 2024
Line 279:		Line 279:
	End Function		End Function
	</pre>		</pre>

			==== Debugging ====

			Use the [[SQLDump]] command in the Chrome Console to see the contents of a database table.

			[[File:Screenshot 2024-06-03 at 7.44.40 AM.png]]

Ghenne at 14:12, 28 August 2024

2024-08-28T14:12:13Z

← Older revision		Revision as of 14:12, 28 August 2024
Line 279:		Line 279:
	End Function		End Function
	</pre>		</pre>

	~~=== Clearing a Locally-Deployed App Incorporating an SQLite Database From a PC ===~~

	Clearing a remotely-deployed app's data and SQLite DB from a browser simply involves clearing the browser's cached app data or content for that app's domain via the settings panel. However, for a locally-deployed app the process is more involved because the various pieces are stored in multiple locations on the PC.

	~~Here's a way to eliminate all traces of a locally-deployed app so that it will behave as a freshly installed app on the next deploy:~~

	1. In Chrome Debugger's console, with the app currently deployed locally, delete all localStorage variables with the localStorage.clear() command. Use the Resources tab, Local Storage, file:// to confirm success.

	~~2. Find the special location where Windows stores SQLite (and other) databases and delete that folder with its contents:~~

	* Windows 7+: \Users\_username_\AppData\Local\Google\Chrome\User Data\Default\databases
	* Mac OS X: ~/Library/Application Support/Google/Chrome/Default/databases
	* Linux: ~/.config/google-chrome/Default/databases

	3. Delete the app files themselves (html, /nsb folder, etc.) from the Windows system. The location for these is found in the URL/Address window of the Chrome browser itself. Just drill down using the file explorer and delete the temp folder being used.

	~~''Contributed by c185driver''~~

Ghenne: /* Using the Chrome Debugger to examine databases */

2024-08-28T14:11:11Z

Using the Chrome Debugger to examine databases

← Older revision		Revision as of 14:11, 28 August 2024
Line 279:		Line 279:
	End Function		End Function
	</pre>		</pre>

	~~=== Using the Chrome Debugger to examine databases ===~~

	By opening the Chrome Debugger and using the Resource Tab, you can examine the database. The following example shows a database named customers with a single record containing John Doe's name, age and sales:

	~~[[File:Sqldebugger.png]]~~

	=== Clearing a Locally-Deployed App Incorporating an SQLite Database From a PC ===		=== Clearing a Locally-Deployed App Incorporating an SQLite Database From a PC ===

Ghenne: /* Platforms Supported */

2024-08-28T14:01:09Z

Platforms Supported

@@ Line 19: / Line 19: @@
 SQLite is supported on all iOS and Android devices. It is in Chrome, Safari and Brave. It is not supported by other browsers, such as Internet Explorer, Edge or Firefox.
 To include the SQLite libraries in web apps, enable SQLite WASM in your [[https://wiki.appstudio.dev/Toolbox|project's libraries]]. If you're making a native app, use the Cordova plugin for SQLite.
 === Persisting Updates to the Database ===

Ghenne: /* Platforms Supported */

2024-08-28T13:59:54Z

Platforms Supported

← Older revision		Revision as of 13:59, 28 August 2024
Line 17:		Line 17:
	=== Platforms Supported ===		=== Platforms Supported ===

	SQLite is on all iOS and Android devices. It is in Chrome, Safari and Brave. It is not supported by other browsers, such as Internet Explorer, Edge or Firefox.		SQLite is supported on all iOS and Android devices. It is in Chrome, Safari and Brave. It is not supported by other browsers, such as Internet Explorer, Edge or Firefox.

			To include the SQLite libraries in web apps, enable SQLite WASM in your [[https://wiki.appstudio.dev/Toolbox\|project's libraries]]. If you're making a native app, use the Cordova plugin for SQLite.

	To test if SQLite is supported, use this code:		To test if SQLite is supported, use this code:

Ghenne at 12:29, 9 August 2024

2024-08-09T12:29:47Z

← Older revision		Revision as of 12:29, 9 August 2024
Line 1:		Line 1:
	(~~Note: as we transition to~~ SQLite ~~WASM, the information on this page will change~~. See [[Using_SQLite_with_Chrome_119\|~~Using~~ SQLite ~~WASM~~]] for the latest information.)		(The implementation of SQLite was changed by Google in 2024. See [[Using_SQLite_with_Chrome_119\|Support for SQLite]] for the latest information.)

	SQLite is a fast, popular and easy to use database. Its speed and easy of use make it a practical choice for use when you need an indexed file system for an app. Databases you create can be accessed, without change, on any platform SQLite supports. It is built into mobile devices that AppStudio supports.		SQLite is a fast, popular and easy to use database. Its speed and easy of use make it a practical choice for use when you need an indexed file system for an app. Databases you create can be accessed, without change, on any platform SQLite supports. It is built into mobile devices that AppStudio supports.

Ghenne at 14:49, 28 April 2024

2024-04-28T14:49:58Z

← Older revision		Revision as of 14:49, 28 April 2024
Line 1:		Line 1:
			(Note: as we transition to SQLite WASM, the information on this page will change. See [[Using_SQLite_with_Chrome_119\|Using SQLite WASM]] for the latest information.)

	SQLite is a fast, popular and easy to use database. Its speed and easy of use make it a practical choice for use when you need an indexed file system for an app. Databases you create can be accessed, without change, on any platform SQLite supports. It is built into mobile devices that AppStudio supports.		SQLite is a fast, popular and easy to use database. Its speed and easy of use make it a practical choice for use when you need an indexed file system for an app. Databases you create can be accessed, without change, on any platform SQLite supports. It is built into mobile devices that AppStudio supports.

Ghenne: /* Create a table in the database */

2021-02-01T20:45:41Z

Create a table in the database

← Older revision		Revision as of 20:45, 1 February 2021
Line 123:		Line 123:
	sqlList=[]		sqlList=[]
	sqlList[0]=["DROP TABLE customerData;",,skipError]		sqlList[0]=["DROP TABLE customerData;",,skipError]
	sqlList[1]=["CREATE TABLE customerData('name', 'age', 'sales', PRIMARY KEY('name') );"]		Sql(DB, sqlList)

			sqlList=[]
			sqlList[0]=["CREATE TABLE customerData('name', 'age', 'sales', PRIMARY KEY('name') );"]
	Sql(DB, sqlList)		Sql(DB, sqlList)