lp:~jaypipes/drizzle/replication-ddl

Created by Jay Pipes and last modified
Get this branch:
bzr branch lp:~jaypipes/drizzle/replication-ddl
Only Jay Pipes can upload to this branch. If you are Jay Pipes please log in for upload directions.

Branch merges

Related bugs

Related blueprints

Branch information

Owner:
Jay Pipes
Project:
Drizzle
Status:
Merged

Recent revisions

1427. By Jay Pipes <jpipes@serialcoder>

Try another const_cast<> technique on pthread_traits.

1426. By Jay Pipes <jpipes@serialcoder>

Merge trunk

1425. By Jay Pipes <jpipes@serialcoder>

merge replication-api

1424. By Jay Pipes <jpipes@serialcoder>

merge trunk

1423. By Jay Pipes <jpipes@serialcoder>

Fix cpplint header guard.

1422. By Jay Pipes <jpipes@serialcoder>

Merge trunk

1421. By Jay Pipes <jpipes@serialcoder>

OK, Sun Studio still didn't like that...seems to think that inline means something different than other compilers think it is...

1420. By Jay Pipes <jpipes@serialcoder>

Sun Studio says inlined functions must be defined before being called...

1419. By Jay Pipes <jpipes@serialcoder>

Add Solaris atomics fixes and test files. Add replication.h header to makefile.

1418. By Jay Pipes <jpipes@serialcoder>

* Fixes drizzled's atomics:

- fetch_and_add() was actually add_and_fetch() - fixed to have both methods correct
- compare_and_swap() was incorrect for all traits classes. Fixed to return a bool
true only when the supplied value is actually swapped
- fixes increment() and decrement() methods and operator+=() in outer atomics class
template to call proper add_and_fetch() methods on traits classes
- Now that above are fixed, removed the hacks in Query_id and TransactionLog to
have query ID and the new transactoin ID start properly at 1.

* Transaction messages sent over replication stream now use
a real transaction ID, managed by drizzled::TransactionServices. Previously,
the Query_id was being used, resulting in SELECT statements incrementing the
transaction ID.

* Added a test case to ensure that DDL ops are given a transaction ID and SELECT
ops do not increment the transaction ID.

The transaction ID will be paired with a channel ID to become the global
transaction identifier. ReplicationServices will manage the pairing of
channel and transaction ID and understand how far a particular subscriber
node has applied.

Branch metadata

Branch format:
Branch format 7
Repository format:
Bazaar repository format 2a (needs bzr 1.16 or later)
Stacked on:
lp:~drizzle-trunk/drizzle/development
This branch contains Public information 
Everyone can see this information.

Subscribers