3 ms·
"the ORM didn't support composite keys" Well composite keys are a bad idea, so maybe it had a reason for that.
by SoftTalker 2y ago
"the ORM didn't support composite keys"
Well composite keys are a bad idea, so maybe it had a reason for that.
- wvenable 2y agoComposite keys are fine as long as all the key columns are surrogate keys.
- SoftTalker 2y agoHigh bridges without guardrails are fine as long as you don't fall off.
- wvenable 2y agoUsing composite keys can help prevent you from representing invalid states in the database or in your application. They can be guardrails.
- TOGoS 2y agoIf an ORM can't be used to access a valid database, then that ORM sucks. (ORMs often suck for additional reasons, but that one's pretty hard to ignore if you have an existing database that you need to interact with.) There are perfectly valid uses for composite keys. In a table that indicates a relationship between multiple other objects, for example.