Re: IN(INT VS CHAR)
Hello.
In my humble opinion, the design of the database should not depend
on operators which you're going to use in your queries. Yes, using
INTs in the IN clause (that means the the column type is INT as well,
isn't it?) should be a bit faster, because operations with strings are in
general
slower than with numbers.
Test USER wrote:
When using IN should i design the database to use int's or is the performance
equal?
WHERE col IN('test','test2','test3')
vs
WHERE col IN(1,2,3)
-
FREE E-MAIL IN 1 MINUTE!
- [EMAIL PROTECTED] - http://www.pc.nu
--
For technical support contracts, goto https://order.mysql.com/?ref=ensita
This email is sponsored by Ensita.NET http://www.ensita.net/
__ ___ ___ __
/ |/ /_ __/ __/ __ \/ /Gleb Paharenko
/ /|_/ / // /\ \/ /_/ / /__ [EMAIL PROTECTED]
/_/ /_/\_, /___/\___\_\___/ MySQL AB / Ensita.NET
___/ www.mysql.com
--
MySQL General Mailing List
For list archives: http://lists.mysql.com/mysql
To unsubscribe:http://lists.mysql.com/[EMAIL PROTECTED]
RE: from MySQL to MS Excel ...
Here's the skinny -- YES and NO. NO in that it won't export directly, YES in that you have to do a little leg work in order for it to be done. You have 3 options -- ODBC, Code and CSV. ODBC -- Excel has the ability to use ODBC connections to the MySQL database. Run your MySQL query with the HTML flags turned on and then export to a file so that Excel can read it. (Thanks to SGreen for this info from an earlier post). CODE -- If you code it in ASP or PHP, you can get your code to push directly into Excel with field headers and data, and have formatting options because Excel can interpret HTML code. CSV -- Do your MySQL query from the CLI and then use MySQL to export your results to a CSV file. Then open the CSV file in Excel (using the Excel File Open). See ODBC connection above for another option using the HTML flag. HTH, J.R. -Original Message- From: C.R.Vegelin [mailto:[EMAIL PROTECTED] Sent: Saturday, December 10, 2005 9:35 AM To: mysql@lists.mysql.com Subject: from MySQL to MS Excel ... Hi Friends, I am looking for an easy and seamless way to export MySQL query output to MS Excel. At this moment I am using MS Access 2003 as front-end for a MySQL database. With MS Access I can easily send the output of queries on my database to MS Excel. All I need to do is select Tools Office Links Analyze it with Microsoft Office Excel. That's all. This applies to all kinds of MySQL queries, including WITH ROLLUP options. In the manual I found: http://dev.mysql.com/doc/refman/5.0/en/doctoexcel.html But this is too much trouble, and does not allow full functionality of MySQL queries. Question: is it possible to create MS Excel files directly from MySQL ? TIA, Cor smime.p7s Description: S/MIME cryptographic signature
Re: Normalization question
Thanks for you responses! This list has proven to be for useful to pick pick the brains of other DBA's. I think we are probably going to go the route of splitting the different pieces of data into seperate columns, while keeping the original product_id, since we have a lot of third party applications that reference that column for data identification purposes, although not to specifically find the information that is overloaded within the field. Thanks!
RE: from MySQL to MS Excel ...
There is at least one other option that JR didn't mention... at least some versions of Excel have the menu option Data-Get External Data which allows you to link through ODBC to run queries directly from within Excel. I have barely used it and I have never tried it with MySQL so I can't really explain how to use it or what it's limitations will be but I know that it works through at least two other ODBC drivers. Shawn Green Database Administrator Unimin Corporation - Spruce Pine J.R. Bullington [EMAIL PROTECTED] wrote on 12/10/2005 10:33:18 AM: Here's the skinny -- YES and NO. NO in that it won't export directly, YES in that you have to do a little leg work in order for it to be done. You have 3 options -- ODBC, Code and CSV. ODBC -- Excel has the ability to use ODBC connections to the MySQL database. Run your MySQL query with the HTML flags turned on and then export to a file so that Excel can read it. (Thanks to SGreen for this info from an earlier post). CODE -- If you code it in ASP or PHP, you can get your code to push directly into Excel with field headers and data, and have formatting options because Excel can interpret HTML code. CSV -- Do your MySQL query from the CLI and then use MySQL to export your results to a CSV file. Then open the CSV file in Excel (using the Excel File Open). See ODBC connection above for another option using the HTML flag. HTH, J.R. -Original Message- From: C.R.Vegelin [mailto:[EMAIL PROTECTED] Sent: Saturday, December 10, 2005 9:35 AM To: mysql@lists.mysql.com Subject: from MySQL to MS Excel ... Hi Friends, I am looking for an easy and seamless way to export MySQL query output to MS Excel. At this moment I am using MS Access 2003 as front-end for a MySQL database. With MS Access I can easily send the output of queries on my database to MS Excel. All I need to do is select Tools Office Links Analyze it with Microsoft Office Excel. That's all. This applies to all kinds of MySQL queries, including WITH ROLLUP options. In the manual I found: http://dev.mysql.com/doc/refman/5.0/en/doctoexcel.html But this is too much trouble, and does not allow full functionality of MySQL queries. Question: is it possible to create MS Excel files directly from MySQL ? TIA, Cor
Re: which release of Mysql is compatible with fedora core3 ?
ali asghar torabi parizy wrote: i have fedora core3 installed on my system. which release of Mysql is compatible with fedora core3 ? You should have no issue installing MySQL 5 from the download site, while using Fedora Core 3 - http://dev.mysql.com/downloads/. If however, you want to use the Fedora Project provided version, that caps of 3.23 (the RPM's available via yum) Hope this helps -- Colin Charles, Community Engineer MySQL AB, Kuala Lumpur, Malaysia, www.mysql.com Office: [EMAIL PROTECTED] / +46 18 174 400 ext. 4528 Are you MySQL certified? www.mysql.com/certification -- MySQL General Mailing List For list archives: http://lists.mysql.com/mysql To unsubscribe:http://lists.mysql.com/[EMAIL PROTECTED]
mysqldump: INSERTS for each individual record.
When performing mysqldump is there any way to ensure that each record gets an INSERT of it's own? I keep getting the following: INSERT INTO 'mytable' (1,'test item'), (2,'test item'), (3,'test item'), (4,'test item'), (5,'test item'); but I'd rather have INSERT INTO 'mytable' (1,'test item'); INSERT INTO 'mytable' (2,'test item'); INSERT INTO 'mytable' (3,'test item'); INSERT INTO 'mytable' (4,'test item'); INSERT INTO 'mytable' (5,'test item'); because I'm doing my own line diff between files and it's much easier for me to have the items on individual lines. Any assistance would be appreciated. Regards, Michael -- MySQL General Mailing List For list archives: http://lists.mysql.com/mysql To unsubscribe:http://lists.mysql.com/[EMAIL PROTECTED]
Re: mysqldump: INSERTS for each individual record.
hello there.. mysqldump has a option called --opt that dump your data in that way. This is the default option for new versions of mysqldump. --opt is the equivalent of typing --add-drop-table, add-locks, --create-options, --quick, --extended-insert, --lock-tables, --set-charset and --disable-keys. The --extended-insert option is responsible for the behavior you´re getting in inserts statement. To avoid the --opt option use --skip-opt option and inform other options separately... good luck!!! Richard AB. - Original Message - From: Michael Williams [EMAIL PROTECTED] To: mysql@lists.mysql.com Sent: Saturday, December 10, 2005 9:50 PM Subject: mysqldump: INSERTS for each individual record. When performing mysqldump is there any way to ensure that each record gets an INSERT of it's own? I keep getting the following: INSERT INTO 'mytable' (1,'test item'), (2,'test item'), (3,'test item'), (4,'test item'), (5,'test item'); but I'd rather have INSERT INTO 'mytable' (1,'test item'); INSERT INTO 'mytable' (2,'test item'); INSERT INTO 'mytable' (3,'test item'); INSERT INTO 'mytable' (4,'test item'); INSERT INTO 'mytable' (5,'test item'); because I'm doing my own line diff between files and it's much easier for me to have the items on individual lines. Any assistance would be appreciated. Regards, Michael -- MySQL General Mailing List For list archives: http://lists.mysql.com/mysql To unsubscribe: http://lists.mysql.com/[EMAIL PROTECTED] -- No virus found in this incoming message. Checked by AVG Free Edition. Version: 7.1.371 / Virus Database: 267.13.12/194 - Release Date: 07/12/2005 -- No virus found in this outgoing message. Checked by AVG Free Edition. Version: 7.1.371 / Virus Database: 267.13.12/194 - Release Date: 07/12/2005 -- MySQL General Mailing List For list archives: http://lists.mysql.com/mysql To unsubscribe:http://lists.mysql.com/[EMAIL PROTECTED]
maximum number of tables supported in a mysql database
hi, what is the maximum no of tables supported in a mysql database? -- MySQL General Mailing List For list archives: http://lists.mysql.com/mysql To unsubscribe:http://lists.mysql.com/[EMAIL PROTECTED]
Re: maximum number of tables supported in a mysql database
sunaram patir [EMAIL PROTECTED] wrote on 12/11/2005 12:10:52 AM: hi, what is the maximum no of tables supported in a mysql database? That mostly depends on how large your hard drives are... Except for the InnoDB engine (in default mode) and the NDB engine, all other database engines use 1 or more files per table. How many individual files fit on your hard drive? Here is a page describing the maximum sizes of tables based on which operating system you are using: http://dev.mysql.com/doc/refman/4.1/en/table-size.html This article discusses the drawbacks to creating too many tables in the same database: http://dev.mysql.com/doc/refman/4.1/en/creating-many-tables.html This page starts the section about all database engines except InnoDB and NDB: http://dev.mysql.com/doc/refman/4.1/en/storage-engines.html This describes the InnoDB engine: http://dev.mysql.com/doc/refman/4.1/en/innodb.html This describes NDB Cluster: http://dev.mysql.com/doc/refman/4.1/en/ndbcluster.html Somewhere in those articles it may describe the theoretical limits to how many tables you can define but I can summarize them by saying that the actual limits will depend mostly on what type of operating system you have and how big your disks are. I have never heard of any one needing more tables than they could create. I would assume that a few thousand tables wouldn't be too many for most modern hard drives to handle. How many were you worried about? Shawn Green Database Administrator Unimin Corporation - Spruce Pine
