/
- Original Message -
From: Markus Holmberg [EMAIL PROTECTED]
To: Orion-Interest [EMAIL PROTECTED]
Cc: Orion-Interest [EMAIL PROTECTED]
Sent: Friday, January 12, 2001 7:58 PM
Subject: Re: large field bug ??
On Thu, Jan 11, 2001 at 08:20:58AM +0700, Agus K. Pranantoseno wrote:
I have manage
On Thu, Jan 11, 2001 at 08:20:58AM +0700, Agus K. Pranantoseno wrote:
I have manage to put my String stored as blob working using cmp but if
the size is more than 1k it's go wrong... (the blob does not stored to the
db and the next time i restart the orion those entity even failed to
:[EMAIL PROTECTED]]
Sent: Jueves, 11 de Enero de 2001 7:27
To: Orion-Interest
Subject: RE: large field bug ??
Some thoughts...
You are right, that such a work-around would work, but having
to keep your
Strings stored in memory as Objects i not very nice - can't
the mapping be
changed, so
-Interest
Emne: RE: large field bug ??
Some thoughts...
You are right, that such a work-around would work, but having to keep your
Strings stored in memory as Objects i not very nice - can't the mapping be
changed, so Strings are mapped to Blobs...?
If not, I would use StringBuffer (which
-Interest
Subject: Re: large field bug ??
On Thu, Jan 11, 2001 at 08:20:58AM +0700, Agus K. Pranantoseno wrote:
I have manage to put my String stored as blob working using cmp but if
the size is more than 1k it's go wrong... (the blob does not stored to the
db and the next time i restart
had that problem
it's a mapping problem... (oracle-schema)
Strings get Mapped to varchars(size)...
They get chopped at size chars...
the only solution is to declare the field as java.lang.Object
then use it as string
public Object name;
public void setName(String name)
{
, 11 de Enero de 2001 7:27
To: Orion-Interest
Subject: RE: large field bug ??
Some thoughts...
You are right, that such a work-around would work, but having to keep your
Strings stored in memory as Objects i not very nice - can't the mapping be
changed, so Strings are mapped to Blobs...?
If not, I
