[ https://issues.apache.org/jira/browse/OAK-3645?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15092165#comment-15092165 ]
Julian Reschke commented on OAK-3645: ------------------------------------- The patch works for me, except that Oracle and Derby complained about the trailing semicolon. I removed it throughout (for all other DBs as well), and this seems to work. One remaining concern is that we don't have a default implementation for unknown databases (or we have one, but it won't work). It probably would be best to disable the check in that case. Will post an updated patch. > RDBDocumentStore: server time detection for DB2 fails due to timezone/dst > differences > ------------------------------------------------------------------------------------- > > Key: OAK-3645 > URL: https://issues.apache.org/jira/browse/OAK-3645 > Project: Jackrabbit Oak > Issue Type: Technical task > Components: rdbmk > Affects Versions: 1.3.10, 1.2.8, 1.0.24 > Reporter: Julian Reschke > Assignee: Tomek Rękawek > Attachments: OAK-3645.patch > > > We use {{CURRENT_TIMESTAMP(4)}} to ask the DB for it's system time. > Apparently, at least with DB2, this might return a value that is off by a > multiple of one hour (3600 * 1000ms) depending on whether the OAK instance > and the DB run in different timezones. > Known to work: both on the same machine. > Known to fail: OAK in CET, DB2 in UTC, in which case we're getting a > timestamp one hour in the past. > At this time it's not clear whether the same problem occurs for other > databases. -- This message was sent by Atlassian JIRA (v6.3.4#6332)