Now it's time to get serious about replicating to MariaDB from
Oracle, and we are real close now, right? What I needed was a
means of keeping track of what happens in a transaction, such as
a LOG table of some kind, and then an idea of applying this log
to MariaDB when there is a COMMIT in Oracle. And thing is, these
two don't have to be related. So I can have a table which I write
to and also have a Materialized View that is refreshed on COMMIT
on, and I need a log table or something. And when the
Materialized View is refreshed, as there is a COMMIT, then the
log can be applied. From a schematic point-of-view, it looks
something like this:
This looks more complex than it is, actually,
all that is needed is some smart PL/SQL and this will work. I
have not done much of any kind of testing, except checking that
the basics …
In time for Oracle OpenWorld 2014, we released Connector/Python 2.0. We also released a labs release Connector/Python 2.1 and we have a new feature: a C Extension which uses Connector/C.
This C Extension is an optional, an alternative to the pure Python MySQL Client protocol implementation. One of the reasons to implement it was to improve performance in some situations, for example, when huge result sets are returned. Pure Python is still default, if C Extension is not available.
The following post will get your through downloading and installing the MySQL Connector/Python 2.1.0 labs release.
Requirements
- Windows users out of luck; the labs release only compiles on Linux, OSX …
In time for Oracle OpenWorld 2014, we released Connector/Python 2.0. We also released a labs release Connector/Python 2.1 and we have a new feature: a C Extension which uses Connector/C.
This C Extension is an optional, an alternative to the pure Python MySQL Client protocol implementation. One of the reasons to implement it was to improve performance in some situations, for example, when huge result sets are returned. Pure Python is still default, if C Extension is not available.
The following post will get your through downloading and installing the MySQL Connector/Python 2.1.0 labs release.
Requirements
- Windows users out of luck; the labs release only compiles on Linux, OSX and other …
Both MySQL Connector/Python 2.0.1 and 1.2.3 are now available through the Python Package Index or PyPI. Leaving the previous version available is probably a good idea as you can always go back if needed.
Note that we still have no files hosted at PyPI.
In this third installment in this series, I'll explain why the
smart solution I described in the previous post actually wasn't that good, and
then I go on to explain how to fix it, and why that fix wasn't
such a smart thing after all. So, this was the design we ended
with last time:
We have Oracle replicating to a Materialized
View, this to ensure that we can run triggers when the is a
commit, and then triggers on this Materialized View updates
MariaDB by sending a UDP message to a server that in turn is
connected to MariaDB.
The issue with the above thingy was that a Materialized View by
default is refreshed in it's entirety when there is a refresh, so
if the table has 10.000 rows and 1 …
Business Wire Oracle Open World 2014, Booth # 430- Continuent, Inc., a leading provider of open source database clustering and replication solutions, today announced Continuent Tungsten 3.0, a powerful solution that combines advanced clustering and replication technologies to meet the transaction processing and analytic needs of the entire business. Continuent Tungsten 3.0 enables constant,
Get a preview of the next advance in data management technology! Continuent Tungsten 3.0 brings the power of advanced clustering and replication to offer data management needs for your entire business including MySQL high availability, disaster recovery, multi-master operation, and real-time data warehouse loading. With Continuent Tungsten you can apply the full power not just of MySQL but all
We have relocated the MySQL Connector/Python repository on GitHub to the following location:
https://github.com/mysql/mysql-connector-python
The old location will redirect to the above URL.
No, we have not updated the README.txt or made something special for GitHub. I personally don’t mind what is currently showing on GitHub: it is readable, and it is correct. I still hope GitHub will make it easier to show something else, like asking which document to display and as what format.
We have relocated the MySQL Connector/Python repository on GitHub to the following location:
https://github.com/mysql/mysql-connector-python
The old location will redirect to the above URL.
No, we have not updated the README.txt or made something special for GitHub. I personally don’t mind what is currently showing on GitHub: it is readable, and it is correct. I still hope GitHub will make it easier to show something else, like asking which document to display and as what format.
The theme for this series of posts is, and indicated in the
previous post, "Try and try, again", and there
will be more of this now when I start to make this work by
playing with Oracle, with PL/SQL and with the restrictions of
Oracle Express (which is the version I have available).
So, what we have right now is a way of "sending" SQL statements
from Oracle to MariaDB, the question is when and how to send them
from Oracle. The idea for this was then to use triggers on the
Oracle tables to send the data to MariaDB, like this, assuming we
are trying to replicate the orders table from Oracle to
MariaDB:
In Oracle, and assuming that the
extproc I have that created to send UDP …
