db-torque-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Thomas Fischer (JIRA)" <j...@apache.org>
Subject [jira] Reopened: (TORQUE-128) remove autoIncrement attribute of column element
Date Fri, 10 Sep 2010 08:46:32 GMT

     [ https://issues.apache.org/jira/browse/TORQUE-128?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]

Thomas Fischer reopened TORQUE-128:
-----------------------------------


There is no problem on tables with composite primary key where none of the columns are automatically
generated (set idMethod to none on table). This is the most common use case (e.g. the m:n
table use case).

However, in the case of a composite key where only one column is autoincremented and the others
are fixed, I now see that functionality is lost. This seems a rather exotic use case and on
mysql does not do what I'd expect (see http://dev.mysql.com/doc/refman/5.0/en/example-auto-increment.html)

But even if we decide to keep the functionality, the flag should not be called autoincrement
but also idMethod in my eyes. The name is most confusing on systems which do not use autoincrement
but sequences. But I see the problem that it breaks backwards-compatibility for no compelling
reason.

Please state your opinions on how to proceed.

> remove autoIncrement attribute of column element
> ------------------------------------------------
>
>                 Key: TORQUE-128
>                 URL: https://issues.apache.org/jira/browse/TORQUE-128
>             Project: Torque
>          Issue Type: Sub-task
>    Affects Versions: 4.0
>            Reporter: Thomas Fischer
>             Fix For: 4.0
>
>
> In the 3.3 schema, the id method for a column is determined by the idMethod attribute
of the table, the defaultIdMethod attribute of the database and the primaryKey attribute of
the column. This is sufficient for determining the idMethod.
> However, in the 3.3 schema, there is still the autoIncrement attribute which kind of
overrides the settings outlined above. There is no such equivalent for sequence generation,
thus the attribute is bad for database interoperability.
> Therefore I'd suggest to remove this attribute with no replacement. The consequence would
be that it would no longer be possible to have auto_increment on columns which are no primary
key (but again, torque supports no such feature for sequence generation).

-- 
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.


---------------------------------------------------------------------
To unsubscribe, e-mail: torque-dev-unsubscribe@db.apache.org
For additional commands, e-mail: torque-dev-help@db.apache.org


Mime
View raw message