3 ms·

i really dont get this the entire point of design time is to understand and design your data first.

• chipdart 2y ago
  > the entire point of design time is to understand and design your data first. What's hard to understand? You design a data store to store data, and aggregate data is still data. Do you care about low-level details of an aggregate data type? Do you care about how a UUID is implemented, or even if you store it as a string, a 128 bit integer, or a bitmap? Do you care if you store the UUID type along with the UUID? Or do you simply want to store an ID that's produced/consumed by a client? Now, replace UUID with JSON and you arrive at the same conclusion.
  • sigmonsays 2y ago
    i do care i care about how data is stored. There are limits to every data type and time spent on that in the beginning is time gained down the road
    • chipdart 2y ago
      I'm not sure you understand why your comment makes no sense in the context of SQLite, as under the hood it stores most data types as text strings, whereas it supports storing JSON as JSONB. https://sqlite.org/draft/jsonb.html https://sqlite.org/draft/jsonb.html Therefore, even if you had any remotely relevant reason for that fundamentalism, storing JSON documents in SQLite does more to meet that personal arbitrary goal than storing it in tabular form.