PKs set always as unique (BUG?)

[sargasso]

Buggerus meus. I non comprende (conprehenamo ), you Pseudonaja affinis

bruce

[Martin Terreni]

I failed to exaplain my self again - When I makr several clumns as PKs (the only way in EA to create concatinated key) they are marked as unique and there is no way to change it - BUG!!!!

[sargasso]

I am actually going to shut up here, because I feel you (two) may be right and I am not going to upgrade beyond 6.7 until this is fixed!!!

bruce

[«Midnight»]

I failed to exaplain my self again - When I makr several clumns as PKs (the only way in EA to create concatinated key) they are marked as unique and there is no way to change it - BUG!!!!

I submitted a report of something similar to this during the final beta. No apparent change.

[Martin Terreni]

Thanks, i also opened a bug.

[Thomas Mercer-Hursh]

Can one vote for bug resolutions or enhancements?  Multiple fields participating in a single primary key is very characteristic of the legacy applications with which I deal.  In fact, no guarantee that even the field combination is necessarily unique in all cases (no, these are not my designs!)

[Martin Terreni]

Don't know how, but I'll bug them a little...

[Paolo F Cantoni]

Can one vote for bug resolutions or enhancements?  Multiple fields participating in a single primary key is very characteristic of the legacy applications with which I deal.  In fact, no guarantee that even the field combination is necessarily unique in all cases (no, these are not my designs!)

This is the point of exposing the bug reports/feature requests via the forum.  The Sparxians can see a wide range of opinion and get a better appreciation of how the user community feels of the various topics.  Sometimes, like in this thread, it's also possible to explorer some of the more theoretical aspects of the problem.

Paolo

[KP]

When I makr several clumns as PKs (the only way in EA to create concatinated key) they are marked as unique and there is no way to change it - BUG!!!!

If there is a bug here, it's probably that EA just disables the checkbox and doesn't hide it. The "Unique" checkbox, if there was more room on the dialog, might be better named "Create Uniqueness Constraint". EA won't create a uniqueness constraint for a column which is part of a primary key (don't ask me why, I don't know the answer), so there's no point changing the value of the "Unique" checkbox, it won't have any effect. This is exactly the same behaviour as in EA 6.5.806 which I have just tried.

If you want to create a uniqueness constraint for a column that is part of a PK, check the Unique checkbox for some other column, change the <<unique>> operation that gets created so it refers to the PK column, then uncheck the Unique checkbox.

[«Midnight»]

If you want to create a uniqueness constraint for a column that is part of a PK, check the Unique checkbox for some other column, change the <<unique>> operation that gets created so it refers to the PK column, then uncheck the Unique checkbox.

And wait a (hopefully) brief while until this gets rectified.

Thanks for the insight and workaround Neil.

David

[Martin Terreni]

Thanks, now I know it will be created properly, but yet it is not good and I want it to be changed.
I have reversed engineered tables with out unique mark for concatenated PKs and new once with it marked, it is not consistent and it doesn't make our designs look better.
please change it!

[Martin Terreni]

This issue will be resolved in release build 817.

So I guess this is the end of the issue