You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@openjpa.apache.org by "Milosz Tylenda (JIRA)" <ji...@apache.org> on 2010/05/16 13:56:42 UTC
[jira] Created: (OPENJPA-1667) Incorrect column type for LOB
streaming in MySQL
Incorrect column type for LOB streaming in MySQL
------------------------------------------------
Key: OPENJPA-1667
URL: https://issues.apache.org/jira/browse/OPENJPA-1667
Project: OpenJPA
Issue Type: Bug
Components: sql
Affects Versions: 2.0.0, 1.3.0
Environment: MySQL 5.1.30
Reporter: Milosz Tylenda
Assignee: Milosz Tylenda
Priority: Minor
After the changes made in OPENJPA-740, a LOB streaming field is mapped to TINYBLOB instead of BLOB in MySQL. This is because column size is -1 and in MySQLDictionary.getColumnType we assume that only size = 0 means "size unknown". Adding a check for -1 will probably resolve the issue.
--
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.
[jira] Resolved: (OPENJPA-1667) Incorrect column type for LOB
streaming in MySQL
Posted by "Milosz Tylenda (JIRA)" <ji...@apache.org>.
[ https://issues.apache.org/jira/browse/OPENJPA-1667?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Milosz Tylenda resolved OPENJPA-1667.
-------------------------------------
Fix Version/s: 1.3.0
2.1.0
Resolution: Fixed
> Incorrect column type for LOB streaming in MySQL
> ------------------------------------------------
>
> Key: OPENJPA-1667
> URL: https://issues.apache.org/jira/browse/OPENJPA-1667
> Project: OpenJPA
> Issue Type: Bug
> Components: sql
> Affects Versions: 1.3.0, 2.0.0
> Environment: MySQL 5.1.30
> Reporter: Milosz Tylenda
> Assignee: Milosz Tylenda
> Priority: Minor
> Fix For: 1.3.0, 2.1.0
>
>
> After the changes made in OPENJPA-740, a LOB streaming field is mapped to TINYBLOB instead of BLOB in MySQL. This is because column size is -1 and in MySQLDictionary.getColumnType we assume that only size = 0 means "size unknown". Adding a check for -1 will probably resolve the issue.
--
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.