Re: combined or single indexes?

2010-07-06 Thread Octavian Rasnita
Hi, MySQL can use a single index in a query as you've seen in the result of explain. Of course it is better to have an index made of 2 or more columns because it will match better the query. But if I remember well, the in() function can't use an index. And I think it also can't use an index

Re: Fixed Connection Diagnostic Tool

2010-07-06 Thread Michael Dykman
C3P0 connection does, indeed work well on remote machines.. In fact, I only deploy it locally on dev servers. My production systems all use c3p0 on remote servers. Again, if you can connect from the command line of your client machine to the server *via TCP* with the same credentials as your Dat

Re: Fixed Connection Diagnostic Tool

2010-07-06 Thread michel
Thank you all for the help and info! This error happened because I started MySQL with -bind-address=91.203.57.207; even if Softslate is given the proper IP address and port number is fails on connection pooling. I fixed the problem by setting the MySQL IP address to 127.0.0.1. I am thinking th

Re: combined or single indexes?

2010-07-06 Thread Joerg Bruehe
Hi Bryan, all! Bryan Cantwell wrote: > Is there a benefit to a combined index on a table? Or is multiple single > column indexes better? This is a FAQ, but I'm not aware of a place to point you for the answer. > > If I have table 'foo' with columns a, b, and c. I will have a query > like: > se

Re: How to slim MySQL?

2010-07-06 Thread Andrés Tello
The more information, the easiest to pinpoint solutions. delete all client and administrativ tools (mysql, mysqladmin, etc from the "server", since you aren't doing any transactions, I think you can ditch all engines excepto the isam/myisam, the basic one, also you migth want to leave memory engin

Re: How to slim MySQL?

2010-07-06 Thread Nima Mohammadi
On Tue, Jul 6, 2010 at 7:10 PM, mos wrote: > Roam, > Why are you installing a client server database on an embedded > system? There are better databases for this task. In the past I've been able > to squeeze a Windows application and an SQL database so it could run > directly off of a flopp

Re: How to slim MySQL?

2010-07-06 Thread Nima Mohammadi
On Tue, Jul 6, 2010 at 2:00 PM, Joerg Bruehe wrote: > Hi! > > > Nima Mohammadi wrote: > > On Mon, Jul 5, 2010 at 8:26 PM, Rob Wultsch wrote: > > > >> [[...]] > >> > >> You probably want to compile your own version of MySQL. You probably > >> want to remove debugging symbols* (which have been pre

combined or single indexes?

2010-07-06 Thread Bryan Cantwell
Is there a benefit to a combined index on a table? Or is multiple single column indexes better? If I have table 'foo' with columns a, b, and c. I will have a query like: select c from foo where a in (1,2,3) and b < 12345; Is index on a,b better in any way than an a index and a b index? An explain

Re: Got error 139 from storage engine (InnoDB)

2010-07-06 Thread James Corteciano
Hi Joerg, Thanks for your reply. I found out that this error was limitation row length of 8000 bytes on InnoDB. I have check the dump sql file and one particular table is causing error 139. What I did is just to use MyISAM engine rather than InnoDB for a specific table only. BTW, the machine ha

Re: How to slim MySQL?

2010-07-06 Thread mos
Roam, Why are you installing a client server database on an embedded system? There are better databases for this task. In the past I've been able to squeeze a Windows application and an SQL database so it could run directly off of a floppy disk (remember those?). But it wasn't client se

Re: How to slim MySQL?

2010-07-06 Thread Joerg Bruehe
Hi! Nima Mohammadi wrote: > On Mon, Jul 5, 2010 at 8:26 PM, Rob Wultsch wrote: > >> [[...]] >> >> You probably want to compile your own version of MySQL. You probably >> want to remove debugging symbols* (which have been present since the >> mid 5.0 series, iirc), and any engines/character sets

Re: Got error 139 from storage engine (InnoDB)

2010-07-06 Thread Joerg Bruehe
James, all, James Corteciano wrote: > Hi All, > > I have received error message "ERROR 1030 (HY000) at line 167: Got error 139 > from storage engine" when importing dump database to MySQL server. The MySQL > server is using InnoDB. I have google it and it's something problem on > exceeding > a r