Login ProductsSalesSupportDownloadsAbout |
Home » Technical Support » ElevateDB Technical Support » Support Forums » ElevateDB SQL » View Thread |
Messages 11 to 12 of 12 total |
chained master-detail deletions not working |
Mon, Dec 7 2009 7:23 AM | Permanent Link |
"Lucian Radulescu" | Tim Young wrote:
> Lucian, > > << I chahnged a bit the name of tables, but anyway, now all before > delete triggers look very simple, they call a procedure. The thing is > I'm having problems with the procedure. >> > > Ahh, okay. The problem is with the START TRANSACTION - it does not > accept variables in the ON TABLES clause, so you're going to have to > do something klunky like this: > > CASE TableName > WHEN 'Versions' THEN > START TRANSACTION ON TABLES Versions; > WHEN 'Apps' THEN > START TRANSACTION ON TABLES 'Apps'; > END CASE; It seems it was not only that. This didn't work: INTRANSACTION(''), once I passed there a table name, it works fine. Or if it's used clean without the empty parameter, just INTRANSACTION Thanks, Lucian |
Mon, Dec 7 2009 2:10 PM | Permanent Link |
Tim Young [Elevate Software] Elevate Software, Inc. timyoung@elevatesoft.com | Lucian,
<< It seems it was not only that. This didn't work: INTRANSACTION(''), once I passed there a table name, it works fine. Or if it's used clean without the empty parameter, just INTRANSACTION >> Yes, EDB interprets INTRANSACTION('') as "is the table <blank> involved in the current transaction" which, of course, always evaluates to False. -- Tim Young Elevate Software www.elevatesoft.com |
« Previous Page | Page 2 of 2 | |
Jump to Page: 1 2 |
This web page was last updated on Saturday, May 4, 2024 at 12:54 AM | Privacy PolicySite Map © 2024 Elevate Software, Inc. All Rights Reserved Questions or comments ? E-mail us at info@elevatesoft.com |