Further to this, any query that involves a BOOLEANINT field fails with the error:
org.postgresql.util.PSQLException: ERROR: operator does not exist: smallint = boolean Apparently the query passes a boolean value for the field even though it's implemented as an integer. From what I read elsewhere, this strict behaviour in the PostgreSQL driver is unlikely to change, so does anyone know of a workaround? Thanks, Peter On 25/03/06, Peter Ledbrook <[EMAIL PROTECTED]> wrote: > Hi, > > I have tried to build Scarab against a postgresql database, but I'm > running into a problem with the SQL generated by Torque. The Scarab > database schema specifies a size for some of its integer columns, and > these columns then have a type of INTEGER(n), where 'n' is the given > size. For example: > > <column name="DELETED" required="false" type="BOOLEANINT" > default="0" size="1" javaType="primitive"/> > > becomes the SQL: > > DELETED INT2(1) > > Unfortunately, postgresql does not support a size here, i.e. "INT2" > works, but "INT2(1)" does not. Note that this problem occurs with > INTEGER as well as BOOLEANINT. > > Is this a know problem? Is there a workaround other than removing the > 'size' attributes from integer columns? > > Thanks, > > Peter > --------------------------------------------------------------------- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
