← Blog

Product

Why every entity gets a real table

One table per entity and one column per field. What that means for reports, backups, speed and leaving.

When you create an entity in Qorekit, such as Customers or Tickets, Qorekit creates a database table for it. Each field you add becomes a column of the right type: a date is a date, an amount is a decimal, a link to a company holds the id of a row in the companies table.

Many no-code tools work differently. They keep every value of every record in one large table of “values”, which only the tool itself can make sense of. That is easier for the tool, and harder for you.

What real tables give you

Your data stays readable. Reporting tools, spreadsheets with a database connection and your own scripts can read the tables directly. A column called close_date holds dates, and a database client shows them as dates.

Backups are ordinary backups. Your hosting panel’s database backup, mysqldump or pg_dump already back up everything Qorekit keeps. Restoring needs nothing special.

Lists stay fast. The database can index and sort real columns. A list of a hundred thousand records opens a page at a time on ordinary shared hosting.

Leaving is easy. If you stop using Qorekit one day, your data is already in a usable shape, in tables named after your entities.

Changing a field changes the column

Fields change as the work changes. When you rename a field, make it required or give it a new type, Qorekit changes the column for you. Before it does, it shows what the change would do to the values already stored, and which of them it cannot convert.

That is the part a “values” table makes look easy, and the part that matters most once real data is in it.

You can see it in the public demo, or read how fields work in the guide.