tejeswarp / tungsten-replicator

Automatically exported from code.google.com/p/tungsten-replicator
0 stars 0 forks source link

Document ReplDBMSEvent structure #494

Closed GoogleCodeExporter closed 9 years ago

GoogleCodeExporter commented 9 years ago
What steps will reproduce the problem?

1. Try writing some filter working on row replication events.

What is the expected output?

Structure of event (transaction) is clear.

What do you see instead?

It's mysterious each time you try to use it.

What is the possible cause?

ReplDBMSEvent structure is too complex and not documented.

What is the proposed solution?

At least document what we have now.

Additional information

Looking at filter implementation is a good place to grasp how we're using this 
structure currently. Also, Robert is a good person to ask about details (this 
task was originally assigned to him). Linas & Stephane can help too.

Afterwards we'll need to simplify this structure by providing wrapper classes 
(that's a separate issue).

Original issue reported on code.google.com by linas.vi...@continuent.com on 20 Mar 2013 at 8:32

GoogleCodeExporter commented 9 years ago

Original comment by linas.vi...@continuent.com on 20 Mar 2013 at 8:35

GoogleCodeExporter commented 9 years ago
Instead, let's implement RbrRowChange, RbrRowImage, etc. wrappers. It will make 
it easier for the users to work on.

Original comment by linas.vi...@continuent.com on 20 Mar 2013 at 3:42

GoogleCodeExporter commented 9 years ago
We'll use 2.1.0 instead of 2.0.8, hence moving the issues.

Original comment by linas.vi...@continuent.com on 27 Mar 2013 at 3:14