Hi,
I am rather sure that this will not solve the problem, as the problem is
probably not in the IdBroker, but somewhere else.
Usually, if you see this message, there is something wrong in the
configuration. It would help to read the logs; if you do not have any, you
should configure logging for your application to find the error.
Thomas
Andras Balogh <[EMAIL PROTECTED]> schrieb am 23.06.2005 09:02:00:
> Hello,
>
> How did you configured the idMethod in your schema? You don't need
> IDBroker since mysql should
> support auto increment primary keys so you should go with
> idMethod="native" for tables with auto increment
> primary key.
>
> Best regards,
> Andras.
>
>
> Youngho Cho wrote:
>
> >Hello,
> >
> >I read TRQ278 for InnoDB related Issue.
> >It is about create tables and fk relations issue.
> >In my case, when I create tables using generated sql from xml.
> >I set SET FOREIGN_KEY_CHECKS=0; before execute the sql.
> >Than there is no complain.
> >
> >My problem is I would like to use transaction but the warn report
> said torque doesn't use transaction.
> >I use connector/j-3.1.7 driver.
> >Do I have to ask it to mysql driver mailling list ?
> >How you use torque with InnoDB ?
> >
> >Thanks.
> >
> >Youngho
> >
> >
> >
> >
>
>
> ---------------------------------------------------------------------
> 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]
