Mysql database offline-online synchronization
As per your requirement you're suggesting leads to this solution:

mysqlbinlog --start-datetime=&lt;START_DATETIME&gt; --stop-datetime=&lt;STOP_DATETIME&gt; binlog.xxx &gt; binlog.xxx.sql

Though this is very much prone to corrupt your data and/or introduce inconsistency! Not recommended!

There can be multiple solutions to one problem, if you could share the scenario you would get a better solution.

For eg: 


If you're planning to make application specific changes on development (local) server and want to push that to live, use version control to manage the SQLs and exec to live.
If it is only specific database, you can setup replication and only move replicate changes to that db (or even tables).