empire-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From Francis De Brabandere <franci...@gmail.com>
Subject Re: error using apache derby and CLOB datatype
Date Mon, 13 Jul 2009 22:06:08 GMT
Hi Eike,

Thanks for reporting the bug, I added it to Jira for reference.

I have to admit that the postgres, h2 and derby drivers were only
tested using our demo application. We need to work on a decent test
suite. I applied a slightly different patch only using CLOB with size
as I think most people will expect a CLOB column for the CLOB data
type (do you think there might be performace implications?)

I started a build on hudson, it will be deployed on the apache
snapshot maven repo in a few minutes:
repository: https://repository.apache.org/content/repositories/snapshots



On Mon, Jul 13, 2009 at 11:18 PM, <news@eknet.org> wrote:
> hi there
> i was just experimenting with apache derby and found the following
> situation:
> 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.
> i will attach a tiny patch which worked in my case, but im not sure if
> i missed something...
> kind regards, eike

Microsoft gives you windows, Linux gives you the whole house.

View raw message