AW: How can i duplocate a database???? i 've tried mysqldump can get it towork ANy ideas??

Hi Jorge, you usually do something like mysqldump -u USER -p TABLE > FILE where TABLE is dumped to the FILE. USER must have privileges to do so (I usually take the superuser). The other way around you simply have to do mysql -u USER -p TABLE < FILE Should work then, Tobias. -Ursprünglich

AW: Duplicate Entry in Key 1

t the error message. Cheers, Tobias. -Ursprüngliche Nachricht- Von: [EMAIL PROTECTED] [mailto:[EMAIL PROTECTED]]Im Auftrag von Gerald L. Clark Gesendet: Donnerstag, 8. März 2001 18:40 An: Tobias Wolff Cc: Mysql Betreff: Re: Duplicate Entry in Key 1 Tobias Wolff wrote: > > Hello, > I

Duplicate Entry in Key 1

Hello, I have searched the mailing list for this topic, but didn't find a match vor my problem. I am working on Linux Mandrake with MySQL 3.23.33 installed from the RPMs for Mandrake. I am trying to convert a ACCESS database to MySQL using a perl script. The script makes connections to the ACCESS

AW: PHP and MySQL

You have to edit your "php.ini" file, usually located in /usr/local/lib. There is an option called "mysql.default_socket". The value of this options is the path to the mysql socket file. Your systems seems to search the socket file at "/var/lib/mysql/mysql.sock". It might be at a different place,

AW: version 3.23.29a-1

The binary may have a different name. If there is only a /usr/bin/perl you may have to create and symbolic link. Tobias. -Ursprüngliche Nachricht- Von: acci [mailto:[EMAIL PROTECTED]] Gesendet: Mittwoch, 28. Februar 2001 13:53 An: [EMAIL PROTECTED] Betreff: version 3.23.29a-1 I have tr

AW: EXPLAIN with unexpected result.

Hi Simon, thanks for your response. So, would it be wise to replace the multi-column index (a,d,b) with (a,d) to avoid the overhead you mentioned when accessing data from a+b?? Thanks again, Tobias. -Ursprüngliche Nachricht- Von: Simon Windsor [mailto:[EMAIL PROTECTED]] Gesendet: Mittwo

EXPLAIN with unexpected result.

Hello, I'm slightly stunned seeing a result from the EXPLAIN statement. I have a table "T" with columns "a", "b", "c", "d" and a multi-column index on (a, b, c) I perform a query: EXPLAIN SELECT * FROM T WHERE a = , d = , b = The result tells me that MySQL is taking index (a, b, c). Why? Fur

Some questions on indexes.

Hello, I have searched for some information on single- and multi-colum indexes, but often it is mentioned that the behaviour is implementation dependend. So I post my questions on this list. If it's the wrong place, please redirect me to the right one. I am currently working with MySQL 3.22.32 o

AW: Display information

Have a look in the manual, it says LIMIT [offset], rows, so you should say: order by id limit 1932, 10; SELECT [STRAIGHT_JOIN] [SQL_SMALL_RESULT] [SQL_BIG_RESULT] [HIGH_PRIORITY] [DISTINCT | DISTINCTROW | ALL]select_expression,... [INTO OUTFILE 'file_name' export_options][FRO

Switching from 3.22.32 to 3.23.33. What about the database files?

Hello, can anyone tell me whether or not I have to convert the database files when switching from MySQL Version 3.22.32 to Version 3.23.33. I am working on SuSe Linux 6.4. Is it sufficient just to copy the database files? Thanks, Tobias. --