There seems to be some confusion about 'multi-db'.Within a single
MySQL instance, assuming that all your tables are a transactional type
(InnoDB isn't the only one), you don't have to do anything special to
cross database boundaries. XA is required if you plan to spread your
transactions out
There seems to be some confusion about 'multi-db'.Within a single
MySQL instance, assuming that all your tables are a transactional type
(InnoDB isn't the only one), you don't have to do anything special to
cross database boundaries. XA is required if you plan to spread your
transactions out a
If all the tables are InnoDB, XA isn't needed. It doesn't matter
whether all tables are in the same database.
On Oct 28, 2009, at 5:48 AM, Martijn Tonies wrote:
Ah, works for InnoDB I see.
Nice.
With regards,
Martijn Tonies
Upscene Productions
http://www.upscene.com
Download Database Wor
Ah, works for InnoDB I see.
Nice.
With regards,
Martijn Tonies
Upscene Productions
http://www.upscene.com
Download Database Workbench for Oracle, MS SQL Server, Sybase SQL
Anywhere, MySQL, InterBase, NexusDB and Firebird!
Database questions? Check the forum:
http://www.databasedevelopmentforu
Looks to me we should use XA transaction syntax instead. Check this:
http://dev.mysql.com/doc/refman/5.0/en/xa.html
Thanks,
YY
2009/10/28 Martijn Tonies
> Michael,
>
> Does MySQL support multi-db transactions?
>
> With regards,
>
> Martijn Tonies
> Upscene Productions
> http://www.upscene.com
Michael,
Does MySQL support multi-db transactions?
With regards,
Martijn Tonies
Upscene Productions
http://www.upscene.com
Download Database Workbench for Oracle, MS SQL Server, Sybase SQL
Anywhere, MySQL, InterBase, NexusDB and Firebird!
Database questions? Check the forum:
http://www.databa
That is correct. Many db interfaces off programmatic abstractions of
these facilities, but you may certainly just issue the statments.
START TRANSACTION
INSERT that
UPDATE that
on success: COMMIT
on error: ROLLBACK
- michael dykman
On Wed, Oct 28, 2009 at 12:07 AM, Mosaed AlZamil wrote: