empire-commits mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Francis De Brabandere (JIRA)" <empire-db-...@incubator.apache.org>
Subject [jira] Commented: (EMPIREDB-44) error using apache derby and CLOB datatype
Date Mon, 13 Jul 2009 21:57:14 GMT

    [ https://issues.apache.org/jira/browse/EMPIREDB-44?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12730544#action_12730544

Francis De Brabandere commented on EMPIREDB-44:

I applied a slightly different patch as most people probably will expect a CLOB column for
that data type.

> 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 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.
You can reply to this email to add a comment to the issue online.

View raw message