Not a problem... Extra info in the replication stream (stmt-based) says
what NOW and RAND should return for the next statement.
I don't know if non-deterministic UDFs are in issue.
MySQL Geeks - Consulting & Review
> -----Original Message-----
> From: Jesse [mailto:jc@stripped]
> Sent: Tuesday, July 15, 2008 4:46 AM
> To: replication@stripped
> Subject: Re: Questions about replication
> > I've been a bit concerned about statement based replication
> - if you ever
> > use non-deterministic functions like NOW() and RAND(), your
> master and
> > slave may contain different data, and row-based replication
> solves that.
> > I'm running 5.1 locally for development and have not seen
> any problems,
> > but I've not deployed it anywhere yet.
> That was kind of my concern. I do use some triggers that use
> Now() to load
> up an AddedDate, or UpdatedDate field. I don't believe I use
> Rand() in
> anything. I use that in my code from time-to-time in the
> ORDER BY clause to
> produce a randomly sorted list, but I don't believe I'm using
> that anywhere
> other than that.
> I'm not comfortable using a beta for our production
> databases, so I guess
> RBR will be out of the question until they get a final release of 5.1
> > Take a look at the maatkit scripts
> (http://www.maatkit.org/) for keeping
> > an eye on your replication slave contents.
> Those appear to be perl scripts. We're using Microsoft
> servers. However, I
> did install a perl script runner at one point, but not being
> familiar with
> it or Linux much, I had difficulty getting it to run. At any
> rate, once I
> get this thing going, hopefully I'll be able to use this to
> make sure that
> replication is working.
> MySQL Replication Mailing List
> For list archives: http://lists.mysql.com/replication
> To unsubscribe: