Multiple key columns lead to data corruption or data loss

Description

None

Environment

I selected two primary keys in table. See the pictures.

Attachments

6

Activity

Show:

Carlos Ruiz February 14, 2019 at 6:10 PM

Hi , yes, a wiki collecting potential inconsistencies sounds good.

However, this specific case is unlikely in a prod database, the data problem would have been discovered early on any test. But if you want to document it that sounds fine.

Regards,

Carlos Ruiz

Hiep Lq February 14, 2019 at 5:57 PM

hi , maybe we create a wiki page to note all modify like this one.

it help people can verify old database and correct it follow that change

example this one, can add a note and a query to find out table have more than one column is key

Anna Fadeeva December 7, 2013 at 5:21 PM

OK, Carlos.
I think that better change the subject on this.

Carlos Ruiz December 7, 2013 at 5:09 PM

Anna, just one column can be key column, to define a composite primary key you need to define all columns as parent key and do not define a key column for that table.

I think is worthy to open a bug (or change the subject on this) to add a validation to forbid multiple key columns.

Regards,

Carlos Ruiz

Fixed

Details

Assignee

Reporter

Labels

Components

Fix versions

Affects versions

Priority

Created December 7, 2013 at 10:07 AM
Updated April 1, 2019 at 2:53 PM
Resolved February 14, 2019 at 3:56 PM