Re: How do I use and JOIN the mysql.time_zone% tables?

2010-10-14 Thread Johan De Meersman
Part of your answer is the offset column, which seems to be relative to the abbreviation used. This implies, to me, that each particular abbreviation has it's own way of specifying the starting point of the time. Added is the DST flag, which (probably) tells you that your app needs to keep

How to kill locked queries

2010-10-14 Thread monloi perez
All, Is there a mysql configuration to kill queries that have been locked for quite some time. If there's none what is an alternative approach to kill these locked queries and what is the root cause of it? Thanks, Mon

Re: How to kill locked queries

2010-10-14 Thread Johan De Meersman
The root cause is another query that has tables locked that your locked queries want. Behind that may be, for example, an inefficient but often-executed query, high I/O concurrency that has a cumulative slowing effect, or maybe simply a long-running update that might be better scheduled during the

Re: How to kill locked queries

2010-10-14 Thread Claudio Nanni
Hi Mon, Killing locked queries is not the first step in database tuning. Queries locked for a long time usually depend on slow updates that lock other updates or selects, this happen on MyISAM (or table level locking engines). If you are really sure you want and can without problems kill the

Re: How to kill locked queries

2010-10-14 Thread monloi perez
Does this happen if your table is InnoDB? Thanks all, Mon From: Claudio Nanni claudio.na...@gmail.com To: monloi perez mlp_fol...@yahoo.com Cc: mysql mailing list mysql@lists.mysql.com Sent: Thu, October 14, 2010 3:16:38 PM Subject: Re: How to kill locked

Re: How to kill locked queries

2010-10-14 Thread Johan De Meersman
On Thu, Oct 14, 2010 at 9:19 AM, monloi perez mlp_fol...@yahoo.com wrote: Does this happen if your table is InnoDB? That depends on the type of lock. If no lock type is specified, InnDB will prefer row locks, while MyISAM will do table locks. That may help, unless all your queries are trying

Backing up MySQL using PHPMyAdmin problem with UTF-8

2010-10-14 Thread Tompkins Neil
Hi, I'm using PHP MyAdmin to backup my MySQL database. The database is of type InnoDB and encoding used is utf8_unicode_ci. The variables are set as follows : *MySQL connection collation: **utf8_unicode_ci* *MySQL charset: **UTF-8 Unicode (utf8)* *character set client: utf8* *character set

Re: How to kill locked queries

2010-10-14 Thread Perrin Harkins
On Thu, Oct 14, 2010 at 3:28 AM, Johan De Meersman vegiv...@tuxera.be wrote: That depends on the type of lock. If no lock type is specified, InnDB will prefer row locks, while MyISAM will do table locks. That may help, unless all your queries are trying to access the same rows anyway :-)

RE: How do I use and JOIN the mysql.time_zone% tables?

2010-10-14 Thread Jerry Schwartz
Interesting question -- I hope someone can give an in-depth explanation. I've created some TZ processing to use in Access, to go back and forth from local time to UTC (which Access doesn't make easy). To do this, I had to find and reformat some official files so I could cram them into Access

Re: Backing up MySQL using PHPMyAdmin problem with UTF-8

2010-10-14 Thread Michael Dykman
I have had this problem with PHPMyAdmin many times, and the only way I know around it, is to go in and do your dump at the console. PHP does not deal with UTF very well. - michael dykman On Thu, Oct 14, 2010 at 5:48 AM, Tompkins Neil neil.tompk...@googlemail.com wrote: Hi, I'm using PHP

How do I GRANT SELECT to mysql.time_zone_name for ANYONE?!

2010-10-14 Thread Daevid Vincent
I'm pulling my hair out. How do I GRANT the SELECT ability to ANY USER for the very specific mysql.time_zone_name table?? I don't want to GRANT it to every individual user manually, I want one single GRANT that encompasses every user simultaneously. I've tried all of these, and they all are valid