Didn't even know that one existed. It has an attraction, esp. in
terms of backing up the data.
But the link refers to the performance benefit in accessing one line
at a time. Supposing I was doing a search for all records where a
particular string is present -- what would the overhead be in the
Ah, if you are single-user and updating really is a special occasion
that is completely in your control, you could even use compressed
MyISAM. That makes the table read-only though, but it does give
performance benefits:
http://dev.mysql.com/doc/refman/4.1/en/myisampack.html
good luck!
Walter Hec
>> 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
Hello MySQL Community,
I'm new around, and I'm a new mysql user. I use mysql mostly together with
Moodle to support many courses on a public university in Brazil (UFBA).
Recently, I was trying to use Reverse Engineering on Workbench to catch a
relationship diagram for moodle, and so I've attempte
In the last episode (Apr 02), Gavin Towey said:
> I disagree. There's nothing about his requirements that sounds like
> MyIsam is a better solution. InnoDB should be your default for all
> tables, unless you have specific requirements that need myisam. One
> specific example of an appropriate ta
I disagree. There's nothing about his requirements that sounds like MyIsam is
a better solution. InnoDB should be your default for all tables, unless you
have specific requirements that need myisam. One specific example of an
appropriate task for myisam is where you need very high insert thro
InnoDB won't give you much in terms of disk crash recovery. That's what
backups are for.
Where InnoDB does excel is if your database server dies while updating
rows. If that happens, your database will come back up with sane data.
For both table types, once the data has been flushed to disk,
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 onc
Krishna:
> Just check it up that any active transaction is still there in innodb
> internal data dictionary.
Acutally I figured it out.
There was a constraint on that column as well.
Once I dropped the constraint, I was able to drop the index.
Thanks for the help,
Neil
--
Neil Aggarwal,
Hi Neil,
Just check it up that any active transaction is still there in innodb
internal data dictionary.
Execute show engine innodb status\G
Check for active transaction related to the current table. If it's there
kill that transaction id and try again.
_Krishna
On Fri, Apr 2, 2010 at 10:35
Hello:
When I try to drop an index from an InnoDB table:
drop index company_n56 on company;
I get this error:
ERROR 1025 (HY000): Error on rename of './thymeleweb/#sql-788_1218' to
'./thymeleweb/company' (errno: 150)
Look at the index using: show keys from company\G
gives me this info for that
Hi guys,
Is the information is true.
No, it was blocked by the EU.
http://tokutek.com/2010/04/tokuteks-acquisitions-blocked-by-eu/
http://planet.mysql.com/
http://tokutek.com/2010/04/tokutek-acquires-oracle/
With regards,
Martijn Tonies
Upscene Productions
http://www.upscene.com
Down
12 matches
Mail list logo