Re: LEFT JOIN and WHERE: identical or not and what is better?

'where' is a filter. You're limiting records based on a criterion. 'on' is used for joining. On Mon, Apr 25, 2011 at 10:42 AM, Andre Polykanine an...@oire.org wrote: Hello everyone, Sorry for my beginner question. Actually I have been using MySql for a long  time  but  I  just  start  using

better way to backup 50 Gig db?

I'm using MySQL to manage data on my computer . The total data is 50 Gig in MyISAM folders. As I type, I already have the folder with the myd, frm, etc being copied offsite. As I understand it, if this computer dies tomorrow, I can reinstall MySQL on a new computer, drag over the archive, stick

reshaping challenge

I have a table with two columns, ID and order. Each ID can be repeated up to 16 timers. I need to reshape it so that I have one row per ID, and columns order1, order 2,...order 16, and one number that lists how many orders there actually were. No this is not a homework assignment. I'm trying

fast update with 1:1 table?

I have two tables, A and B. B has newer data, A has more columns. I want to update some of the columns in A with all but one of the columns in B. They have the same number of records -- about eight million -- and one key column in common for matching. (That's the one from B I don't want to

getting 64 bit machine -- need to compile workbench?

I've already downloaded the 64 bit build of MySQL to have ready for a 64 bit machine I have coming. But the only available download for Workbench binaries is 32 bit. So I have a few questions: (1) will the 32 bit Workbench work with 64 bit MySQL under Windows XP (64 bit)? (2) if I need to

MyISAM better than innodb for large files?

I'm going to be setting up a MySQL database for a project. My reading indicates that MyISAM (default) is going to be better than InnoDB for the project but I want to be sure I have the trade-offs right. This is going to be a very large data file -- many gigabytes -- only used internally, and

Re: MyISAM better than innodb for large files?

You want the crash safety and data integrity that comes with InnoDB.  Even more so as your dataset grows.  It's performance is far better than myisam tables for most OLTP users, and as your number of concurrent readers and writers grows, the improvement in performance from using innodb over

Re: MyISAM better than innodb for large files?

though, but it does give performance benefits: http://dev.mysql.com/doc/refman/4.1/en/myisampack.html good luck! Walter Heck Engineer @ Open Query (http://openquery.com) On Sat, Apr 3, 2010 at 08:50, Mitchell Maltenfort mmal...@gmail.com wrote: You want the crash safety and data integrity

music.sql with FK from Learning MySQL -- 1005 error?

I've been mucking with the O'Reilly book Learning MySQL for the obvious purpose of learning MySQL. The book offers two versions of a program: http://learningmysql.com/Downloads/Files/Data/SQL_files_with_foreign_key_references/music.sql sticks at creating the track table. However, its sibling

Re: music.sql with FK from Learning MySQL -- 1005 error?

that makes sense except why is that not a problem for flight.sql and university.sql? On 3/22/10, Martin Gainty mgai...@hotmail.com wrote: FOREIGN KEY (album_id) REFERENCES album(album_id)whichever value is being used for to populate album_id is NOT presently as a row in the album table (and

Q on Mysql install on OS X (SNow Leopard)

For some reason, the thing doesn't show the problem I posted already about foreign keys, but what it won't let me do is drop a schema once I've created it. How do I change permissions so MySQL on OS X can delete directories? Thanks! -- MySQL General Mailing List For list archives: