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

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 daylig

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

I'm trying to figure out how to join the mysql.time_zone% tables and make sense of this. YES, I know how to "use" them with SET time_zone = timezone; and all that. http://dev.mysql.com/doc/refman/5.0/en/time-zone-support.html That is NOT what I need them for (yet). I have a list of airports and

Are Ubuntu 64-bit /var/lib/mysql/ibdata (etc) compatible with 32-bit ??

We have a PSE05 "Master" and PSE06 "Slave" (PRODUCTION servers) both are Ubuntu 32-bit. We have a third slave PSE07 which is Ubuntu 64-bit. This is our 'live backup' so to speak. We take mysqld down daily on there and tarball the /var/lib/mysql and /var/log/mysql as snapshots (since mysqldump woul

Table locking generally

I have a problem that I can't understand readily. I have a database that has a couple of tables that lock for a recognizable period of time. The reason I know is because during the lock the application stops responding totally. The storage engine is MyIsam. I have reread everything about loc

Re: Primary key not unique on InnoDB table

Hi Travis, Thanks for your response. The fields which have indexes on, can be used on every other search, which is why I thought about creating them. Would you recommend against this ? Cheers Neil On Wed, Oct 13, 2010 at 6:48 PM, Travis Ard wrote: > I couldn't help but notice you have indivi

RE: Primary key not unique on InnoDB table

I couldn't help but notice you have individual indexes on nearly all the fields of your table. If you won't be using these fields exclusively as a join or filter condition in a query, you are unlikely to benefit from the extra indexes and, in fact, they could slow down your inserts and add to your

Re: Primary key not unique on InnoDB table

Shawn it is fine. I thought my primary key was just 1 field. On Wed, Oct 13, 2010 at 4:44 PM, Shawn Green (MySQL) < shawn.l.gr...@oracle.com> wrote: > On 10/13/2010 11:37 AM, Tompkins Neil wrote: > >> Shawn, sorry my error, I didn't realise I had two fields as the primary >> key >> >> > That's

Re: Primary key not unique on InnoDB table

On 10/13/2010 11:37 AM, Tompkins Neil wrote: Shawn, sorry my error, I didn't realise I had two fields as the primary key That's misinformation. You can have multiple fields as a primary key. Show us what you think is duplicate data and I may be able to help you fix your definition -- Shaw

Re: Primary key not unique on InnoDB table

On 10/13/2010 10:37 AM, Tompkins Neil wrote: I've the following table. But why isn't the primary key unique, e.g. preventing duplicates if entered ? CREATE TABLE `players_master` ( `players_id` bigint(20) NOT NULL AUTO_INCREMENT, `default_teams_id` bigint(20) NOT NULL, `first_name` va

Re: Primary key not unique on InnoDB table

Of course, sorry totally stupid should I recognised that. Thanks Neil On Wed, Oct 13, 2010 at 3:46 PM, Krishna Chandra Prajapati < prajapat...@gmail.com> wrote: > Hi Neil, > > Yes, primary key is always unique. > > In your case, you are using composite key (players_id,default_teams_id). > > _Kri

Re: Primary key not unique on InnoDB table

I see what you mean. Infact this is wrong and I will be dropping the second field in the primary key. 2010/10/13 João Cândido de Souza Neto > A primary key with an auto_increment is ok, but I cant think about a > primary > key with two fiels where one of them is autoincrement. Am I completely

Re: Primary key not unique on InnoDB table

A primary key with an auto_increment is ok, but I cant think about a primary key with two fiels where one of them is autoincrement. Am I completely wrong? -- João Cândido de Souza Neto "Tompkins Neil" escreveu na mensagem news:aanlkti=xnjcaiq7bmoxg-q+4nowdhv8uaj9dcqrol...@mail.gmail.com...

Re: Primary key not unique on InnoDB table

Sorry Joao, I thought that was pretty standard to have a primary key with auto_increment ?? 2010/10/13 João Cândido de Souza Neto > Sorry, the word is counpound instead of composed. > > -- > João Cândido de Souza Neto > > ""João Cândido de Souza Neto"" escreveu na > mensagem news:2010101

Re: Primary key not unique on InnoDB table

Hi Neil, Yes, primary key is always unique. In your case, you are using composite key (players_id,default_teams_id). _Krishna On Wed, Oct 13, 2010 at 8:07 PM, Tompkins Neil wrote: > I've the following table. But why isn't the primary key unique, e.g. > preventing duplicates if entered ? > >

Re: Primary key not unique on InnoDB table

Sorry, the word is counpound instead of composed. -- João Cândido de Souza Neto ""João Cândido de Souza Neto"" escreveu na mensagem news:20101013144314.9787.qm...@lists.mysql.com... > I´d never seen before a composed primary key that has an auto_increment > field on it. > > May be I can

Re: Primary key not unique on InnoDB table

I´d never seen before a composed primary key that has an auto_increment field on it. May be I can be wrong but I think it wont work properly. As far as I know, if you have an auto_increment field it must be your single primary key. Am I wrong? -- João Cândido de Souza Neto "Tompkins Neil"

Primary key not unique on InnoDB table

I've the following table. But why isn't the primary key unique, e.g. preventing duplicates if entered ? CREATE TABLE `players_master` ( `players_id` bigint(20) NOT NULL AUTO_INCREMENT, `default_teams_id` bigint(20) NOT NULL, `first_name` varchar(100) COLLATE utf8_unicode_ci NOT NULL, `se

Re: Incremental Backup Script

On 10/13/2010 9:18 AM, kranthi wrote: Hi Please be send sample incremental backup script (bash Shell script Easy to understand) Thanks& Regards, Kranthikiran I think you missed the points of the previous replies. MySQL does not do incremental backups the the same way that othe

Re:Incremental Backup Script

Hi Please be send sample incremental backup script (bash Shell script Easy to understand) Thanks & Regards, Kranthikiran

Re: Backing up the InnoDB tables

> The problem is I don't have any command line access, just direct MySQL > access to the database tables. > > whats wrong with mysqldump? -- bEsT rEgArDs| "Confidence is what you have before you tomasz dereszynski | understand the problem." -- Woody Allen

Re: Backing up the InnoDB tables

Quoting Tompkins Neil : The problem is I don't have any command line access, just direct MySQL access to the database tables. I dont know xtra backup, but if thats not an option you can just use mysqldump. This can be run from a remote server to your DB server, just using MySQL network ac

Re: Backing up the InnoDB tables

The problem is I don't have any command line access, just direct MySQL access to the database tables. On Wed, Oct 13, 2010 at 1:19 PM, Suresh Kuna wrote: > use xtra backup > > On Wed, Oct 13, 2010 at 5:37 PM, Tompkins Neil < > neil.tompk...@googlemail.com> wrote: > >> Would really appreciate som

Re: Backing up the InnoDB tables

use xtra backup On Wed, Oct 13, 2010 at 5:37 PM, Tompkins Neil wrote: > Would really appreciate some help or suggestions on this please, if anyone > can assist ? > > Regards > Neil > > -- Forwarded message -- > From: Tompkins Neil > Date: Tue, Oct 12, 2010 at 5:45 PM > Subject:

Fwd: Backing up the InnoDB tables

Would really appreciate some help or suggestions on this please, if anyone can assist ? Regards Neil -- Forwarded message -- From: Tompkins Neil Date: Tue, Oct 12, 2010 at 5:45 PM Subject: Backing up the InnoDB tables To: "[MySQL]" Hi On a shared MySQL server with access just

Re: Can this query be done w/o adding another column?

After bashing at this for a while with no luck I replaced the "inner" with "left" and I got the desired result. Thanks for the help. On Tue, Oct 12, 2010 at 5:18 PM, Travis Ard wrote: > Sorry, try changing the column mappings.ip to use the table aliases (m.ip > and m2.ip). > > > > -Travis > > >