This should be working.

You can respond directly to me with schema and SQL that you are using and I can try to reproduce in-house.

Thanks,

Jonathan Miller Austin, Texas USA Senior Quality Assurance Developer MySQL AB www.mysql.com __ ___ ___ ____ __ / |/ /_ __/ __/ __ \/ / / /|_/ / // /\ \/ /_/ / /__ /_/ /_/\_, /___/\___\_\___/ <___/ www.mysql.com

Jumpstart your cluster! http://www.mysql.com/consulting/packaged/cluster.html

Get training on clusters http://www.mysql.com/training/courses/mysql_cluster.html

All-in-one Enterprise-grade Database, Support and Services http://www.mysql.com/network/

-> -----Original Message----- -> From: Cory @ SkyVantage [mailto:las...@skyvantage.com] -> Sent: Thursday, December 15, 2005 1:45 AM -> To: clus...@lists.mysql.com; mys...@lists.mysql.com -> Subject: Transactions (not rolling back on error) -> -> I have a transaction that is very simple, I need to create records in -> multiple tables that are related. If any one insert statement fails or -> throws an error I want to rollback the ENTIRE transaction. -> -> I thought that this was the default functionality, but apparently that's -> not the case here. -> -> I'm running MySQL-Cluster 5.0.something. -> -> Here's a simplified example.. -> -> START TRANSACTION; -> INSERT INTO....; -> INSERT INTO....; -> INSERT INTO....; -> COMMIT; -> -> I'm getting data inserted into some tables when others (or one) throw an -> error. What am I doing wrong? Do I need to put in a conditional -> that checks for an error between each statement? If so, what might that -> look like? -> -> I guess the reason this is so important to me is that Cluster doesn't -> enforce Foriegn Key Rules, so it's important that my relationships are -> maintained by the transaction properly or else I'll have orphaned -> records all over the place... -> -> Thanks in advance! -> -> Cory. -> -> -- -> MySQL Cluster Mailing List -> For list archives: http://lists.mysql.com/cluster -> To unsubscribe: -> http://lists.mysql.com/cluster?unsub=jbmi...@mysql.com