Why Aren't You Using SQLite?

[weirdo12 19]

If you are building a stand alone app that relies on a database, why aren't you using SQLite?

 

We used to use SQL Anywhere as our default database. It was great. The database could be one file that you could copy and move very easily. Like SQLite. But it did have an engine to install which could be done easily with InnoSetup without a separate exe included in the setup file (think SQL Server whatever). We did have have to pay for each install which was fine. But then it was sold to SAP and you know what, they just stopped asking us for royalties. I guess it was so small time they couldn't be bothered.

 

So like 6-7 years ago I thought I'd see if I could use SQLite as a replacement. And it was possible. Obviously the database would work. The issue was with stuff stuff that was done in database - triggers - that we used and could they be done in SQLite. They could be.

Edited 22 hours ago by weirdo12

[Brian Evans 102]

I started with FlashFiler then migrated to NexusDB for both standalone and C/S versions of applications. The former was available years before SQLite came on the scene and the latter was the spiritual successor of the former. Never migrated to SQLite because using C/S tooling during development of even a standalone application makes things easier. Both a database development tool like Upscene Production's Database Workbench and the application itself can access the live database tables at the same time easing debugging and other tasks. Can then ship the application with the same database engine compiled into the EXE but hooked up directly instead of through C/S components. 

 

Originally used FlashFiler as the database engine for an application + database published monthly on a CDROM. With some modifications to the source to open read-only files as shared it worked well for years. Both FlashFiler and NexusDB are royalty free so no per user fees in either standalone or C/S configurations. 

[Der schöne Günther 312]

I am using Sqlite exclusively, because I don't know anything else.

[Markus Kinzler 173]

FireBird (embedded) would be a futher option. The same database file can be used in the server and embedded (client) edition. Triggers are fully supported.

[DelphiUdIT 153]

Normally I always use SQLite as a base for all my applications (configurations, settings and more are kept inside). Then depending on the customer, additional databases such as MSSql, MySql, Firebird are used in addition, but with the server managed by the customer. However, the use of databases in addition to SQLite is sporadic, many customers want to have the data in an open format of pure text such as a CSV file.

[corneliusdavid 197]

SQLite's own documentation lists some reasons why using it might not be the best for every situation.

11 hours ago, weirdo12 said:

building a stand alone app that relies on a database

That's a pretty broad question and could mean anything from a small single-person app with a few records in a couple of tables (where SQLite would be perfect) to a large, multi-user application suite with hundreds of users over a large network with thousands of transactions per minute (where SQLite would be quite inadequate).

[weirdo12 19]

29 minutes ago, corneliusdavid said:

a small single-person app

Okay, then let's go with that description if stand alone isn't clear enough.

[corneliusdavid 197]

2 minutes ago, weirdo12 said:

if stand alone isn't clear enough.

To me, "stand alone" means it's not a plug-in for something else. So, yeah, could be large or small. Thanks for the clarification. :-)