> What is your use case ? I'm genuinely interested as I'm advocating > composite key support myself :)
If you're advocating it then you probably won't need to know any further arguments since you've already understood the issue yourself: That data integrity is what counts. And without composite keys, that can't work for any non-trivial application that requires a thoroughly normalised schema of significant complexity, since proper unification of records in such a schema requires composite keys. One of the issues that's practically impossible to solve with surrogate keys is explained in database design textbooks under the title "overlapping foreign keys". In my case, I'm specifically using an industry standard data model that has been in continuous development (by a non-profit organisation, in cooperation between domain expoerts and database design experts) and use for over a decade now. It's currently at >400 entities and growing. For the length of the primary keys, I stopped counting at 15 columns or so. Sincerely, Wolfgang -- -- [email protected] mailing list --- You received this message because you are subscribed to the Google Groups "tryton" group. To unsubscribe from this group and stop receiving emails from it, send an email to [email protected]. For more options, visit https://groups.google.com/groups/opt_out.
