Geek Answers Handbook

SQLite or Blackfish - what should I use with a delphi application?

I am thinking about using SQLite

It is a standalone, server-wide, zero-configuration, transactional database engine SQL and is open source.

Will I get anything using Blackfish instead of SQLight?

+4
source share
5 answers

Why not Firebird?

http://www.firebirdsql.org

http://www.firebirdfaq.org

"... Firebird is a relational database that offers many standard ANSI SQL functions that run on Linux, Windows and various Unix platforms. Firebird offers excellent concurrency, high performance and powerful language support for stored procedures and triggers. It was used in production systems under different names since 1981 .... "

+10
source

Stick with FOSS (free open source software).

Both SQLite and Firebird are a great choice. Both meet your requirements. Both of them are very reliable, work with zero configuration and support.

Unaware of the intended use, Firebird will be my first choice, as it allows you to switch to Client Server deployment with effort close to zero and has a very reliable feature set. It is all about options.

IMHO Blackfish - not God's choice - "Blackfish SQL runs on both the .NET platform and the Java platform." - he said.

+6
source

Use SQLite.

Significantly less, less overhead, licensing issues, etc.

Laslty, only you can decide which one will do everything you need to work with the db system. Who has all the features that need to be supported?

John

+4
source

At first I will vote for Sqlite because it is compact, lightweight and fast, but depending on your application you can go with other options like Firebird or PostgreSql.

for example, Sqlite has a limit on one script at the same time, this may not be a problem for most desktop applications that are used by one user, but will not be scaled for more future use.

you can go with FireBird built in as a solution that will act like Sqlite and then go to the Firebird server when you need more users.

On the other side of the BlackFish database, you will force you to install the .NET infrastructure on your client machines, which is something bad IMO, especially if you need to distribute your application on the Internet, in addition, you will need a license when it scales to more than final version.

+3
source

Another thing to consider is how you are going to access your data. For example, if you use DBX4, it is very easy to change which database you are looking at. In this case, I would suggest trying both (plus any others that people strongly recommend that you try). On the other hand, if you use Interbase or ADO database access components, your ability to change is somewhat limited.

+2
source

More articles:


All Articles