Choose your database:
AnySQL
MySQL
MS SQL Server
PostgreSQL
SQLite
Firebird
Oracle
SQL Anywhere
DB2
MaxDB

Subscribe to our news:
Partners
Testimonials
Marco De Luca: "I can handle now both version of SQLite Databases, 2.x and 3.x. Your SQLite PHP Generator is among the best tools I have seen".
Johnson Sieu: "Your PHP Generator is the BEST that I have used so far. It is affordable and user-friendly. Congratulation for coming up with such a fine product. I will not hesitate to introduce it to my peers".

More

Add your opinion

SQLite PHP Generator online Help

Prev Return to chapter overview Next

How to connect to SQLite

Connection properties

Specify the connection parameters for a database you want SQLite PHP Generator to work with.

 

Script connection properties

These parameters will be used by the generated web application. By default they are the same as parameters used by SQLite PHP Generator but you can change them if necessary. For example, if you are working with a remote database located at your web hosting and your database server and web server are installed on the same computer, you have to specify the value of the Host parameter as localhost.

 

 

As SQLite is implemented as an embedded database engine contained in a single DLL, SQLite databases usually are stored locally or in the shared folders. To connect to such database, you should provide only a full database file name (e.g. C:\Data\SQLite\MyDatabase.db3) and a password (only for encrypted databases).

 

To read and write encrypted databases, SQLite PHP Generator uses the free wxSQLite3 library that is included into the installation package. This means it can operate only with encrypted databases created by itself or by any other tool that uses the same library. Unfortunately, our software cannot connect to databases encrypted by any other library because different SQLite security extensions use different algorithms, which are not compatible with each other.

 

SQLite engine does not support network connections, however SQLite PHP Generator allows you to manage remote SQLite databases using the HTTP tunneling technique. For this purpose, you need to have a webserver running on a computer that stores the database file. Of course this webserver should be accessible from your workstation and you should be able to upload files there.

 

 More about connection via HTTP tunnel

 

To connect to a remote SQLite database using an HTTP tunnel, you need to:

 

1.Upload the connection PHP script to your website. The scripts are named sqlite_tunnel.php and sqlite3_tunnel.php for SQLite databases versions 2 and 3 accordingly and can be found under the installation folder, usually C:\Program Files\SQL Maestro Group\SQLite PHP Generator.

 

2.Turn ON the I have to use HTTP tunneling checkbox.

 

3.Enter the connection PHP script URL, e.g. www.yoursite.com/files/sqlite_tunnel.php. You can test the connection before the profile is created. Just use Test script using default browser to open connection script in your browser, enter all the required connection parameters and use the Test connection button.

 

 

4.In case using of a proxy server use Configure tunnelling options to open the HTTP tunnelling options window and specify your proxy server connection parameters and HTTP authentication.

 

Note 1. Do not forget to enable read/write permissions for a database file and read/write/execute permissions for the directory where the database file is stored.

 

Note 2 (only for SQLite 3 databases).  The webserver PDO_SQLite library must be compatible (not earlier in the most cases) with the library the database was created with. If they are not compatible, you will get an error message "Could not retrieve table list from _database_name_ ... " on getting a table list at the connection script. If you've got the message, check the PDO_SQLite library version using, for example,  the phpinfo() function, download a compatible library from the SQLite official website, get an SQL dump of the database and create a new one from the dump file with this library.

 



Prev Return to chapter overview Next