Paul McNett wrote: > Basically, every transaction commited to the database resulted in my > replicants getting updated nearly simultaneously. I'd back up the data > from one of the replicants. > > To make this work, IIRC, you need to enable binary logging and grant > proper permissions to the replicants. > > This can also be used to distribute load, so that your read-only client > accesses can query against the more local replicated copy, while writes > to the database go to the master. > > Google for 'mysql replication' if interested. That will probably get you > what you need. This was back in MySQL 3.23 days... perhaps it is known > as something else now. > >
Replication is not a choice here, as it's just a little ol' 2 person office with one server PC. The amount required to inject replication into this scenario is more work than I'm willing to do, and certainly more than they're willing to pay for. But thanks just the same for the idea/suggestion! _______________________________________________ Post Messages to: [email protected] Subscription Maintenance: http://leafe.com/mailman/listinfo/profox OT-free version of this list: http://leafe.com/mailman/listinfo/profoxtech Searchable Archive: http://leafe.com/archives/search/profox This message: http://leafe.com/archives/byMID/profox/[EMAIL PROTECTED] ** All postings, unless explicitly stated otherwise, are the opinions of the author, and do not constitute legal or medical advice. This statement is added to the messages for those lawyers who are too stupid to see the obvious.
