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 2013/02/04 15:08:12 UTC
[jira] [Closed] (EMPIREDB-44) error using apache derby and CLOB
datatype
[ https://issues.apache.org/jira/browse/EMPIREDB-44?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Rainer Döbele closed EMPIREDB-44.
---------------------------------
Cleanup of unclosed issues.
> error using apache derby and CLOB datatype
> ------------------------------------------
>
> Key: EMPIREDB-44
> URL: https://issues.apache.org/jira/browse/EMPIREDB-44
> Project: Empire-DB
> Issue Type: Bug
> Components: Core
> Affects Versions: empire-db-2.0.4-incubating
> Reporter: Francis De Brabandere
> Assignee: Francis De Brabandere
> Fix For: empire-db-2.0.5-incubating
>
>
> One of our users (eike) reported this bug:
> one of my columns needs to store really long texts. so what i did with
> empire-db is this:
> C_DESCRIPTION = addColumn("description", DataType.CLOB, 1024*1024, false);
> not being really sure, if this is the desired way to go, it worked
> with mysql (5.0.27). the same results in a "BadSQLGrammarException"
> using apache derby 10.4.2.0. the CLOB datatype is translated into
> this:
> CREATE TABLE betmarket (
> ...
> description LONGTEXT,
> ...
> im really new to apache derby, but having a quick look at their page i
> could not find the data type "LONGTEXT" in their manual. they have
> CLOB and LONG VARCHAR as i could see. where LONG VARCHAR goes up to
> 32700 characters and a CLOB may be up to 2,147,483,647.
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators
For more information on JIRA, see: http://www.atlassian.com/software/jira