empire-commits mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From Rainer Döbele (Resolved) (JIRA) <empire-db-...@incubator.apache.org>
Subject [jira] [Resolved] (EMPIREDB-132) Fix support for CLOB data type in Postgre
Date Sat, 25 Feb 2012 22:15:50 GMT

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

Rainer Döbele resolved EMPIREDB-132.

    Resolution: Fixed

Added suggestions made by Vladimir Lahoda.

Changes are untested (due to lack of Postgre database) and should be checked.
> Fix support for CLOB data type in Postgre
> -----------------------------------------
>                 Key: EMPIREDB-132
>                 URL: https://issues.apache.org/jira/browse/EMPIREDB-132
>             Project: Empire-DB
>          Issue Type: Bug
>          Components: Core
>            Reporter: Rainer Döbele
> Fix problems reported by Vladimir Lahoda:
> The problem is that DbReader eventually calls JDBC method getClob() which IMHO is not
implemented correctly in the postgresql driver. It is recommended to use getString() method
on the CLOBs in Postgresql instead. But calling DBReader.getString() does not help either,
because it ends up calling getValue().toString(), with the same result as above. The same
situation holds for BLOBs as well. Any hints or workarounds, please?
> The second problem is with the DDL generator, which defines the CLOB column type as CLOB,
but this is unsupported by Postgresql and should be TEXT instead. Some googling suggests that
this was already fixed for previous versions of empire-db (at least in 2.0.7), but probably
the fix got lost in refactorings for version 2.2.0.

This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators: https://issues.apache.org/jira/secure/ContactAdministrators!default.jspa
For more information on JIRA, see: http://www.atlassian.com/software/jira


View raw message