Re: Mapping for type BIT broke afer upgrade from 1.0.1 to 1.0.4

Hi Oliver,

Oliver Seimel wrote:
> Hi,
> 
> we migrated from ojb 1.0.1 to 1.0.4
> DB is Postgres. But I think, that the "problem" is independent
> of the DB. 
> We use the type BIT(1) for boolean values, so a mapping looks
> like this:
> 
> <field-descriptor
>     name="emailNotice"
>     column="emailnotice"
>     jdbc-type="BIT"
> />
> 
> With version 1.0.1 the generated SQL was
> ... WHERE emailnotice = '1' .....
> 
> With version 1.0.4 the generated SQL is
> ... WHERE emailnotice = 'true' .....
> 
> Thats not good, because the statement fails.
> 
> Does anybody know why ojb now maps the BIT types
> to BOOLEAN? 

OJB 1.0.4 and higher try to support the JDBC 3.0 specification which 
specify to map BIT to boolean
http://db.apache.org/ojb/docu/guides/jdbc-types.html
Maybe this cause your problem.
Could you please post the query/criteria which produce the SQL shown above.

regards,
Armin

> 
> Thank you very much
> Oliver
> 
> 
> ---------------------------------------------------------------------
> To unsubscribe, e-mail: [email protected]
> For additional commands, e-mail: [email protected]
> 
>