Hi;
I need to see the table structure of all the tables of a database I have. I
could also just dump all the data from all the tables in the database and copy
the database, thus grabbing the table structures. I can´t find in the
documentation how to do either of those. Please advise.
TIA,
Tony
Yes, please, email it to me.
Tony
-Original Message-
From: Olaf Stein [EMAIL PROTECTED]
To: [EMAIL PROTECTED]; MySql mysql@lists.mysql.com
Sent: Mon, 23 Jul 2007 12:22 pm
Subject: Re: Seeing Table Structure
I don't know of any way of doing this for all tables.
wrote a python
That works. Thanks.
Tony
-Original Message-
From: Mogens Melander [EMAIL PROTECTED]
To: Olaf Stein [EMAIL PROTECTED]
Cc: [EMAIL PROTECTED]; MySql mysql@lists.mysql.com
Sent: Mon, 23 Jul 2007 12:29 pm
Subject: Re: Seeing Table Structure
Try this:
# mysqldump -d DBNAME tables.sql
Hi;
I mysqldump'd a dbase, created a new empty dbase by another name, then injected
the old dbase into the new. They both exist. I then dumped out all the prods
and categories from the new dbase and created new cats. However, when I surf to
my TTW interface to add new prods, the *old* cats show
It appears to me that the problem is not only in the TTW, since I can add a
prod in the TTW with a cat not found in the new database, but rather found in
the old dbase. Furthermore, both prods show up in MySQL and in the TTW
interface. I have cleared all caches, rebooted Zope (the TTW), even
It appears to me that the problem is not only in the TTW, since I can add a
prod in the TTW with a cat not found in the new database, but rather found in
the old dbase. Furthermore, both prods show up in MySQL and in the TTW
interface. I have cleared all caches, rebooted Zope (the TTW), even
Hi;
I have an unusual problem. My current production server's OS is corrupt and I'm
building a new one. However, due to the corruption, I can't move files out of
it. I have a back door through Zope, but I can only move files of a certain
size (I don't know how large ;). I need to back up a
-Original Message-
From: [EMAIL PROTECTED]
To: mysql@lists.mysql.com
Sent: Thu, 1 Mar 2007 6:01 AM
Subject: Re: Breaking Up Tables
Otherwise you're looking at perhaps select limit 0,1000, 1000,1000, 2000,1000
etc ..
Can you clean up this command? I can't find documentation on the
-Original Message-
From: [EMAIL PROTECTED]
To: mysql@lists.mysql.com
Sent: Thu, 1 Mar 2007 10:00 AM
Subject: Re: Breaking Up Tables
It's nothing to do with mysqldump - it's part of the SELECT syntax for regular
queries.
Then I'm confused as to what you're suggesting I do. I need to
-Original Message-
From: [EMAIL PROTECTED]
To: mysql@lists.mysql.com
Sent: Thu, 1 Mar 2007 10:35 AM
Subject: Re: [inbox] Re: Breaking Up Tables
if you have shell access on the server, why not just use
split? Create your big dump file, split it into smaller
chunks and use cat on the
-Original Message-
From: [EMAIL PROTECTED]
To: mysql@lists.mysql.com
Sent: Thu, 1 Mar 2007 11:47 AM
Subject: Re: [inbox] Re: Breaking Up Tables
Hope this helps.
Sure does! Thanks a bunch :))
Tony
AOL now offers
-Original Message-
From: [EMAIL PROTECTED]
To: mysql@lists.mysql.com
Sent: Tue, 27 Feb 2007 7:34 PM
Subject: Re: Installation Gone Haywire
have you run mysql_install_db on your production server?
I ran that, but I still got the same problem:
# Starting mysqld daemon with databases from
-Original Message-
From: [EMAIL PROTECTED]
To: mysql@lists.mysql.com
Sent: Tue, 27 Feb 2007 7:34 PM
Subject: Re: Installation Gone Haywire
have you run mysql_install_db on your production server?
Let me add more to my response. After running your command, I have these three
problems
Hi;
I successfully installed MySQL 5.1 from FreeBSD port on both my home server and
the new production server I'm building. Then, stupidly, I taught myself that
one can delete actual files when deleting symlinks :( I wiped out my entire
/usr/local/include dir. Since I had a duplicate on my home
14 matches
Mail list logo
