<br><br><div class="gmail_quote">On Wed, Aug 19, 2009 at 2:51 AM, Maciej (Matchek) Blizinski <span dir="ltr"><<a href="mailto:maciej@opencsw.org">maciej@opencsw.org</a>></span> wrote:<br><blockquote class="gmail_quote" style="border-left: 1px solid rgb(204, 204, 204); margin: 0pt 0pt 0pt 0.8ex; padding-left: 1ex;">
Hello,<br>
<br>
I'm working on some web code with relation to the packages database.<br>
I'd like to ask for few minor changes to the database schema. It boils<br>
down to creating an autoincremented primary key to tables in which<br>
rows are identified by a tuple of two columns. The reason for a change<br>
is that the framework I'm using doesn't support composite primary<br>
keys.<br>
....<br>
Is it okay to apply those changes to the packages database?<br>
</blockquote><br>
<br>
<br>
If you want a unique primary key, you should be using the mantis project id number, which exists already.<br>
the internal "package database" is sort of a convenience thing. canonical ownership is what mantis says.<br>
<br>
Sounds like you and I should have a more in-depth technical discussion. Please tell me more about what you are trying to do.<br>
<br>
I'm also wondering what kind of "framework" you are using,that somehow limits you about choice of keys.<br><br></div><br>