Could you enter a defect for the problem with byte mappings? -----Original Message----- From: Marc Lustig [mailto:[EMAIL PROTECTED]] Sent: Sunday, December 15, 2002 7:31 PM To: Turbine Users List Subject: AW: more patches to Extending User update (was AW: Documentation update)
> > That's interesting to know. What is the exact xml-syntax? Is it > > specified in the database-element like this? <database > > defaultJavaType="object"> Is it possible to specifiy this for each > > table individually? Probably this would cause trouble with > > TurbineUserAdapter. > > > > You are correct with the syntax. For the table it is > javaType="object". The code given in the how-to is based on using > defaultJavaType="object" for your project. The implementation of > TurbineUser in the o.a.t.om.security package is using primatives. I tried with defaultJavaType="object". It works except for type tinyint. Torque generates things like Byte xx = new Byte(0); which does not work as Byte doesn't have a constructor for int. These columns need to be specified as javaType="primitive", e.g. <column name="GLOBAL_AVAILABILITY" type="TINYINT" size="1" default="0" javaType="primitive"/> I use mysql which has no support for boolean, so I simulate this using tinyint 1. It would be cool if Torque would allow a mapping to boolean. Marc -- To unsubscribe, e-mail: <mailto:[EMAIL PROTECTED]> For additional commands, e-mail: <mailto:[EMAIL PROTECTED]> -- To unsubscribe, e-mail: <mailto:[EMAIL PROTECTED]> For additional commands, e-mail: <mailto:[EMAIL PROTECTED]>
