Comments on Monty says: A bugs life

About problems with 5.0:To be able to help you, we...

2008-07-29T10:18:00.000+03:00

About problems with 5.0:

To be able to help you, we would need some information where 5.0 hangs or a way to repeat it. The current 5.0 has been proven to be quite stable now, but there may of course be something unique in your setup that we don't know about.

You could try to setup a 5.1 server and see if this would help you; If you are only using 5.0 features, then 5.1 may be a better alternative for you.

We've got sth around 60 mysql 5.0.x database serve...

2008-07-23T02:33:00.000+03:00

We've got sth around 60 mysql 5.0.x database servers running all the time on production and every month there is some problem with mysql bug. Recently it got locked forever (for 20 hours) even though there were no queries shown by mysqladmin processlist (it couldn't even do a simple select * from X limit 1 (X being innodb table); and it wasn't the case of lacking unlock tables on connection).

For me any mysql 5.0.x is still a great example of unreliable database.

It's intentionally that auto-increment can't count...

2008-07-29T10:12:00.000+03:00

It's intentionally that auto-increment can't count down: This is how autoincrement and sequences work in most databases.

If it would count down, you would easily get serious problems with entries in other tables that refers to deleted rows, with replication and with multiple connections inserting and updating the same database.

If you set the auto-increment key to a long value, there basicly no chance a value will be reused (2^32 is a really big number).

There is a huge Bug in MySQL when you are using id...

2008-07-23T15:19:00.000+03:00

There is a huge Bug in MySQL when you are using id's with auto-increment. When you put in 3 entries in the db and than delete 1 entry. If you now add a new entry it gets the id 4. So the autoincrement can only count up, but not down. So you have to delete the primary key and than recreate it. So the autoinkrement has no holes and reaches the maximum count only if you really have so much entries.

We need a function for that, because that what i am doing is only a workaround but it works fine.

thx for reading my poor english ;)

Found this bug with SAVEPOINT last week: http://bu...

2008-07-20T19:45:00.000+03:00

Found this bug with SAVEPOINT last week: http://bugs.mysql.com/bug.php?id=38187

It affects me pretty badly since I use savepoints in all stored procedures to handle local errors. Each SP updates 2-5 tables, and needs to be able to rollback it's own chances if something goes wrong without affecting the applications "broader" transaction.

Anyone that uses savepoints is potentially affected by this bug.

Hello,Downloading the release. ;)I hope that a new...

2008-07-21T01:41:00.000+03:00

Hello,
Downloading the release. ;)

I hope that a new versions of MySQL Server have a utilities or systems for Bussines Intelligence, It'll be great for this technologies.

The best regards
Gildus

Please add the Spatial Functions from 5.1.23-gis (...

2008-07-18T23:30:00.000+03:00

Please add the Spatial Functions from 5.1.23-gis (forge) to MySQL 5.1-GA

http://forge.mysql.com/wiki/GIS_Functions

Here's a nasty that has existed since information_...

2008-07-18T01:30:00.000+03:00

Here's a nasty that has existed since information_schema was introduced in 5.0: http://bugs.mysql.com/bug.php?id=29153
SHOW and infoschema use LONGTEXT columns, so the temporary table that is internally created cannot be type MEMORY.
Since most people's default is MyISAM, the table goes to disk, making infoschema excruciatingly slow.
A full list of which infoschema tables use this type is included in the bug report.
Infoschema is sooooo useful, but also soooo unusable on servers with more databases/tables/columns as it's just too slow, and this issue is a major factor.

MySQL 5.0 has support for VARCHAR up to nearly 64k, so these columns could be changed to varchars. The exact value is not that important, you can even just put in the maximum and it would still perform better than what it is now!