How to import or export SQL dumps via the mysql command console

Importing an SQL dump via the mysql.exe-application is a lot faster than importing via the good old phpMyAdmin web-interface, which takes the pain out of handling huge files.

Hit [WIN] + [R], type cmd and hit enter. The command console window opens.

If you don't have the path to your mysql binaries in your environment variables you will have to navigate there first using the cd console command:

cd c:\PathToWebServer\Mysql\bin>

Then execute the mysql-application and pass the appropiate parameters, as seen in the example below.

Be aware, that there is no space between the parameter identifiers -u and -p, and their corresponding parameter data.

Also note the lower-than operator < between the database name and the filename of the target sql-file.
Reverse this operator to export into that file instead!


# export sql dump to file
mysqldump -uUsername -pPassword DatabaseName > "C:\PathToSQLFile\hugeMySQLDump.sql"

# import sql dump from file
mysql -uUsername -pPassword DatabaseName < "C:\PathToSQLFile\hugeMySQLDump.sql"

There is a lot more you can do with the MySQL console. It does have some pretty useful interactive features. A good starting point to learn about them, is to login in to the mysql and asking for help:


# first login to the mysql shell
mysql -uUsername -pPassword

# you now have a new command prompt, which replaces your windows prompt:
mysql> 

# ask for help, like this:
mysql> help;

Now go and learn the meaning of this Scripture.

Sprite vs. MovieClip in AS3

Just a quote:

Prior to ActionScript 3.0, the MovieClip class was used as an all-purpose graphics container (much like ActionScript 3.0s Sprite class is used). As of ActionScript 3.0, MovieClip is used only to control instances of movieclip symbols created in the Flash authoring tool. Because ActionScript 3.0 does not provide a way to create timeline elements such as frames and tweens, there is no need to create new empty movieclips at runtime in ActionScript 3.0. Instead, all programmatically created graphics should be instances of the appropriate core display class (Bitmap, Shape, Sprite, TextField, etc).

Essential Actionscript 3.0 (Colin Moock)

Flash Cookies aka (Local) SharedObjects

Why?

Because you may sometimes need to save a small amount of data locally on the visiting-users computer. Login data or highscores are common examples.

What?

You can store multiple attributes as long as the user has not explicitly disabled local storage using the Flash Player Settings Manager and as long as the assigned storage-space isn't exceeded.

Each attribute can be an object of any ActionScript or JavaScript type — Array, Number, Boolean, ByteArray, XML, and so on.

ActionScript 3.0 Reference SharedObject#data

Where?

The SharedObject storage-location depends on the clients operating system:

Windows
%AppData%\Macromedia\Flash Player\#SharedObjects
Mac OSX
~/Library/Preferences/Macromedia/Flash Player/#SharedObjects
Unix
~/.macromedia/Flash_Player/#SharedObjects

How?

First you have to import the flash.net.SharedObject-class:

		import flash.net.SharedObject;
	

Then you can retrieve a cookie using the static SharedObject.getLocal-method. If the specified SharedObject does not yet exist, a new one - with a size of 0 bytes - will be created and returned.

Read:

To read data from a cookie you can use dot- or array-syntax to access specific attributes of the data-variable. Iterating over all of the set attributes can be done using a for-in- or for-each-in-loop.

			var so:SharedObject = SharedObject.getLocal("some_cookie_name_you_chose");
			
			if (so.size == 0) {
				trace("The SharedObject is empty! Aborting ...");
				return;
			}
			
			// Iterate over all properties:
			for (var property:Object in so.data) {
				trace(property + ": " + so.data[property]);
			}
			
			// Or access specific properties:
			trace("so.data.SomeValue_01: " + so.data.someValue_01);
			trace("so.data.SomeValue_02: " + so.data.someValue_02);
			trace("so.data.SomeValue_03: " + so.data.someValue_03);
		

Write:

To save attributes to a cookie, you first have to add them to the SharedObjects-data-object and then you need to utilize the flush-method.

			
			var so:SharedObject = SharedObject.getLocal("some_cookie_name_you_chose");
			
			// add some attributes to 'data'
			so.data.someValue_01 = "Are";
			so.data.someValue_02 = "Flash Cookies";
			so.data.someValue_03 = "evil?";
			
			// save changes
			so.flush();
			
		

Delete:

Properties within the data object can be removed by using the top-level delete-method. Setting a property to null or undefined will not suffice.

		var so:SharedObject = SharedObject.getLocal("some_cookie_name_you_chose");
		
		if(so.data.password){
			delete so.data.password;
		}
		
		// save changes
		so.flush();
	

Danke, und auf Wiedersehen.

Syndicate content