New answers tagged

4 votes

Designing APIs that don't expose database primary keys

The fundamental problem with exposing the simple, surrogate keys which tend to be the database's Primary Keys is that it leaks your implementation outside of your database. If you have an API that [...
user avatar
  • 11.6k
0 votes

Picking data store for Location Tracking Based Application

My first thought is that you could use a time-series database, this could speed the operation of your second requirement (= Fetch the location of a device at any instant). PostgreSQL for example has ...
user avatar
2 votes

Mixing static referred and dynamic data in database

Putting limits on values for database identifiers can be problematic. Today, you think "surely 1000 static items will always be enough." But what happens when it isn't enough? Values 1-1000 ...
user avatar
0 votes

Database design - how to model database tables for similar objects - booleans / enums / inheritance / archived vs active

For your first question, it best to model that as an column on a table. Consider students; there are undergrads and grads. But they live in the same table because they share data attributes. In ...
user avatar
  • 10.6k
1 vote

Form builder app database design adding versioning

There are a variety of options with associated trade offs: Create a new explicit version of the form for each change - and snapshot each element of the form for each change. Lots of records, but ...
user avatar
  • 338

Top 50 recent answers are included