Use case: There is a table called release with a primary key id of type integer and an additional column name (the release name). And further tables (e.g. table_x, table_y, …) with a reference (foreign key) to release.id. The working tables are table_x, table_y, a.s.o. and the selects have to be ordered by the foreign key release.id. An ordering by release.name is not possible because of arbitrary release names that are not sortable.
To the discussion that primary keys should not be changed can I say that this use case is not like a change of the release primary key but more like a movement of primary keys/releases and their referenced data to insert a new release and get the desired order.
Why is it useful?
|Who would benefit from this IDEA?||Who knows? We!|
How should it work?
The concrete example to understand it better:
create table release (
Proposed solution: Support for ON UPDATE CASCADE by column references. Other database systems supports it, like Postgresql.
|Priority Justification||Informix is not usable for the planned application.|
|Customer Name||Axians ICT Austria GmbH|
NOTICE TO EU RESIDENTS: per EU Data Protection Policy, if you wish to remove your personal information from the IBM ideas portal, please login to the ideas portal using your previously registered information then change your email to "email@example.com" and first name to "anonymous" and last name to "anonymous". This will ensure that IBM will not send any emails to you about all idea submissions