New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Unique index creation #361
Comments
@dreab8 as mentioned in https://jakarta.ee/committees/specification/tckprocess/, this issue needs the |
Note that we can't add a challenge label to the issue |
label added; note that any committer is able to do that |
As per https://jakarta.ee/committees/specification/tckprocess, approval is the default after 14 days (March 4 I think), unless the challenge is accepted/denied before then. |
I believe this is purely TCK issue and since it has been resolved there already, time to close this. |
Sure, but we would like the challenge to be accepted so that we can exclude the test from the 3.0 TCK |
you don't see the label added about an hour ago? |
Sorry, I didn't look careful enough before. All fine :) |
ok |
Signed-off-by: Scott Marlow <smarlow@redhat.com>
…aee/persistence#350 and also increment Persistence TCK version to 3.0.2 Signed-off-by: Scott Marlow <smarlow@redhat.com>
The
com/sun/ts/tests/jpa/se/schemaGeneration/annotations/index/Client.java#indexTest
test checks for the unique index creation that the generated schema creation script containsALTER TABLE SCHEMAGENSIMPLE ADD UNIQUE INDEX SCHEMAGENSIMPLE_SVALUE3
orCREATE UNIQUE INDEX SCHEMAGENSIMPLE_SVALUE3 ON SCHEMAGENSIMPLE (SVALUE3)
and it fails ifALTER TABLE SCHEMAGENSIMPLE ADD CONSTRAINT SCHEMAGENSIMPLE_SVALUE3 UNIQUE (SVALUE3)
is generated instead.The text was updated successfully, but these errors were encountered: