3 ms·
As a consultant/free-lancer I've seen this in plenty of SaaS businesses, even if they only have one product. The DB url would be "product-name.db.domain.tld/pro
by capableweb 4y ago
As a consultant/free-lancer I've seen this in plenty of SaaS businesses, even if they only have one product. The DB url would be "product-name.db.domain.tld/product-name", the database would be named "product-name" and the table would be called "product_name_users". Not really sure how it came to be, but it's not super uncommon.
For products built by outsourced teams (or if initial prototype was built by a outsourced team but then taken over by in-house), it's more common, even when building products for others.
- larsnystrom 4y agoPrefixing table names with the app name is a simple way of letting multiple apps share the same database. Sharing the same database used to be really common, almost standard I’d say, when deploying on low-cost web hosts and also locally when working on multiple projects. I don’t let apps share databases anymore, but I still usually prefix table names anyway. Old habits die hard I guess, and for most ORMs it’s usually just a single config switch anyway.
- neurostimulant 4y agoNothing strange about it. ORMs like Django name their tables <app name>_<model name> by default.