Special

Introducing the “Welcome to Xojo” Bundle!

New to Xojo and looking for guidance? We've put together a terrific bundle to welcome you! Xojo Bundle

This bundle includes six back issues of the magazine -- all of year 21 in printed book and digital formats -- plus a one-year subscription (beginning with 22.1) so you'll be learning all about Xojo for the next year. It's the perfect way to get started programming with Xojo. And you save as much as $35 over the non-bundle price!

This offer is only available for a limited time as supplies are limited, so hurry today and order this special bundle before the offer goes away!

Article Preview


Buy Now

Issue 9.3

COLUMN

Serving SQLite

Using SQLite as a Server

Issue: 9.3 (March/April 2011)
Author Bio: Paul Lefebvre has been using REAL Studio for nine years. His company, LogicalVue Software, specializes in creating database applications using REAL Studio. Paul also runs the RBDevZone community site and is a founding member of the Association of REALbasic Professionals.
Article Description: No description available.
Article Length (in bytes): 7,051
Starting Page Number: 78
Article Number: 9312
Related Web Link(s):

http://studiostable.com/Database
http://www.sqlabs.com/blog/?p=92
http://www.sqlite.org/wal.html

Excerpt of article text...

SQLIte is a wonderfully flexible database, but for most purposes it really is intended for use as a single-user database engine. But because of its speed and flexibility, it is also possible to use it as a server, if you're careful. This month we will look at using SQLite on a network, Studio Stable Database, CubeSQL Server, and SQLite Write Ahead Logging.

SQLite on a Network

Although not technically a server, you can put your SQLite database file on a shared network folder so that multiple clients can connect to it. This will decrease your performance, perhaps significantly, but can be useful for specific situations.

You'll have to code more carefully because SQLite only allows one client to write to the database at a time. You'll need to check for a database error whenever you write to the database (which you should be doing anyway) and possibly wait a short period and try to write again.

For applications that have a few clients connecting to the database or that are mostly read-only, this option can work reasonably well.

Studio Stable Database

...End of Excerpt. Please purchase the magazine to read the full article.