What you might try is keeping an incremental log of each completed transaction (yes, I believe MySQL only allows "transactions", properly so-called, via a somewhat hackish maneuver at the moment -- so read this as "UPDATE, INSERT or DELETE") that's been issued since the last time your script ran; presumably, this means you'll have to have access to the apps that are used for updating the internal database so they can write the logs. And be prepared to learn all about file locking, too, because you'll want the updaters to be unable to add to the file when you're reading from it to do the updates (any updates recorded while the script is running will have to go to some sort of temp file ... and thinking about the concurrency issues is making my head spin) ...
Or maybe MySQL can do this on its own (I'm pretty sure Oracle etc. has such a facility).
Then you simply issue those SQL commands to the publically accessible DB and ba da bing!
Hope that's workable ..
Philosophy can be made out of anything. Or less -- Jerry A. Fodor
Are you posting in the right place? Check out Where do I post X? to know for sure.
Posts may use any of the Perl Monks Approved HTML tags. Currently these include the following:
<code> <a> <b> <big>
<blockquote> <br /> <dd>
<dl> <dt> <em> <font>
<h1> <h2> <h3> <h4>
<h5> <h6> <hr /> <i>
<li> <nbsp> <ol> <p>
<small> <strike> <strong>
<sub> <sup> <table>
<td> <th> <tr> <tt>
Snippets of code should be wrapped in
<code> tags not
<pre> tags. In fact, <pre>
tags should generally be avoided. If they must
be used, extreme care should be
taken to ensure that their contents do not
have long lines (<70 chars), in order to prevent
horizontal scrolling (and possible janitor
Want more info? How to link or
or How to display code and escape characters
are good places to start.