Hi:
I have the following python code:
import os
os.system(mysqldump -u root -pPASSWORD --opt spreadsheets dump.sql)
This nicely creates the file...but the file is empty! The database exists
and has lots of data, I double-checked it. If there is nothing wrong with my
code, is there some way to do
I have two tables:
PtActive
ptNum // the patient's number
user // the user who made this patient active
expires// when the patient becomes inactive again
primary index: PtNum
PtName
ptNum
sequence
lname
fname
primary index: ptNum, sequence
The table PtName may have multiple
My local windows machine has mysql 5.1.33 installed on it. One of my
Mac OSX dev servers has some 4.1 flavor of MySQL on it.
When I try to do something like the following: mysqldump -h devserver
-u me -p somedb dump.sql
I get the following:
mysqldump: Error: 'Table 'information_schema.files'
If you look at the options for mysqldump more closely, you will see
that you can specify the version of the server which will be importing
the result file. These cause MySQL to taylor the SQL syntax according
to the target platform.
- michael dykman
On Wed, Sep 2, 2009 at 11:03 AM, Matt
[Sorry if you receive multiple copies of this message.]
[Please feel free to forward the message to others who may be
interested.]
Hi,
We are a computer systems research group at the Computer Science
department at Rutgers University, and are conducting research on
simplifying the software
On 9/2/2009 3:43 AM Victor Subervi said...
Hi:
I have the following python code:
import os
os.system(mysqldump -u root -pPASSWORD --opt spreadsheets dump.sql)
First, test this at the system command line -- you'll likely get an
empty file there as well, so calling from within python simply
Hi Matt,
The error you are getting is very particular to information_schema
database.
Information_schema does NOT actually have tables, they are views:
|INFORMATION_SCHEMA| is the information database, the place that stores
information about all the other databases that the MySQL server
Does anyone have any information regarding my question?
Is the 'share/mysql_fix_privilege_tables.sql' script distributed with MySQL the
same as the script (represented as '[fix_priv_tables]') generated interally by
the mysql_upgrade command that contains SQL statements to upgrade the tables in
While not python, maybe this bash script will give you some clues?
http://daevid.com/content/examples/daily_backup.php
Also, please don't cross post to multiple lists. Not everyone on this mySQL
list is on the python list and vice versa. It's just bad netiquette.
-Original Message-
I checked my own backup script from earlier years and everything was good.
You know, if I could simply figure out where the data was actually stored,
in what file, I could copy it over to another computer. Any ideas?
Thanks,
V
On Wed, Sep 2, 2009 at 4:09 PM, Daevid Vincent dae...@daevid.com
Can you please send me a script to do that?
I have MySQL Reference Manual for version 3.23.55.
/* Copyright Abandoned 1996, 1999, 2001 MySQL AB
This file is public domain and comes with NO WARRANTY of any kind */
/* Version numbers for protocol mysqld */
#ifdef _CUSTOMCONFIG_
#include
If it's MYISAM tables, then they're all self contained in folders in
/var/lib/mysql/spreadsheets. Remember that if you do copy the files, to shut
down mysql first or you could copy corrupt files.
If you're using INNODB, then the schema is in that folder, but the actual
data is in the
Not in Windoze. The only folders I have inside the Programs/MySQL are Docs,
bin and Shared
V
On Wed, Sep 2, 2009 at 5:29 PM, Daevid Vincent dae...@daevid.com wrote:
If it's MYISAM tables, then they're all self contained in folders in
/var/lib/mysql/spreadsheets. Remember that if you do copy
Uma Mudumba wrote:
Can you please send me a script to do that?
I have MySQL Reference Manual for version 3.23.55.
/* Copyright Abandoned 1996, 1999, 2001 MySQL AB
This file is public domain and comes with NO WARRANTY of any kind */
/* Version numbers for protocol mysqld */
#ifdef
On Fri, Aug 28, 2009 at 9:18 AM, Shawn Green shawn.gr...@sun.com wrote:
Hank wrote:
Hello All,
I'm in the process of upgrading my database from 4.1 to 5.0 on CentOS.
I've been testing the mysqlcheck --check-upgrade --auto-repair
command,
and on one of my MYISAM tables, it's taking
Hello All,
I have a legacy application which was written using a compound primary key
of an item number (non unique) along with a category ID. The combination of
the item number and category ID make the records unique.
I am in the process of replacing the compound (VARCHAR) keys with an
Do you know that if you create seq column on the original table as an
auto_increment primary key, it will fill in the numbers automatically? There's
no need to create the values on another table and update with a join.
Regards,
Gavin Towey
-Original Message-
From: Hank
Hello Gavin,
That's what I did with the first one-to-one table to create the unique SEQ
field mapping to each item/category combination. The problem is on the
TRANSACTION table, where there are multiple instances of each item/category.
If I just put a auto_increment primary key on that table,
18 matches
Mail list logo
