[
https://issues.apache.org/jira/browse/DERBY-4038?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12796317#action_12796317
]
Myrna van Lunteren commented on DERBY-4038:
-------------------------------------------
I have played with various scenarios...
I can modify AccessTest fixtures to create the PADSTRING stored procedure
without using the decorateSQL...
Or I can modify EncryptionSuite to have a setUp and tearDown method to create
and shutdown the stored procedure...
But the SystemPropertyTestSetup and the Decorator.encryptedDatabase don't work
together, because for SystemPropertyTestSetup the database has to be rebooted
and the required boot password is local to Decorator.encryptedDatabase().
I'll experiment getting a EncryptedSystemPropertyTestSetup, but in the mean
time, really the only bit that's affected by not having the SystemProperties is
that in the test case for CS1346 (a and b), half the time the length(a) of
long1 and long2 is different when we have the property
derby.optimizer.ruleBasedOptimization set to true (3240) vs. when it is false
(3024).
(the other half of the time it's already 3024 characters).
Is that part of the test important to be verified with encryption?
> On Z/OS store/access.sql fails with encryptionAES and encryptionDES
> -------------------------------------------------------------------
>
> Key: DERBY-4038
> URL: https://issues.apache.org/jira/browse/DERBY-4038
> Project: Derby
> Issue Type: Bug
> Components: Test
> Affects Versions: 10.3.3.0
> Environment: java version "1.6.0"
> Java(TM) SE Runtime Environment (build pmz6460sr3-20081108_01(SR3))
> IBM J9 VM (build 2.4, J2RE 1.6.0 IBM J9 2.4 z/OS s390x-64
> jvmmz6460-20081107_25433 (JIT enabled, AOT enabled)
> J9VM - 20081105_025433_BHdSMr
> JIT - r9_20081031_1330
> GC - 20081027_AB)
> JCL - 20081106_01
> $ pwd
> Reporter: Kathey Marsden
> Priority: Minor
> Attachments: access.diff, access.out, DERBY-4038.diff_1,
> DERBY-4038.diff_2, DERBY-4038.diff_3, runaccess.out
>
>
> On Z/OS access.sql fails for encryptionAES and encryptionDES. The diff is big
> but I can't quite make out what the problem is. Maybe just a change of query
> plans.
--
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.
