Re: Bad value for type BigDecimal : Y

From: Ashish Jain <ashjain2(at)gmail(dot)com>
To: John Lister <john(dot)lister(at)kickstone(dot)com>
Cc: Mikko Tiihonen <mikko(dot)tiihonen(at)nitorcreations(dot)com>, richard(dot)broersma(at)gmail(dot)com, pgsql-jdbc(at)postgresql(dot)org
Subject: Re: Bad value for type BigDecimal : Y
Date: 2009-06-16 08:22:18
Message-ID: 14af40510906160122t60d30e48r828cb8acf7804bd0@mail.gmail.com
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: pgsql-jdbc

John/Mikko/Richard,

Thanks a lot for all your help on this issue.
I was able to resolve this problem by setting the following property
<property name="openjpa.jdbc.DBDictionary"
value="postgres(StoreCharsAsNumbers=false)"/>

Thanks
Ashish

On Fri, Jun 12, 2009 at 1:12 PM, John Lister <john(dot)lister(at)kickstone(dot)com>wrote:

> Ashish Jain wrote:
>
>> Hi Mikko/Richard,
>> Thanks for your reply. I do have a column whose length is 1. The
>> definition goes something like this
>> @Column(updatable=true, name="st_spom_status", nullable=false, length=1)
>> private String status;
>> Do you think this is what may be the cause of the problem??
>>
>>
> My first guess is that you have a column defined as a bigdecimal in your
> jpa object but it is actually a string in the database one of whose rows
> contains the value 'Y'.
>
> JOHN
>
>

In response to

Browse pgsql-jdbc by date

  From Date Subject
Next Message Ashish Jain 2009-06-16 10:10:16 prepared transaction with identifier "1197822575_XAAAAAAAAABHVE1JRAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAA==_AQAAAAAAAABHVE1JRAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAA==" does not exist
Previous Message Dave Page 2009-06-15 20:08:12 Testing - ignore.