Hi Cliff, 1. The reason I was getting an error on OBJECTDATA was due to the fact that I was trying to the DB2 profile in Torque which specified that a VARBINARY was to be treated as a BLOB. This threw type mismatch errors when I would try to add a new user in DB2/400. I ended over-hauling the DB2 and created a DB2/400 profile in torque/turbine which is now available from the CVS (I think it's in the HEAD, I haven't checked lately though) and works correctly with DB2/400.
2. You need all the fields defined in the turbine-schema.xml, at least from experience you do. 3. To have FKEY reference to TURBINE_USER, you will need to follow the extending the turbine user how-to: http://jakarta.apache.org/turbine/turbine-2/howto/extend-user-howto.html Also, there are other postings that spell out the gotchas with the above method. You'll have to search the archive for them. Scott -----Original Message----- From: Lang, Cliff [mailto:[EMAIL PROTECTED]] Sent: Friday, October 19, 2001 9:37 AM To: [EMAIL PROTECTED] Subject: Minimum fields required in TURBINE_USER table What are the minimum fields for the TURBINE_USER table? I saw an earlier message stating he had to keep the "OBJECTDATA" field in or he got errors. Can I have the LOGIN_NAME be a foreign key reference to one of my tables? <foreign-key foreignTable="WWW_DB"> <reference local="LOGIN_NAME" foreign="USER_NAME"/> </foreign-key> For that matter, which fields really need to be in the TURBINE_USER table? When Torque creates the Peers and maps, are those foreign keys automatically referenced, or does it just make it easier to do joins? Thanks, Cliff --------------------------------------------------------------------- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED] --------------------------------------------------------------------- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
