The new IS_MAPPING_ONLY column in SECURITY_PRINCIPAL is mapped to a bool data type when used with Postgres. Obviously the population scripts gag when trying to insert a 0 into the column. As a workaround I am generating this column type locally as a BOOLEANINT which comes out to an int2 in Postgres. This works just fine as far as I can tell, but how about changing this to a simple boolean type for the long term? An alternative is to see if there is a way to coerce Torque to create a BIT(1) or something like that but I could not find a way to easily modify the way Torque maps data types.
I work exclusively with Postgres and I normally keep updated from CVS daily, if someone wants me to create these Postgres related items as Jira issues let me know, I would be happy to do it. Chris --------------------------------------------------------------------- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
