Summary: | Add support for creating multi-column primary key | ||
---|---|---|---|
Product: | [Applications] KEXI | Reporter: | Jaime Torres <jtamate> |
Component: | Tables | Assignee: | Kexi Bugs <kexi-bugs> |
Status: | CONFIRMED --- | ||
Severity: | wishlist | CC: | marko.kn, xanas3712 |
Priority: | NOR | ||
Version: | 3.0.x | ||
Target Milestone: | --- | ||
Platform: | Compiled Sources | ||
OS: | Linux | ||
Latest Commit: | Version Fixed In: | ||
Sentry Crash Report: | |||
Bug Depends on: | |||
Bug Blocks: | 264392 |
Description
Jaime Torres
2011-07-09 21:07:59 UTC
I think this behaviour is intentional and should not be changed. It corresponds to the common definition of a primary key. According to Wikipedia, "A table can have at most one primary key, but more than one unique key." If you have a special usecase where you would want to use more than one primary key I suggest you ask in the forums how to do that in Kexi - I think there will be a way to do it which does not involve multiple primary keys. The current behaviour is intentional. That said, compound keys [1] will eventually come to Kexi in a form of dedicated option, so this report has been set as a Wishlist and marked as NEW. Good thing is that SQLite somewhat supports them (but I not tested this feature heavily): "Optionally, a PRIMARY KEY for the table. Both single column and composite (multiple column) primary keys are supported." [2] Also, relates to Bug #249966 - "Add composite primary keys support for many-to-many relationships" [1] http://en.wikipedia.org/wiki/Compound_key [2] http://www.sqlite.org/lang_createtable.html Sorry for my poor English. I did not know how to say "composite primary keys". Until I'm able to create one-to-many or many-to-many relationships with Kexi, I can not replace Acc... with Kexi. Jaime, I see and understand your need, we're both users too. Please don't be afraid of sharing more needs as wishlists using this web site :) *** Bug 144841 has been marked as a duplicate of this bug. *** |