Restore MySQL database from sql dump file?

This is more of a personal note for myself because I keep forgetting the syntax :p.

When developing web applications I often, 'mess around' with the database and I then need to restore it to make sure everything is running ok, (or simply to run some kind of test again and again).
MySQL, (my current development database here), allows me to reload the db from the command line. And the command is...

Replace USERNAME with your database username, DATABASE with your database name and of course the 'dumpo.sql' with the name of your sql dump file.

You will then be asked to enter your password and the update should happen with not too much problems.

if you get an error message like "'mysql.exe' is not recignized as ab internal or external command, ...." this is because mysql is not in your &#xpa;th%, so you will need to run the command above with the full path where mysql.exe is located, (normally in your program files directory).

06h37 - 5/31/2011 - comments {0} - post comment

register_shutdown_function(...) doesn't work with ob_gzhandler(...)

[I have decided to start adding some entries about the re-factoring of journal home, either it will help someone else or someone will be able to offer some comments]

I am busy doing a lot of changes to the code of Journalhome.com to ensure that it runs better than the current software, (that is no longer supported in any case). My aim is to speed up the whole delivery of the page to the browsers.
Some of the tools used to speed up the delivery of pages is compression with things like ob_gzhander and ob_start

The problem with that is that some code that I want to be executed at the very end of the script, (as the script is completing) it does not seem to be executed.

In php when you call ob_start('ob_gzhandler'); it tells the php compiler to take all the output, (everything going to the screen), and, instead of sending it to the screen we will send the string to a function called ob_gzhandler who in turn will return a compressed string.

Normally the way it works is:

Code =//=> PHP compiler=//=> Send to the browser (as soon as code want it to go, we cannot get it back) =//=> Do do some completion code

With ob_start( ... ) it is a litte bit more complex

Code =//=> ob_start( ... )  PHP compiler=//=> ob_end_flush(...) =//=> Send to the browser, (all at once) =//=> Do do some completion code

What this means is that the created page is sent out as one big string to the browser.
In practice, a page is almost always sent as one big chunk of string, but we cannot really control the string that is sent out. So we can call a function to 'handle'  the string and do what we want with it.

Code =//=> ob_start( 'ob_gzhandler' )  PHP compiler=//=> ob_end_flush(...)  =//=>
                                                                                             ob_gzhandler( $str ) { // compress it }  =//=>
                                                                                               Send that to the browser, (all at once) =//=> Do do some completion code 

The problem with that is the function ob_gzhandler(...) does not seem to allow the "Do do some completion code"

The problem is almost certainly with register_shutdown_function(...), because as the manual clearly says, if any of the registered function call exit() then the processing will stop completely and no other registered function will be called.
So I can only guess that ob_gzhandler(...)  itself registers a function that calls exit(), (of course this is only a guess).

The other bigger problem with that logic, (and kind of backs up my theory), is that it seems to allow _some_of the registered code to be completed. This makes sense as the shutdown functions are called in the order they are registered so the ones registered before ob_start('ob_gzhandler'); will be executed but not the ones after.

For example...

function foo()
{
  echo "This should be called last";
}

ob_start('ob_gzhandler'); // replace with ob_start(); for it to work
register_shutdown_function('foo');
echo "This is called now
";
?>

JournalHome.com has created this blog for the purpose of keeping members and visitors up to date with JournalHome.com site information.
The easiest way to stay up to date is by using the RSS/XML feed.
Place this URL within your rss aggregator and it will automatically update itself whenever a new journal entry is published.