What is the Best "Stand Alone" Database for lazarus

[kapibara]

@Thaddy Many apps using sqlite seem to put sqlite.dll in their program directory, probably to be sure the right version is always available. Isn't there a risk that your program stops working if you rely on a systemic sqlite.dll?

[Ñuño_Martínez]

Windows isn't Linux.

On Linux (may be because its part of the POSIX definition, so may be UNIX too) there's a convention that allows to install various versions of the same library by adding the version id to the library name; and using links you can define different levels of compatibility (i.e liballeg.so.4, liballeg.so.4.4 and liballeg.so.4.4.2 are actually the same library, and your application may use one or another depending of its tolerance to changes, so my Allegro.pas library uses liballeg.so.4.4 by default).

Windows doesn't has that convention so many developers decided to put the DLL files in the same directory than the application.  Fortunatelly, several developers have adopted the Linux way and added the version number to the DLL name.  For example SQLite library includes such number, but only the major number (sqlite3.dll).  Allegro includes two numbers (alleg44.dll/ allegro-5.2.dll).

[Thaddy]

@Thaddy Many apps using sqlite seem to put sqlite.dll in their program directory, probably to be sure the right version is always available. Isn't there a risk that your program stops working if you rely on a systemic sqlite.dll?

Windows programmers that work outside of Microsoft(as a company, inside)  itself tend to be not as carefull about reading specifications! as is required.
E.g. When windows 7 was introduced and enforced it broke a good many of applications.... And rightly so. Not MS fault, they documented that for years and years and years....
 Stupid developers. (including tooling companies that developed the tools.)

The correct answer is and always has been in the case of Windows: put your shared library somewhere under the windows directory, preferably in system32 or a sub.
And put writable data under users, not under ... well, too lazy to explain stupidity again....

[Graeme]

Define "Stand Alone" (MySQL can be regarded standalone as it doesn't have 3rd party dependency...

That choice would definitely fail the "best" criteria. Here are my reasons.

[Graeme]

Whatever you decide, avoid MS SQL with Lazarus (FPC).

Strange, I had no problems with a FPC based application talking to a MS SQL Server database. Either way, MS SQL Server would definitely not fit the original poster's criteria of "stand alone" (as in embedded).

[snorkel]

On windows I almost always put any DLLs I need in the application directory.  Windows first looks in the exe location for dlls, then the system folders.
I started doing this because the copies that where in the system folders for things like open SSL where always out of date and in a corp environment it was a pain to get them updated.  Obviously if a user is installing your app with a setup program they might not have the rights to install DLLS in program files along with the exe.
 

SQLite is a really good choice for an embedded database and you can statically link the C obj files I think( I know it could be done on Delphi for sure)
SQLite also has a WAL mode that can give pretty good concurrency.

[tatamata]

You could also try ZMSQL.
ZMSQL has no external dependencies and is pure Pascal database (https://sourceforge.net/projects/lazarus-ccr/files/zmsql/).
It is included in CodeTyphon Lazarus distribution by default (see http://www.pilotlogic.com/sitejoom/index.php).

[JD]

Looking for a Database that run inside the program and does not depend on a server or client software running.

Where the user, or my install program, does not have to have to install any other software, Mysql, Firebird, etc.

Light weight, few users or one user.

This is what I define as "Stand Alone".

I am coming back to Pascal after many years of being away from programming, so I am trying to get caught up, and find out what is in Lazarus?

Unless you are absolutely certain that you'll never have more than one user at a time, I would suggest biting the bullet & using Firebird Embedded. That way if in the future you need to move to multiple users, all you'll need to do is install the server version of Firebird & your app will continue to run normally. User needs evolve, plan for multiple users especially where databases are concerned.

JD

[Thaddy]

@Thaddy Many apps using sqlite seem to put sqlite.dll in their program directory, probably to be sure the right version is always available. Isn't there a risk that your program stops working if you rely on a systemic sqlite.dll?

Well. That's not where  shared libraries belong and a dll is a shared library as per design and specification and not a moronic way to let your executable look smaller.......

That's developer stupidity.

Hence I often choose to link  Sqlite statically! Solved.
(Some wtf and shouting involved when writing this)   

It is over 40 degrees C in my garden. So it is provocative by default for lack of ice cubes.

[kapibara]

As long as you take responsibility for the right lib is available, do what you find best. Beside that, the DLL is just like people, its is what it does.