cayenne-commits mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "ASF GitHub Bot (JIRA)" <>
Subject [jira] [Commented] (CAY-2098) EOModel import does not distinguish CLOB columns from VARCHAR
Date Fri, 05 Aug 2016 14:01:20 GMT


ASF GitHub Bot commented on CAY-2098:

GitHub user maiksd opened a pull request:

    Modeler EOModel import improvements


You can merge this pull request into a Git repository by running:

    $ git pull modeler_fixes

Alternatively you can review and apply these changes as the patch at:

To close this pull request, make a commit to your master/trunk branch
with (at least) the following in the commit message:

    This closes #103
commit ee22c10da10c672e2c19b16c7f3a36d27025d18b
Author: Maik Musall <>
Date:   2016-08-05T11:58:10Z

    CAY-2098 correctly distinguish CLOB columns from VARCHAR. Tested only with a PostgreSQL
based model.

commit bc4f9a3608b9e80ab03ea0bc46bb15cfe395e1d3
Author: Maik Musall <>
Date:   2016-08-05T13:57:01Z

    CAY-2099 guess sql type of prototyped custom Java attributes based on externalType in
model plist

commit 3591c2626b61357f0b3f589ab69265bda312ef9f
Author: Maik Musall <>
Date:   2016-08-05T13:58:08Z

    Merge branch 'master' into modeler_fixes


> EOModel import does not distinguish CLOB columns from VARCHAR
> -------------------------------------------------------------
>                 Key: CAY-2098
>                 URL:
>             Project: Cayenne
>          Issue Type: Bug
>          Components: EOF integration
>    Affects Versions: 4.0.M3
>            Reporter: Maik Musall
> CLOB columns have no width in the plist, and an externalType CLOB or TEXT (in the case
of PostgreSQL), but since the mapping is based only on the Java type, they end up as VARCHAR
with no width set.
> I've already fixed this and will submit a pull request shortly.

This message was sent by Atlassian JIRA

View raw message