Word Virus » mySQL http://wordvirus.us The word is now a virus. - William S. Burroughs Mon, 06 Feb 2012 11:00:05 +0000 en hourly 1 http://wordpress.org/?v=3.3.1 Copying a database between MySQL servers http://wordvirus.us/2011/05/copying-a-database-between-mysql-servers/ http://wordvirus.us/2011/05/copying-a-database-between-mysql-servers/#comments Wed, 25 May 2011 17:40:10 +0000 gabriel http://wordvirus.us/?p=5686 I was trying to migrate a MySQL database today, that contained Chinese characters. When you dump the database to standard out, like you normally would with mysqldump, the export doesn’t keep the Chinese characters. I did all sorts of things with the character set, etc., and nothing seemed to work. I always ended up with garbage on import. Obviously, the database is UTF-8, but the text file doesn’t work the way I expected. I tried the mysqldump command, passing the -r command, specifying the location to output the file. This is supposed to solve this problem, because it’s not going through standard out. However, you are left using standard in for the import, or you can cut in paste into MySQL Workbench. In any case, none of these worked. The characters were always corrupted. After doing a bit of research, and thinking about it for a few, I realized I could pipe the process directly from one MySQL box to another. This shouldn’t have seemed like rocket science, but I’d never thought of doing an export/import like this before. Here’s the syntax.

First, create the database on the remote machine, either by logging in our through mysqladmin.

mysqladmin -h host_name -u user_name -p create db_name

Next, pipe the dump from the original server to the new server.

mysqldump db_name | mysql -h host_name -u user_name -p db_name

This seems like a really easy solution for migration, though I found virtually no documentation on doing such a migration in this manner.

]]> http://wordvirus.us/2011/05/copying-a-database-between-mysql-servers/feed/ 0 Better last key inserted function for mySQL in ColdFusion8 http://wordvirus.us/2008/06/i-guess-i-should-read-the-documentation-for-coldfusion-8-more-often-%c2%a0turns-out-there-is-a-new-feature-when-doing-database-inserts-%c2%a0in-the-cfquery-tag-add-the-parameter-result8221/ http://wordvirus.us/2008/06/i-guess-i-should-read-the-documentation-for-coldfusion-8-more-often-%c2%a0turns-out-there-is-a-new-feature-when-doing-database-inserts-%c2%a0in-the-cfquery-tag-add-the-parameter-result8221/#comments Fri, 27 Jun 2008 01:29:00 +0000 gabriel http://tumblr.themadness.org/post/40012728

I guess I should read the documentation for ColdFusion 8 more often.  Turns out, there is a new feature when doing database inserts.  In the CFQUERY tag, add the parameter result=”somename”.  You can now reference the data inserted into the query, as well as, a really cool new feature, the last inserted key.  Each database type has a different name for this.  MySQL calls it GENERATED_KEY.  You no longer need to do a second query to get back the last_insert_id().

<cfquery datasource=”#application.dsn#” result=”insertPhoto”>

INSERT INTO kidPhotos

(subject, body, dateOf, siteType)

VALUES

(<cfqueryparam value=”#subject#” cfsqltype=”cf_sql_varchar”>,

<cfqueryparam value=”#body#” cfsqltype=”cf_sql_varchar”>,

‘#dateformat(date, “yyyy-mm-dd”)#’,

‘ap’)

</cfquery>

]]> http://wordvirus.us/2008/06/i-guess-i-should-read-the-documentation-for-coldfusion-8-more-often-%c2%a0turns-out-there-is-a-new-feature-when-doing-database-inserts-%c2%a0in-the-cfquery-tag-add-the-parameter-result8221/feed/ 0