Comments on: Supergeek MySQL Tech Bleg

By: Cappy

Cappy — Thu, 22 Jan 2009 00:53:18 +0000

Yeah. Man up and use a real DBMS.

By: Les Jones

Les Jones — Mon, 19 Jan 2009 15:50:49 +0000

Just wait a few days. Once Obama is in office all SQL queries will return the correct results. Also, you’ll be able to successfully divide by zero.

By: Preston Taylor Holmes

Preston Taylor Holmes — Wed, 14 Jan 2009 14:08:05 +0000

I was able to overcome my main issue by migrating all my dbs to the same server, which enabled me to copy the db. I have a feeling the problem with my export/import is the collation my DB is in, so I may have a fix for that but haven’t had time to mess with it. Thanks for the help guys.

By: badanov

badanov — Wed, 14 Jan 2009 12:06:50 +0000

I have essentially a similar problem with backups using PostgreSQL.

In PostgreSQL I have the option of dumping data using PG’s own format or a more universal INSERT mode, which enables me to export to any other SQL database. For some reason that PG mode doesn’t work but the universal mode works famously

By: Doug H

Doug H — Mon, 12 Jan 2009 16:30:35 +0000

I’m used to MS SQL Server, rather than MySQL, but have you tried inserting directly from one database to the other?

In transact SQL, the syntax is DATABASE_NAME.OWNER.TABLE_NAME

So inserting into a table in another database would look like:
Insert Into TestDatabase.dbo.Comments (field, list, here)
Select field, list, here from dbo.Comments

Again, I don’t know if this syntax works in MySQL, but that’s how I would do it in full SQL Server.

By: Chris Short

Chris Short — Sun, 11 Jan 2009 21:24:06 +0000

Try splitting it up into multiple backups then look for malformed syntax in the comments that might be mucking up the works.