You are viewing a plain text version of this content. The canonical link for it is here.
Posted to commits@empire-db.apache.org by "Rainer Döbele (JIRA)" <em...@incubator.apache.org> on 2013/02/04 15:06:16 UTC
[jira] [Closed] (EMPIREDB-41) Deal with databases differences
regarding SQL reverse function
[ https://issues.apache.org/jira/browse/EMPIREDB-41?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Rainer Döbele closed EMPIREDB-41.
---------------------------------
Cleanup of unclosed issues.
> 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.
If you think it was sent incorrectly, please contact your JIRA administrators
For more information on JIRA, see: http://www.atlassian.com/software/jira