stability/reliability of the server backends is naturally inherited by Kexi too.

SQLite is a rock stable backend and format supporting transactions and locking it's heavily tested on all supported platforms and if we look closer, because its embedded nature, it is like a most used SQL engine in the world (have been a part of pre-HTML5, and is extremely popular on embedded/mobile systems and web browsers), data loss, if happens, can be most probably a logic error in Kexi than in SQLite if we're at this, I've not experienced data loss, and during 10 years of statistics, there are no bug reports at related to data loss clearly caused by the backend two examples:,.

Kexi does not implement any 'own' database backend.

Kexi isn't tied to one database backend, currently its primary support is SQLite, PostgreSQL and MySQL.

I'll throw in a number of facts that would help:

Any input on my concern from avid kexi users, and/or the developers would be very much appreciated. My question is, does Kexi suffer from a similar weakness as Base in its default single file configuration, or is the combination of Kexi/Sqlite simply better designed & implemented ensuring data integrity? I've searched through the forums here, but wasn't able to find much discussion on data loss or file corruption issues. Base by default has poor data integrity, and it's really only a matter of when you will lose data using it, rather than if.) Base uses a single file storage scenario by default as Kexi does, but they're using HSQL as their DB. (They refer to it as a split database format, which is not the default in Base.

Using Libreoffice Base as an example, the general consensus seems to be that you need to store data seperately from forms/queries,etc. It's my understanding that it stores everything in a single file, but I had always heard that storing them like that, in general, is inherently unstable. Hi, I have a question in regards to the way Kexi stores data & forms/queries.

Libreoffice base sqlite