You are viewing a plain text version of this content. The canonical link for it is here.
Posted to ddlutils-dev@db.apache.org by "Martin van den Bemt (JIRA)" <ji...@apache.org> on 2007/03/24 18:26:33 UTC

[jira] Commented: (DDLUTILS-165) Data type mismatch in PostgreSQL with TEXT columns

    [ https://issues.apache.org/jira/browse/DDLUTILS-165?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel#action_12483859 ] 

Martin van den Bemt commented on DDLUTILS-165:
----------------------------------------------

I have a patch for this I think. Since I don't have a means to test this atm, instead of committing, I attach the patch here. If someone could check it solves the problem, I will commit it.

> Data type mismatch in PostgreSQL with TEXT columns
> --------------------------------------------------
>
>                 Key: DDLUTILS-165
>                 URL: https://issues.apache.org/jira/browse/DDLUTILS-165
>             Project: DdlUtils
>          Issue Type: Bug
>          Components: Core - PostgreSql
>         Environment: PostgreSQL v2.8.3 on Windows with JDBC driver 'postgresql-8.2-504.jdbc3.jar'
>            Reporter: Stefan Huber
>         Assigned To: Thomas Dudziak
>             Fix For: 1.0
>
>
> The PostgreSql jdbc driver returns VARCHAR(2147483647) for columns defined as TEXT. The ModelReader expects VARCHAR(-1) for these data type. 
> Maybe the behaviour of the jdbc driver changed lately, because there is a comment in the PostgreSqlModelReader.readColumn method which says that PostgreSQL returns VARCHAR(-1), but in my environment i get VARCHAR(2147483647).

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