>>> * use a real boolean column in their schema (I mean, the data you're
> representing IS a boolean value in this case, right?);
> --- No, we already tried this path. Unfortunately boolean is not portable
> column type among DB vendors. So, we ruled out this option.
You can't ship different DDL for different vendors?
I thought part of the point of using a mapping layer like Hibernate was
so Hibernate could handle the details of the mapping to different DBs
(which might be done in different ways) without having to know about the
different mappings in your application. So a Java boolean might be
mapped to either a Postgresql boolean or an Oracle SMALLINT (since
oracle doesn't have a real boolean type?), but your app code doesn't
care about that detail - it's just dealing with a Java boolean either way.
In response to
pgsql-bugs by date
|Next:||From: Magnus Hagander||Date: 2010-09-29 13:45:15|
|Subject: Re: [BUGS] BUG #5305: Postgres service stops when closing
|Previous:||From: Craig Ringer||Date: 2010-09-29 12:13:20|
|Subject: Re: BUG #5682: Postgres Service crashes with exception 0xC0000135|
pgsql-jdbc by date
|Next:||From: Craig Ringer||Date: 2010-09-29 13:57:28|
|Subject: Re: Loading a dump containing include commands|
|Previous:||From: John Lister||Date: 2010-09-29 12:59:27|
|Subject: selecting using array as IN condition parameter - possible?|