Limitations of Mysql

Anon

I wish to switch over from MSSQL to mysql due to the features provided by mysql to integrate with the web using php.

Can any body tell me what the implications of such a change could be?

What is the capacity of mysql in terms of number of databases and number of records etc. ?

Anon

I was once told that it doesn't support transactions (whatever that means). I hope that gives you an idea.

jariizumi

Limitations in numbers... The only time I've read about a limit is the 4GB limit imposed by the ext2 file system (if you use Linux) for a table. I would think that you would hit your server's cpu ceilings before you hit MySQL's row limit. No limit on databases... no more than the filesystem's. Hope this is of some help to you 🙂

Anon

You kinda find some more info here:

http://www.phpbuilder.com/columns/tim20000705.php3

[deleted]

MySQL has a much more limited SQL vocabulary.
Read the MySQL manual about what it can and cannot do.

BTW, MS-SQL can work with PHPjust fine, all it takes is some hard work to get it going.

keegan

My only grievance against MySQL is that it doesn't support sub-selects, so I often end up having to write complex joins where a simple sub-select would have worked well in MS SQL.

-Keegan

Anon

I have to say lack of transactions (don't touch it if you need consistency and reliability), lack of sub selects (damn useful) and lack of foreign key support. The mysql.com documentation section has a list of the key features they are missing from what I gather is 'standard' DB/SQL.

What you might find is that mysql is the lowest common denominator among databases. If you are interested in portability it'll probably be one of the db's that make you use less slick code/queries.

It does a damn fine job at the large class of problems and uses that don't require things like transactions though.