I have this dilemma.

The system is behind schedule. Consultants have been brought in. They have shiny neckties. They are from the dark side. They are certified Micro$oft-bankroll developers.

They want to replace the previous developers' MySQL / PHP solution with an ASP.NET kludge.

What can I do ? How can I save MySQL / PHP, how can I save my conscience?

I need answers. Quick.

Q. Why is MySQL better than ASP.NET ?

OK, I know it's faster, easier to learn etc. but I need some technical answers to stop this beast dead in its tracks.

Any ideas, anyone?

Thanks
Bert

eeeeeeeeeeeeeeeeegh. phutt.

That was the sound of an open source solution dying.

The MySQL / PHP db on the Linux box is dead.

Long live .NET / MSSQL / TransactSQL (?!)



Ah well. I'll put it back when they leave .

Bert

well the stable answer is all u need

Just let them see PHPNuke, and I bet they have never seen anything comparing to that in windows world http://phpnuke.org/

I would focus on the fact that it is far more secure and the costs are much lower. It can also be modified to do exactly what you want it to do.

--jeremy

$ involved long term with ms solution is what i'd also bring to light.

Actually, a more technical reason was given for going for an MS solution. MySQL does not enforce referential integrity.
OK, referential integrity is basically enforcing foreign keys so that the tables are strung together and duplication or redundant data won't exist (that's the theory aneeway).

Do later versions of MySQL enforce referential integrity?

Thanks for the responses.

BTW the money thing is a factor. Systems and the consultants are bickering on this point, as when the consultants leave, we could be left with crippling license costs.

There's a meeting on Monday to resolve this.

Hmmm.

Bert

Hi there!

Well, I don't know MySQL, but I did a quick google, and it seems to me that MySQL does not support referential integrity. But it looks like PostgreSQL support it. I don't use PostgreSQL either, so I won't know if its good.

Hope this helps..
RefriedBean

PS. I don't use SQL at all, so if anything I said is wrong, please ignore this post

MySQL supports foreign keys, since near 3.23.43 - more than half of the year

The trouble is, this app was coded using the current version of MySQL 6 months ago. Frankly, not supporting referential integrity isn't great - it's central to database modelling and everything else (SQL92 even) supports it .

The developer should have used PostgreSQL. The moral of the story is pick your app well. MySQL is a speed tool (I think google runs it for this reason) but complex modelling it won't do.

I'm setting up a Redhat 7.3 NFS server using a processor array (we can't use Ghost anymore as it's an er... aquired copy) so the peguin won't be poleaxed yet.

Grrrr

MySQL isn't ACID compliant and I don't think they plan on it in the near future. If that is one of your needs you should look into PostgreSQL.

http://www.us.postgresql.org/features.html

--jeremy

I should add the following two points.

It is possible to get referential integrity now if you use certain transactional table types. These table types are new however and do have some issuses:
InnoDB - http://www.mysql.com/doc/I/n/InnoDB_overview.html
Gemini - http://www.nusphere.com

You can get an atomic operation with the current MyISAM table type:
http://www.mysql.com/doc/A/N/ANSI_di...nsactions.html

--jeremy