Hi, I was the one with the patch for TorqueSQLExec and it was applied. It added alphabetical ordering of sql files per database schema. Later I found that it still doesn't take care of cases with more than one database but I haven't had time to look at it yet. The problem is that every database schema will get it's own idtable-init sql file that references the id_table. The schema that actually contains the id_table is not guaranteed to be inserted first so inserts end up being done before it exists. I'll try to find some time to fix it today and send a patch if nobody beats me to it.
On a side issue: the sample app generates several schemas, each with its own database name (newapp, second, third, turbine, etc). But only one database is added to Torque.properties (newapp). Is this correct behaviour ? Age > -----Original Message----- > From: Jason van Zyl [mailto:[EMAIL PROTECTED]] > Sent: Tuesday, March 12, 2002 06:07 > To: [EMAIL PROTECTED] > Subject: [tdk] id broker sql insertion order problem > > > Hi, > > I think someone had a patch for the ordering problem w.r.t. the > insertion of the generated id broker sql? > > I am having a problem with the sample app in the tdk so I'm assuming the > patch wasn't applied or I was dreaming that there was a solution. > > Martin, did you apply it? I can't remember :-( > > -- > jvz. > > Jason van Zyl > [EMAIL PROTECTED] > > http://tambora.zenplex.org > > > -- > 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]>
