empire-commits mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Francis De Brabandere (JIRA)" <empire-db-...@incubator.apache.org>
Subject [jira] Resolved: (EMPIREDB-41) Deal with databases differences regarding SQL reverse function
Date Sun, 26 Jul 2009 10:03:14 GMT

     [ https://issues.apache.org/jira/browse/EMPIREDB-41?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]

Francis De Brabandere resolved EMPIREDB-41.
-------------------------------------------

       Resolution: Fixed
    Fix Version/s: empire-db-2.0.5-incubating
         Assignee: Rainer Döbele

fixed the patch

call this if you need this function in your application

// Create the reverse function that is needed by this sample
driver.createReverseFunction(conn);

> Deal with databases differences regarding SQL reverse function
> --------------------------------------------------------------
>
>                 Key: EMPIREDB-41
>                 URL: https://issues.apache.org/jira/browse/EMPIREDB-41
>             Project: Empire-DB
>          Issue Type: Improvement
>          Components: Core
>            Reporter: Rainer Döbele
>            Assignee: Rainer Döbele
>            Priority: Minor
>             Fix For: empire-db-2.0.5-incubating
>
>
> Currently the SQL reverse function is not supported for all databases.
> The reverse function is used in the basic example, the example does not behave the same
for all database types.
> For databases not supporting the SQL reverse function a workaround is used, in order
to run the sample at all.
> On July the 1st Frank Lupo suggested a solution for the postgreql database that creates
such a function.
> The question is how do we deal with this in general. 

-- 
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.


Mime
View raw message