[
https://issues.apache.org/jira/browse/OAK-2949?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Julian Reschke updated OAK-2949:
--------------------------------
Fix Version/s: 1.0.15
> RDBDocumentStore: no custom SQL needed for GREATEST
> ---------------------------------------------------
>
> Key: OAK-2949
> URL: https://issues.apache.org/jira/browse/OAK-2949
> Project: Jackrabbit Oak
> Issue Type: Sub-task
> Components: rdbmk
> Affects Versions: 1.2.2, 1.0.14, 1.3
> Reporter: Julian Reschke
> Assignee: Julian Reschke
> Priority: Minor
> Fix For: 1.3.0, 1.2.3, 1.0.15
>
>
> We currently use "GREATEST" to set MODIFIED to max(old, new). As this isn't
> supported by SQLServer, the code supports custom query strings.
> Turns out we don't need this, because we can replace it with a CASE statement
> (see
> http://stackoverflow.com/questions/30530970/equivalent-of-sql-greatest-function-for-apache-derby)
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
