transactions - MySQL replication, auto_increment and rollbacks -
i have bunch of scripts perform transactional "simulations" against mysql slave replicant, rolled back. these simulations performed against slave, not affect performance of master database.
i use auto_increment primary keys quite heavily throughout schema , i'm noticing rolling transactions, ids being lost , result on time ids in slave not match of master.
i realise not rolling ids design, not temporarily disable feature (along replication) while simulations run, , turn feature on (along replication).
or there better way of safely performing transactions on real time copy of mysql database?
Comments
Post a Comment