[
https://issues.apache.org/jira/browse/DERBY-2999?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Myrna van Lunteren updated DERBY-2999:
--------------------------------------
Attachment: DERBY-2999.diff_v3
DERBY-2999.stat_v3
I tried Ravinder's patch, but it wasn't working for me, for starters, the
dropping and closing left or created locks. Having the statements as global
variables also caused locks to remain in place, and finally the schemas didn't
get created.
So I basically started from scratch, but added Ravinder's check for the Lock
Table command on sys.systables.
Now the test uses a decorateSQL to create the schemas.
I did add Kristian's suggestion for an extra insert in the TXvsTX test.
I also have included the selects from syscs_diag.lock_table.
I also used the assert which checks on an array of errors instead of just
40XL1. Possibly this assert wasn't available when Ravinder made his version.
I also used the DatabasePropertyTestSetup, so we only wait as per the original
test properties.
Running tests...
> convert lang/lockTable.sql to Junit
> -----------------------------------
>
> Key: DERBY-2999
> URL: https://issues.apache.org/jira/browse/DERBY-2999
> Project: Derby
> Issue Type: Improvement
> Components: Test
> Affects Versions: 10.3.1.4
> Reporter: Ravinder Reddy
> Attachments: DERBY-2999.diff-v1, DERBY-2999.diff-v2,
> DERBY-2999.diff_v3, DERBY-2999.stat_v3, STATUS-2999-v1, STATUS-v2
>
>
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators
For more information on JIRA, see: http://www.atlassian.com/software/jira
