to other
external applications/systems + with a good serialization ( e.g. Kryo ) to
lower the bandwidth consumption.
Cheers,
George
--
View this message in context:
http://apache-database.10148.n7.nabble.com/Re-Derby-replication-system-Need-help-tp138003p143749.html
Sent from the Apache Derby
On 03/23/2014 10:22 PM, spykee wrote:
Hi,
From my application tables ( for each table I have a trigger for INSERT,
UPDATE and DELETE operation), I will need two important information:
a) the columns names which changed when an update SQL occured.
b) the columns values that changed during an
a specific message with
this information.
There is no other ways of avoiding using Java code for these tasks ?
Please advice me.
Regards,
George
--
View this message in context:
http://apache-database.10148.n7.nabble.com/Re-Derby-replication-system-Need-help-tp138003p138203.html
Sent from the Apache
for the advice, really helpful.*
Cheers,
George
--
View this message in context:
http://apache-database.10148.n7.nabble.com/Re-Derby-replication-system-Need-help-tp138003p138235.html
Sent from the Apache Derby Users mailing list archive at Nabble.com.
to implement experiment.
Regards,
George
--
View this message in context:
http://apache-database.10148.n7.nabble.com/Re-Derby-replication-system-Need-help-tp138003p138188.html
Sent from the Apache Derby Users mailing list archive at Nabble.com.
-system-Need-help-tp138003p138081.html
Sent from the Apache Derby Users mailing list archive at Nabble.com.
--
Regards,
Dyre
in context:
http://apache-database.10148.n7.nabble.com/Re-Derby-replication-system-Need-help-tp138003p138039.html
Sent from the Apache Derby Users mailing list archive at Nabble.com.
--
Regards,
Dyre
--
View this message in context:
http://apache-database.10148.n7.nabble.com/Re-Derby-replication-system-Need-help-tp138003p138081.html
Sent from the Apache Derby Users mailing list archive at Nabble.com.
On 18/03/2014 22:58, spykee wrote:
Using the monitor approach I will have to make *2 steps:*
- throw a notifier message from the db to the monitor thread ( execute a
stored procedure)
- the monitor thread will then have a logic, and then query the table for
the changes and publish them to the
Hi George, this is a huge topic, but I'll try to answer some of your
questions inline:
On 03/16/2014 04:19 PM, George Toma wrote:
Hi all,
I'm trying to achieve the following functionality and I would like an
opinion, advice from more experienced people:
- the goal is to provide a
protocol buffers.
Any other tips other than using a single table which will fire one
thread/message (the stored procedure triggered by the INSERT trigger from
tReplication table) ?
Regards,
George
--
View this message in context:
http://apache-database.10148.n7.nabble.com/Re-Derby-replication-system
Hi all,
I'm trying to achieve the following functionality and I would like an
opinion, advice from more experienced people:
-
the goal is to provide a replication system which will publish messages
to a JMS queue ( OpenMQ) based on the changes that occur in the
database tables.
12 matches
Mail list logo