innodb_data_file_path tuning

x27;ve had trouble finding resources on tuning innodb - i'd appreciate links as much as answers :) thank you! --- russell uman firebus d-_-b -- MySQL General Mailing List For list archives: http://lists.mysql.com/mysql To unsubscribe:http://lists.mysql.com/[EMAIL PROTECTED]

Re: correct way to simulate 'except' query in mysql 4.1

huh. it's a varchar(50) on table1 and a varchar(50) on table2. i wonder why explain is reporting 150 as key_len? utf8? yes. that does make sense. is there anything else i can investgate? Do you need utf8? :-) yes. it's an internationalized application :) Check your cache hits. I can'

Re: correct way to simulate 'except' query in mysql 4.1

Baron Schwartz wrote: I don't think it will be any better to count distinct values. I think the query is just slow because the index lookups are slow. Is the 'word' column really 150 bytes? huh. it's a varchar(50) on table1 and a varchar(50) on table2. i wonder why explain is reporting 150

Re: correct way to simulate 'except' query in mysql 4.1

making these InnoDB tables? Thanks for your help with this! Baron Schwartz wrote: Hi, That is the right way, but if you show us the exact output of EXPLAIN we can help more. In particular, does it say "Using distinct/not exists" in Extra? Russell Uman wrote: howdy. i try

correct way to simulate 'except' query in mysql 4.1

howdy. i trying to find items in one table that don't exist in another. i'm using a left join with a where clause to do it: SELECT t1.field, t2.field FROM table1 t1 LEFT JOIN table2 t2 ON t1.word = t2.word WHERE t2.word IS NULL; both tables are quite large and the query is quite slow. the f

RESET MASTER during daily backups

howdy. we use the binary log as a crash recovery tool. therefore, once we have backed up the db (we use the excellent mysql_backup for this) we can happily discard yesterday's binlog. the only correct way i've found to get rid of old binlogs in to issue RESET MASTER, and i figure i should do t

undo

howdy. i have a mysql backed php application. has anyone ever come up with a (however kludgy) undo functionality for mysql in a php app? based on keeping a history somewhere? based on the update log? i'm thinking of just making some innodb tables, using transactions, and forcing my users to c

update/join question

i feel like i must be missing something simple because i keep wanting to do things like this, but i can't find a one step way to do it. whether or not there is an easy way, can someone tell me the best way to do it? i want to update a field in one table based on data in another table. example:

novice join question

i have three tables. products, class, and dept. class and dept each have two fields - code and text. products has a field named class (containing class codes) and a field named dept (containing dept codes) for some depts, all the products that have that dept have the same class for other depts,