Mike,
- Original Message -
From: "Mike Debnam" <[EMAIL PROTECTED]>
Newsgroups: mailing.database.myodbc
Sent: Sunday, November 21, 2004 9:25 PM
Subject: temporary tables, replication, and innodb tables
I'm working on a new series of queries that share a temporary ta
I'm working on a new series of queries that share a temporary table.
I've tried using both "create temporary table select" and "create
temp table" then "insert into t ... select from y". Both seem to
create a lock that (if the select portion runs long enough) causes a
deadlock with the replica
Sinisa,
SM> It is the same. Replication works already with all table handlers,
SM> but all that remains to be solved is ROLLBACK.
What could be the problem is servers are recording in their
binary log only committed transactions ?
Why should ROLLBACK be implemented in replication
Christian Jaeger writes:
> At 16:17 Uhr +0300 13.7.2001, Sinisa Milivojevic wrote:
> Hi!
>
> We have been planning to use mysql/innodb with replication soon
> (mid/end of august). http://www.mysql.com/doc/B/i/Binary_log.html
> suggests that replication should work with "transactional table(s)
At 16:17 Uhr +0300 13.7.2001, Sinisa Milivojevic wrote:
>Support for transactions in replication will come in MySQL 4.0 that is
>scheduled for this Autumn.
Hi!
We have been planning to use mysql/innodb with replication soon
(mid/end of august). http://www.mysql.com/doc/B/i/Binary_log.html
sug
Jörg Beckmann writes:
> Hi,
>
> I'm thinking about using MySQL with InnoDB and replication. Are there any
> experiences with this configuration, esp. what about transactions? What will
> happen on the slave if transactions are rolled back? What happens if the
> master or the slave crashes while p
Hi,
I'm thinking about using MySQL with InnoDB and replication. Are there any
experiences with this configuration, esp. what about transactions? What will
happen on the slave if transactions are rolled back? What happens if the
master or the slave crashes while processing transactions.
Thanks,
