On 7/1/13, Andrej Golcov <[email protected]> wrote: [...] > > I think that changing of tickets primary key to something like > id+produc_prefix (Alternative 2 in BPE-0010) is the best solution that > provides plugins backward compatibility and product-scoped numbering > as users would expect based on experience from Jira or Redmine. We > already have DB translator that emulates product scope in DB for > legacy API, so it should not be a huge change to simulate > auto-increment behaviour also. >
I second that , but just wanted to mention that , in case global ticket unique ID is actually needed then it should be possible to add it as well as a new autoinc column, though IMO should not be part of the PK . -- Regards, Olemis.
