Doh! My mistake. When I first read this message, I did not realize it was talking about the TURBINE_* tables. Even though it was in the subject for some reason..... Sigh.
-----Original Message----- From: Quinton McCombs Sent: Wednesday, December 04, 2002 9:33 AM To: Turbine Users List Subject: RE: TURBINE_* using native seqs? What sort of problem are you having? This behavior is configured in your project-schema.xml file. -----Original Message----- From: [EMAIL PROTECTED] [mailto:[EMAIL PROTECTED]] Sent: Tuesday, December 03, 2002 5:45 PM To: Turbine Users List Subject: TURBINE_* using native seqs? I've recently begun a project using Turbine and am quite impressed. I am, however, currently struggling with how to convince the turbine user/group/role objects to use 'native' id brokering rather than the ID_TABLE/idBroker system. It seems to me that this behavior is compiled into the .jar distributed as part of the tdk (I'm using 2.2rc2) and that I'm simply stuck and should learn to enjoy using native sequences for my tables and ID_TABLE for the TURBINE_* classes. Is this the case? Obviously not a huge deal; I'm simply curious. -j ------------------------------------------------- James Diggans Bioinformatics Programmer Gene Logic, Inc. Phone: 301.987.1756 FAX: 301.987.1701 -- 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]> -- To unsubscribe, e-mail: <mailto:[EMAIL PROTECTED]> For additional commands, e-mail: <mailto:[EMAIL PROTECTED]>
