[rotorboy]

peterlaursen wrote on Oct 5 2006, 10:35 AM:

WE CANNOT AFFORD TO BE THAT NAIVE ABOUT OUR MARKET POSITION!

That's incredibly true. The reason I purchased this software yesterday was the “replication” feature alone. Now it's ok for some basic tasks, but what I really need is what I've outlined.

I understand the concern about “sue-age” when some numbskull screws things up and wants to pin the blame on someone else, sure we see it every day. This threat can be minimized with a strong EULA and a big fat DISCLAIMER for any feature you feel has an inherent risk.

For example. If I have 2 databases and I click the 2-way replication feature, not realizing that the source will overwrite the target rows if they should be different – that could be rather nasty. Where I'm sitting, that's just as dangerous, perhaps even more dangerous, than the odd chance of a timestamp being far enough out to screw up my data.

So. Do you offer a full solution and a EULA and DISCLAIMER that covers your butt, or do you offer a product that only handles a portion of what the users need? From what I can see so far, this is a nice package. More replication options would only make it even more useful. Hey, you can even go as far as to have 3 levels of protection. You must accept the terms on download. You accept them on install, and you accept them before you use “dangerous” features.

[rotorboy]

It's our own responsibility to ensure our servers have properly synchronised time. It's not a huge deal to have a check in place to ensure any replication machines are using something close to the same time. It's just a tool that would be incredibly useful to those of us whom are in shops that can't spend tens (hundreds) of thousands on big expensive commercial grade solutions. At the very least, we can run a MySQL (5+) Master-Master setup and have the tools to deal with the odd breakages if/when they occur.

Timestamps — yeah that's right I forgot about that… I don't actually do the implementation of the databases and tables, I'm just the guy that administers the servers and fixes the problems.

[rotorboy]

I appologize in advance for jumping in here only a couple hours after I purchased this software.

We are currently running MySQL 5.0.20 on a Master-Master setup of 2 machines. The system is used by a pair of webservers running a busy Ecommerce store where the load is split between the 2 machines. Most of the load is visitors viewing pages of products with only a few actual orders per day. So far this has been running smoothly for months at a time.

The databases are setup with a trigger to update a timestamp on each row whenever an update is done. What I need is the ability to use our timestamp field to bring the 2 systems back into sync so I can restore MySQL replication.

Example:

IF timestamp on Alpha is newer than timestamp on Beta, Select ROW from Alpha and update ROW to Beta.

ELSEIF timestamp on Beta is newer than timestamp on Alpha, Select ROW from Beta and update ROW to Alpha.

ELSEIF ROW doesn't exist on Beta INSERT to BETA

ELSEIF ROW doesn't exist on Alpha INSERT to ALPHA

Anyway, you all get what I mean I'm sure.

I've read this thread. It seems that WebYog doesn't yet provide this function for an assortment of reasons, yet there seems to be a number of people looking for this option. Even if it's NOT the ideal setup, it's pretty damn close, in my experience, close enough to handle 99.9% of anything I'm faced with.

So…. what would it take to convince the developers of what seems to be a beautiful software package to put in some ability to handle this? Use BIG disclaimers or say it only works on 5.x or whatever…

[Author]

Posts