BIT and BOOLEANCHAR are not working properly with Postgres.  BOOLEANCHAR
should work in the CVS version of Torque, and I think BOOLEANINT should
work too.  Neither of those types use PostgreSQL's BOOLEAN type though,
one uses a CHAR and the other an INT2.  If you don't mind modifying
Torque, you can try editing templates/sql/base/postgres/db.props to
have:

BIT = boolean
BOOLEANCHAR = char

And experiment with those types.  I think BIT will work unless you are
using Objects (instead of primitives), BOOLEANCHAR should work either
way, but I can't guarantee that.

-james

On Mon, 2002-05-06 at 10:29, sbelt wrote:
> I saw the question posted in the Turbine archive, but could not find an
> answer:
> 
> I am using torque (3.0 dev from cvs ~January). My database is Postgresql.
> 
> I have created a table which contains a boolean column defined in my
> schema.xml as follows:
> ...
> <column name="x9"
>     javaName="FlagAudit"
>     primaryKey="false"
>     required="false"
>     autoincrement="false"
>     type="BOOLEANCHAR">
>     <!-- insert any inheritance info here -->
> </column>
> ...
> 
> when I add a new row of information, this value is set to 0 (false).
> (I don't know why it is set as I have not defined a default; but that's
> ok, because this is the default value I would set)
> 
> Now, when I load a row from a .doSelect, change the
> value using .setFlagAudit(true), the column remains 0. I see no
> errors in the output nor the .logs.
> 
> Is this corrected in more recent versions? Is there a fix/work-around?
> Or am I just making some unreported error?
> 
> Thanks!
> 
> Steve B.
> 
> save it, this
> column remains 0. If I
> 
> 
> 
> --
> To unsubscribe, e-mail:   <mailto:[EMAIL PROTECTED]>
> For additional commands, e-mail: <mailto:[EMAIL PROTECTED]>
> 
> 
-- 
[]  James A. Hillyerd <[EMAIL PROTECTED]> - Java Software Engineer
[]  PGP 1024D/D31BC40D F87B 7906 C0DA 32E8 B8F6 DE23 FBF6 4712 D31B C40D


--
To unsubscribe, e-mail:   <mailto:[EMAIL PROTECTED]>
For additional commands, e-mail: <mailto:[EMAIL PROTECTED]>

Reply via email to