4 ms·

How bout adding composite primary key support....ARRRGHHH!!!

• run4yourlives 16y ago
  What major benefit (aside from legacy support) would this achieve that would be worth the effort?
  • jpeterson 16y ago
    ... Situations where use of a composite key is the correct design decision, maybe? Like the very common case of join tables, for example. Surrogate keys in these situations are wasteful and unnecessary. I find it seriously irritating when silly limitations like this in a framework corner you into bad data design.
    • ubernostrum 16y ago
      So... next time a feature-proposal window rolls around, go sign yourself up to work on composite-key support. That's pretty much how things get done :)
    • run4yourlives 16y ago
      I find it seriously irritating when silly limitations like this in a framework corner you into bad data design. Frameworks by their very definition are not meant to cover 100% of use cases. They cover the 80% of issues that can be solved without composite keys, or those where the overhead in not having the correct design is negligible. Perhaps in these cases you shouldn't be forcing the framework into a position it can't fit.
• hartror 16y ago
  SUCH an annoyance! I've had to put a custom hacks in place to allow interfacing with legacy databases! Nasty nasty stuff :(