Rethinkdb support Dropped?

[Roy Nasser]

Hi,

My colleagues and I have noted the rethinkdb example has been very recently deleted...  

One of our engineers has made the mysq-to-rethinkdb example work (it wasnt working in the example), but we have noticed that the sync is only supporting mysql Inserts.

Any reason why it was removed?  Any idea if we can fix it and contribute it back?

We need to learn a bit more about how the rows are identified, so we can send the appropriate update/delete commands into rethink... any other example that supports Update/Delete?

We noticed the Redis example seems to have a "id" column, but is it possible to write something more generic?  maybe finding the pkey of the mysql table dynamically?

thanks!

[Julien Duponchelle]

Hi,

I dropped the RethinkDB example because no body was keeping us up to date and people start to report issues. Don't hesitate to contribute it back. You can probably use the primary key with some introspection using SQL queries. 

Thanks !

--
You received this message because you are subscribed to the Google Groups "Python MySQL replication" group.
To unsubscribe from this group and stop receiving emails from it, send an email to python-mysql-repli...@googlegroups.com.
For more options, visit https://groups.google.com/d/optout.

[Roy Nasser]

Thanks for the repli Julien, we will try to get it working again.  My colleague André already posted a working example, but it works only for Inserts in mysql.  We will work on other events.