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 2009/07/02 20:59:47 UTC
[jira] Created: (EMPIREDB-41) Deal with databases differences
regarding SQL reverse function
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
Priority: Minor
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.
[jira] Commented: (EMPIREDB-41) Deal with databases differences
regarding SQL reverse function
Posted by "Francis De Brabandere (JIRA)" <em...@incubator.apache.org>.
[ https://issues.apache.org/jira/browse/EMPIREDB-41?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12735368#action_12735368 ]
Francis De Brabandere commented on EMPIREDB-41:
-----------------------------------------------
I am testing the patched driver
the first thing I got was this:
he could not find the plpgsql language so I had to run this:
"sudo -u postgres createlang plpgsql postgres"
then this: ERROR: unterminated string
just had to replace \' by \\' in the function creation script
now this seems to work correctly
> 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
> Priority: Minor
>
> 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.
[jira] Resolved: (EMPIREDB-41) Deal with databases differences
regarding SQL reverse function
Posted by "Francis De Brabandere (JIRA)" <em...@incubator.apache.org>.
[ 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.