3 ms·
It's not that you can't change the DB. Options could be: - collaborate more with any breaking changes - add features to the DB and keep backwards compatibilit
by micahdeath 5y ago
It's not that you can't change the DB. Options could be:
- collaborate more with any breaking changes
- add features to the DB and keep backwards compatibility
- use a DB View so it can be changed as needed and not affect other apps (most similar to an API)
- use Stored Procedures instead of direct table access as it gives more compatibility
- there are other methods too.
- cristaloleg 5y agoNice trick with stored procedures, I thought only about views. Agree, we can change the DB but if someone access the db with Postgres driver and after a month it's Mongo - user also must change the driver and this must be aligned, discussed and planned upfront.
- micahdeath 5y agoIf the table is copied somewhere else, you must also remember to update both copies when there is an update or other things can go out of sync. (Depends on what this table is and how often it can change if at all.)