[
https://issues.apache.org/jira/browse/DERBY-5966?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13487765#comment-13487765
]
Rick Hillegas commented on DERBY-5966:
--------------------------------------
Thanks for that suggestion, Knut. I think it will work. However, it requires
different (de)serialization logic for LASTMODIFIED stamps, depending on whether
they were written to SYSUSERS before or after the fix is applied.
1) One approach to this problem would be to overload HASHINGSCHEME so that it
both describes the technique used to hash PASSWORD as well as the technique
used to serialize LASTMODIFIED. We could introduce a new prefix for the
HASHINGSCHEME column: ID_PATTERN_CONFIGURABLE_STRETCHED_SCHEME_GMT. This prefix
would imply hashing behavior identical to
ID_PATTERN_CONFIGURABLE_STRETCHED_SCHEME but it would encode the fact that
LASTMODIFIED was shifted to GMT before being serialized.
2) Another approach would be to add a timezone column to SYS.SYSUSERS.
3) Another approach would be to add a time-zone aware variant of SQLTIMESTAMP
and store that in LASTMODIFIED.
Other suggestions?
Thanks,
-Rick
> NativeAuthenticationServiceTest.testAll() failure: [ FILE, NATIVE
> authentication on, LOCAL authentication ON, Authentication/Authorization
> turned OFF, SecurityManager ON, Embedded ]: Connection to fifthDB
> unexpectedly failed.
> ---------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------
>
> Key: DERBY-5966
> URL: https://issues.apache.org/jira/browse/DERBY-5966
> Project: Derby
> Issue Type: Bug
> Components: Test
> Affects Versions: 10.10.0.0
> Reporter: Knut Anders Hatlen
> Priority: Minor
>
> Saw these failures on multiple platforms around the time Europe switched from
> DST:
> http://dbtg.foundry.sun.com/derby/test/Daily/jvm1.5/testing/testlog/sles/1402814-suitesAll_diff.txt
> http://dbtg.foundry.sun.com/derby/test/Daily/jvm1.5/testing/testlog/sparc/1402814-suitesAll_diff.txt
> http://dbtg.foundry.sun.com/derby/test/Daily/jvm1.5/testing/testlog/vista/1402814-suitesAll_diff.txt
> 3)
> testAll(org.apache.derbyTesting.functionTests.tests.lang.NativeAuthenticationServiceTest)junit.framework.AssertionFailedError:
> [ FILE, NATIVE authentication on, LOCAL authentication ON,
> Authentication/Authorization turned OFF, SecurityManager ON, Embedded ]:
> Connection to fifthDB unexpectedly failed.
> at
> org.apache.derbyTesting.functionTests.tests.lang.NativeAuthenticationServiceTest.getConnection(NativeAuthenticationServiceTest.java:1604)
> at
> org.apache.derbyTesting.functionTests.tests.lang.NativeAuthenticationServiceTest.getConnection(NativeAuthenticationServiceTest.java:1570)
> at
> org.apache.derbyTesting.functionTests.tests.lang.NativeAuthenticationServiceTest.getConnection(NativeAuthenticationServiceTest.java:1564)
> at
> org.apache.derbyTesting.functionTests.tests.lang.NativeAuthenticationServiceTest.vetPasswordLifetime(NativeAuthenticationServiceTest.java:1385)
> at
> org.apache.derbyTesting.functionTests.tests.lang.NativeAuthenticationServiceTest.testAll(NativeAuthenticationServiceTest.java:618)
> at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
--
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
