Though I have had little experience with using mySQL, I can tell you this...it will be a cold day in hell when I will work with another DMBS that does NOT support or provide stored procedures.
Try managing a "real" application without them. You end up with hacks in all shapes and flavors to make up for what the db lacks.
I guess if you never used them, then you don't know what you are missing.
I do however agree with most everyone that mySQL fits a certain roll, but what would that be? My 2 cents
Eck...i can think of so many instances where having text inline (within the row) will just not do. Myself, coming for MS SQL world, this really is a big change to what I am used to...how does this impact performance from an indexing standpoint? I have visions of 200 concurrent users updating text (blobs) all over the place, causing a crap load of page splits. Suppose what ever the impact is, some of it could be offloaded by vertically partitioning the table, but as a dev, that is something I don't want to think about when i am in design/protype mode. Thoughts?
So what exactly is the purpose of this complete waste of time that is called entertainment? About as interesting as watching the mullets driving around making left hand turns for 500 miles.
Sounds like the theme to the movie "The Insider". Guess software could be considered as dangerous as smoking...considering it was written by MS$ it might very well be.
Employeers are not allowed to record person phone calls made from company phones and/or on company time....this does NOT however cover for the fact that your are using company time for personal business.
Slashdot Mirror
Is anyone reviewing this crap, or am I not the only one with a hangover still from the weekend?
Try managing a "real" application without them. You end up with hacks in all shapes and flavors to make up for what the db lacks.
I guess if you never used them, then you don't know what you are missing.
I do however agree with most everyone that mySQL fits a certain roll, but what would that be? My 2 cents
Eck...i can think of so many instances where having text inline (within the row) will just not do. Myself, coming for MS SQL world, this really is a big change to what I am used to...how does this impact performance from an indexing standpoint? I have visions of 200 concurrent users updating text (blobs) all over the place, causing a crap load of page splits. Suppose what ever the impact is, some of it could be offloaded by vertically partitioning the table, but as a dev, that is something I don't want to think about when i am in design/protype mode. Thoughts?
Sounds like the theme to the movie "The Insider". Guess software could be considered as dangerous as smoking...considering it was written by MS$ it might very well be.
Employeers are not allowed to record person phone calls made from company phones and/or on company time....this does NOT however cover for the fact that your are using company time for personal business.
You and me both...feels more and more like Office Space everyday