-Blake

From my cursory reading of the replication FAQ, it seems to require that I have mysqladmin capabilities. As it is a hosted account, the only privileges are those grandted to specific databases attached to the account. I can not start or restart the server or execute any FLUSH commands (or for that matter, do anything of an administrative nature to the mySQL server.)
--
Filmo the Klown

You can cook up a completely general solution for this, but it takes application and database changes. Put most simply, you need to maintain a last-modified-time column in any table that you want to mirror. Any code that updates or inserts the table needs to update that column with a time of sufficient resolution for your application (usually down to seconds).

With that data available, you can retrieve all rows that are newer than the last time you looked at the table (presumably you're maintaining the last-lookup time in a separate table -- or even a flat file). The only trick is if that if the tables allow row deletion, you have to store at least the primary key of every deleted row in a counterpart table. You can also try to do "soft deletes", where you only mark a row as ready to be deleted, and don't actually delete it until some point in the future. But that gets even more complicated.

One client I work for has a system like this in place for about a hundred tables in dozens of applications. It takes work, but it's effective, and generalizes to all rdbms platforms.

HTH

It's interesting to note that mySQL will auto-magically update the first timestamp column for you. http://www.mysql.com/doc/D/A/DATETIME.html

--
perl -p -e "s/(?:\w);([st])/'\$1/mg"

MySQL 3.23.15 introduced Replication, see (gack, info!) info mysql#Replication. The constraints and hurdles from your provider suggest looking at DBI::Proxy.

After Compline,
Zaxo

[mysqld]
log-update
log-long-format
[download]

# Time: 011206  9:47:01
# User@Host: john[john] @  [10.10.10.112]
INSERT INTO official_holidays (OHDate,OHName) VALUES ( "2000/01/01" , 
+"New Years Day");
[download]

#!/usr/bin/perl -w
use strict;

my $start_copy = 0;
while (<>) {
        next if /^\s+$/;
        if ((!$start_copy) 
          and (/^# Time: (\d+)\s+(\d+):(\d\d):(\d\d)/)) {
                my $date = $1;
                my $hour = $2;
                # check if date and time are what you need
                if ((substr($1,4,2) eq "06") and ($hour gt "09")) {
                        $start_copy = 1;
                }
        }
        print if $start_copy;
}
[download]

update
Sorry, it was SQL_LOG_UPDATE=0
The previous one (SQL_LOG_OFF=1) will only affect the general log file. And, in addition, they have different semantics. :-(
summary:

my $query = qq{
SET SQL_LOG_OFF=1; # no logs to the general log
SET SQL_LOG_UPDATE=0; # no logs to the update log.
UPDATE $table SET bigField = $BLOB_value WHERE ID=1;
SET SQL_LOG_OFF=0; # logs to the general log
SET SQL_LOG_UPDATE=1; # logs to the update log.
UPDATE $another SET smallfield = $smallvalue WHERE ID =3;
};
$dbh->do($query);
[download]

I think you are on the right track with your email the SQL statements idea, that way data only gets sent when there is data to send. Probably slightly more secure than FTP. The other methods suggested so far require more rights or access than you have. You could take your SQL convert to XML then back to SQL, but that would be extra work. You will need to do some sort of integrity/validity checking so someone doesn't email your program a "DELETE sales" command. PGP email may do it.

g_White