One part of my program fetches data from many tables and columns in my database for processing. Some of the columns might be null
, but in the current processing context that is an ..
Tag : database-design
I’m defining a DB structure, and I have a strong feeling I’m not doing it right. I have hotels that can be configured to offer some optional services (airport pickup, massage), that can in turn be booked with a room. So, each hotel picks which services it offers and the price. Currently I have the following tables (simpli..
In postgres, I need to store the hours a merchant is open each week. Essentially, the information you’d see posted on a sign in the merchant’s..
Closed 5 years ago
I am designing a database for a document management app for my office. I want to get the backend right so I don’t have issues in the future. Basically all users will be categorized into roles e.g, super admin, admin, staff and interns. All documents will have access restrictions e.g public(all user roles can view the document), private (only user who created it can view), role-based(this means only users with the same roles can view these documents). However, Admins and super admins can view all documents. One user can have many documents. Also user roles can be updated e.g from staff to admin etc. I will be using Postgres with Sequelize as my ORM for this project. Based on the description above, is this a good design? What can be improved? Any inputs will be appreciated.
I want to create an app using MongoDB (NoSQL database) that allows people to vote on posts (simillar to Reddit). What’s the recommended way to store votes for the ..
I am diving in the domain driven design (DDD) and while I go more deeply in it there are some things that I don’t get. As I understand it, a main point is to split the Domain Logic (Business Logic) from the Infrastructure (DB, File System, ..
I have a multiple same tables (14 for now), with a only foreignKey
column difference. Some of the..
It’s common to implement optimistic concurrency control in DynamoDB by giving each item in the database a top-level “version” attribute and only allowing an update of an item to succeed if the current version matches the expected version (see https://docs.aws.amazon.com/amazondynamodb/latest/developerguide/DynamoDBMapper.OptimisticLocking…