db-derby-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From Daniel John Debrunner <...@debrunners.com>
Subject Re: [jira] Commented: (DERBY-102) can not insert more than 32270 charakters in long varchar, clob
Date Mon, 13 Dec 2004 20:36:56 GMT
-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA1

Sunitha Kambhampati (JIRA) wrote:

>      [
http://nagoya.apache.org/jira/browse/DERBY-102?page=comments#action_56591 ]
>
> Sunitha Kambhampati commented on DERBY-102:
> -------------------------------------------
>
> --I believe these are the limits currently enforced :-
> VARCHAR maximum length 32 672
> LONG VARCHAR maximum length 32 700
> CLOB maximum length 2 147 483 647
> BLOB maximum length 2 147 483 647
> and hence the insert of 32800 chars into long varchar fails.
>
> So it seems these didnt make it into the documentation. The following
page will need to reflect the correct limit:
http://incubator.apache.org/derby/manuals/reference/sqlj137.html#IDX1005
>
> Also lot of the limits live in org.apache.derby.iapi.reference.DB2Limit
>
> --I would think you should be able to insert into a clob. If you could
post the test reproduction or SQLExceptions that you are getting for
inserting a clob, along with traces in derby.log, that would be great.

>>ERROR 54002: A string constant starting with ''
>>ddddddddddddddddddddddddddddddddddddddddddddddddddddddddd&' is too long.


The issue is that string constants (literals) in the text of a SQL
statement are limited in length.

If the insert statement used a parameter marker '?' instead of a
constant, then larger values could be passed in, up to the limits
Sunitha lists above.


Dan.
-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.2.5 (MingW32)
Comment: Using GnuPG with Mozilla - http://enigmail.mozdev.org

iD8DBQFBvf1oIv0S4qsbfuQRAsGKAJ0dMLFdHnIOk9XFdNQuShzv73xbXACeKRJu
9MfUDiPqhrEfdNsmMGT0f+A=
=RFgU
-----END PGP SIGNATURE-----


Mime
View raw message