ok, i looked and torque instantiates one of the idgeneraters of each type regardless of which are used in any of the tables. you can minimize the overhead of IDBroker with the following property
torque.idbroker.prefetch=false Though you will still have ignore the warning message, except that it does indicate that your driver is reporting that it does not support transactions. john mcnally Blake Day wrote: > > Yep, I'm sure because I changed the defaultIdMethod="native" and checked the > rest of the XML to ensure that none of the tables defined the idMethod > attribute. > > Michael Blake Day > Artistry Studios - e-commerce design, implementation and hosting > email: [EMAIL PROTECTED] <mailto:[EMAIL PROTECTED]> > > -----Original Message----- > From: [EMAIL PROTECTED] [mailto:[EMAIL PROTECTED]]On > Behalf Of John McNally > Sent: Wednesday, April 10, 2002 10:32 PM > To: Turbine Users List > Subject: Re: couple of noob questions > > Blake Day wrote: > > > > I have 3 relatively simple questions. > > > > a) How do I prevent the IDBroker service from starting? I've tried > removing > > all references to it in my webapp, but it still starts. I would rather > not > > use it or have any artifacts lying around. > > I don't think it should start, if you are not using it for any tables. > But I might be wrong. > You are sure it is not being used for turbine's security tables? > > > > > b) I'm getting the following warning message: > > [Tue Apr 09 18:57:18 EDT 2002] -- WARN -- IDBroker is being used > with db: > > db_name_here > > which does not support transactions. It is possible to > > generate duplicate keys, if multiple JVM's are used or other > > means are used to write to the database. > > Although this warning will go away when I get rid of IDBroker, I'm curious > > as to why I would get that warning while using PostgreSQL as my RDBMS. I > > don't want any other problems relating to transactions to unexpectadly > arise > > later. > > you should not see this error with postgres unless the jdbc driver is > reporting that it does support transactions. Test a connection, what > does > > connection.getMetaData().supportsTransactions() > > return? > > -- > 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]>
