Mysql 4

Anon

What to expect of MySql 4 beta ? The TODO file is really nice, and incitates me to drop PostgreSql which I kept for only 0,000001% of my requests containing ROLLBACK commands.
What is the difference between MySql4 and MySQL-Max 4 since both of them support InnoDB ???

Is somebody anyway satisfied with MySql 4, is it serious to use it now ? Should I wait ? Should I wait and use for now MySql-Max 3 ?

Thank you for your experiences.

Anon

to quote the website...

"Users are not recommended to switch their production systems to MySQL 4.0 until it is released in beta version later Q4/2001. However, even the initial release has passed our extensive test suite without any errors on any of the platforms we test on. Due to the large number of new features, we thus recommend MySQL 4.0 even in alpha form for development use, with the release schedule of MySQL 4.0 being such that it will reach stable state before the deployment of user applications now under development."

make of that what you will...
i'm sticking to 3 on all my production sites until 4 is out of beta.

[deleted]

"Users are not recommended to switch their production systems to MySQL 4.0 until it is released in beta version later Q4/2001"

uhm... they encourage you to run a beta version for production? sick...

[deleted]

MySQL's TODO file has been very nice for the past years, but they also have a reputation for never ever doing any of it.

MySQL with InnoDB is on the right track, but they are still no match for PostgreSQL when it comes to functionality. MySQL still has no functions, no stored procedures, no functional indexes, no cascading deletes, no subqueries, no insert into self select from self... all the things that make a database usefull.

MySQL 4.0 is better than 3 (InnoDB finally adds row-level-locking, transactions and referencial integrety), but it is still just a toy compared to PostgreSQL and the 'big boys'. And that is sad, because far too many people are learning about databases through MySQL, and MySQL is teaching them the wrong things. (like: SELECT * FROM table GROUP BY column... ouch)

PostgreSQL will teach you correct use of databases and correct SQL.

PS: No offence, but if only 0.000001% of your queries require transactions, then you are either brilliant at SQL, or you don't fully understand what transactions are for :-)

Anon

mysql has user defined functions... but their site search seems to be down at the moment so i can't get the URL.

i like mysql for its simplicity, but i learned my SQL on the streets, so i really do miss the stuff they didn't implement. ESPECIALLY sub-selects. i could use that almost every day.

PostgreSQL is getting a LOT of hype, but i'm not buying into it yet. i trust AB is going to implement the features right, and that is what is taking long.

i'm probably just naive though.

Anon

I know all of what you said... 🙂

About my transactions, I only use them for my backoffice scripts, the only ones doing UPDATE requests... Since 5 people have an access to this backoffice, it is a wise solution to use transactions if they all want to update the same datas... well you know the job.

[deleted]

"mysql has user defined functions... "

Yes, pre-compiled pieces of binary code that you can define as a function.
PostgreSQL let's you write the function in SQL or PL/SQL which means you can change the function on the fly without needing a C++ compiler.
http://www3.us.postgresql.org/users-lounge/docs/7.1/reference/sql-createfunction.html

"i like mysql for its simplicity"

You mean you like it for the speed you get in exchange for all the good functions 🙂

"i'm probably just naive though."

defineately :-)

MySQL is getting hype, everybody uses it, everybody thinks it's great, but nobody who uses mysql ever mentions foreign keys, functional indexes, transactions or any of the other things that make sure your data is consistent and reliable.

A simple thing like cascading delete. MySQL users write pages of code to make sure they delete all the parent-child related records in the proper order to try to keep their data consistent. PostgreSQL users just define a foreign key with cascading delete. If the parent is deleted all it's children are deleted by the database itself. That saves coding to delete all the children, and makes sure can never have any orphans.

FYI: Informix (the worlds most used database) started out as a spinoff of postgreSQL.