Databases
StackOverflow2013
Postsdbo
PO
 

Note that there are some explanatory texts on larger screens.

plurals
  1. PO
    primarykey
    data
    text
    <p><strong>Update (see previous version below):</strong></p> <p>With both your solution and my previous version there is actually the problem that not all information from your array structure is saved. You can still avoid <code>api.scopes.1</code> by putting the last element of the option name in a separate field. If you combine this with soft deletion, you can use <code>INSERT ... ON DUBLICATE UPDATE</code>.</p> <pre><code>+----------+-------------------+---------------+------------------+---------+ | user_id* | config_group* | config* | value | deleted | +----------+-------------------+---------------+------------------+---------+ | 1 | user | is_developer | 1 | 0 | | 1 | user | api_access | 1 | 0 | | 1 | api.scopes | 1 | astro | 0 | | 1 | api.scopes | 2 | user_info | 0 | | 1 | api | default_scope | user_info | 0 | | 1 | astro | location_id | 12345 | 0 | | 1 | astro | timezone | America/New_York | 0 | | 1 | astro.coordinates | latitude | 12.22 | 0 | | 1 | astro.coordinates | longitude | 24.44 | 0 | +----------+-----------------------------------+------------------+---------+ * marks key columns </code></pre> <p><strong>Previous version:</strong></p> <p>If you split your data in two tables you can use a unique key for each of them.</p> <p>The first table contains all config options which take on a single value (* marks key columns):</p> <pre><code>+----------+-----------------------------+------------------+ | user_id* | config* | value | +----------+-----------------------------+------------------+ | 1 | user.is_developer | 1 | | 1 | user.api_access | 1 | | 1 | api.default_scope | user_info | | 1 | astro.location_id | 12345 | | 1 | astro.timezone | America/New_York | | 1 | astro.coordinates.latitude | 12.22 | | 1 | astro.coordinates.longitude | 24.44 | +----------+-----------------------------+------------------+ </code></pre> <p>The second table contains all options which consist of a set of values (with no dublicates; * marks key columns):</p> <pre><code>+----------+-----------------------------+------------------+ | user_id* | config* | value* | +----------+-----------------------------+------------------+ | 1 | api.scopes | astro | | 1 | api.scopes | user_info | +----------+-----------------------------+------------------+ </code></pre> <p>Thus you can use your database to ensure data integrity. <code>INSERT ... ON DUBLICATE UPDATE</code> works naturally with the first table. You can also use it with your second table if you are willing to use soft delete:</p> <pre><code>+----------+-----------------------------+------------------+---------+ | user_id* | config* | value* | deleted | +----------+-----------------------------+------------------+---------+ | 1 | api.scopes | astro | 0 | | 1 | api.scopes | user_info | 0 | | 1 | api.scopes | old | 1 | +----------+-----------------------------+------------------+---------+ </code></pre>
    singulars
    1. This table or related slice is empty.
    1. POSaving array data in normalized table
      singulars
      1. PTQuestion
    1. PTAnswer
    1. USunique2
    1. USunique2
    plurals
    1. This table or related slice is empty.
    1. This table or related slice is empty.
    1. This table or related slice is empty.
    1. This table or related slice is empty.
    1. VO
      singulars
      1. PO
      1. This table or related slice is empty.
      1. VTUpMod
    1. COThanks for the comment, but splitting values over two tables does not seem to be a good solution. It will make CRUD operations unnecessarily complicated. Further, api.scopes might have a single value one time, multiple values next time. Which means I will have to check both tables, for each operation.
      singulars
      1. PO
      1. USJoyce Babu
    2. CO`api.scopes` should always be in the second table, since it is *allowed* to have more then one value, while this wouldn't make sense for `user.is_developer`. This assumes you know beforehand in which categories a config belongs to.
      singulars
      1. PO
      1. USunique2
 

Querying!

 
Guidance
A row detail

Detail views are divided into sections. All the information in the data section comes from columns in the selected row. The other sections display data from other, related rows.

Related data can be related in a to-one or a to-many fashion. Captions of data related in a to-many fashion link to a list view showing a filtered view of the table.

Try moving around until you find a non-empty to-many entry and click on the label to get to one. You can move back to the root by clicking on the database name in the header.

SQuiL has stopped working due to an internal error.

If you are curious you may find further information in the browser console, which is accessible through the devtools (F12).

Reload