Title:
Bug 75962:Setting both @unique and @uniquekey results in two unique constraints generated
| View in TrackerStatus/Resolution/Reason: Closed/Fixed/
Reporter/Name(from Bugbase): Devin Holloway / Devin Holloway (Devin Holloway)
Created: 03/13/2009
Components: ORM Support
Versions: 9.0
Failure Type: Unspecified
Found In Build/Fixed In Build: 0000 / 227817
Priority/Frequency: Normal / Unknown
Locale/System: English / Platforms All
Vote Count: 0
Problem:
Setting both @unique and @uniquekey results in two unique constraints generated.
If you set the uniquekey attribute, then unique="true" should be implied and ignored.
The workaround is to set one or the other, but not both.
Method:
/**
* @column login_username
* @datatype string
* @length 75
* @unique true
* @uniquekey UC_login_username
*/
property string username;
Result:
----------------------------- Additional Watson Details -----------------------------
Watson Bug ID: 3037865
External Customer Info:
External Company:
External Customer Name: Devin Holloway
External Customer Email: 5E060FD6422E831A992015D5
External Test Config: 03/13/2009Attachments:
Comments: