How It Works

Configuring DBLX

DBLX is configured through the file This file is expected to be found in the same directory as the DBLX application, DLL, or JAR. The contents are self-explanatory, but let us know if you have any questions.

DBLX Databases and Tables

DBLX does not support multiple databases at this time. There is one database in DBLX that you add all your tables to.
DBLX creates one file for each database table.
DBLX will create table files in the following locations, based on the operating system:

Table files that end in .dat and .idat contain unencrypted table data.
Table files that end in .edat and .eidat contain encrypted table data.
Table files that end in .bak were tables that were dropped.
When a table is dropped it is not deleted and is saved to a .bak file. To add the dropped table back to DBLX, just rename the file without the .bak extension and restart DBLX.

ACID compliance

We are a small group of Old Programmers that does not make a dime on DBLX. We do not have the resources to pay a dubious and/or predatory company to certify that we are ACID compliant.
The short answer is that we believe we are ACID compliant. It was the goal from the start of the project and we have not made any intentional compromises so far.
Here are the tenants of ACID and how they apply to DBLX:

DBLX has been out almost 4 years now, and so far our ACID support has been solid.
The reality is that as more of our beloved users beat on DBLX from day to day, we will find out if our design is truly ACID compliant or not.