So basically they want to omit all the things that never used to be in MySQL (because, you know, if you really needed them, they could always be dealt with at the application level) ?

Sounds like a nice straightforward array persistence layer.

And if it's successful, I don't doubt that in a few years' time, they will be talking of adding foreign keys. And maybe stored procedures. Then triggers .....

mySQL has only now got embedded procedures etc since they are faster to process than sending a SQL comand which then has to be parsed,checked for correctness (integrity etc) and then run.

Seems they are going back to mySQL's old claim that it is faster to run it on the fly but if it was then why have they changed to a stored procedure system?

nerds, who needs them ?

What is it with these people?

Drizzle - in my mind sums up a miserable,forgetable, damp day.

What next?

New super all singing, all dancing Open Source Software called...Fanfare!

Turd!

are bad for performance now? well i guess i just learned my new thing for the day.

PreparedStatements are so important when dealing with web applications. There's a huge potential for crap (illegal characters, SQL injection, etc) to get through to the database, and a PreparedStatement gives a lot of protection (by no means complete protection) against this kind of stuff.

Not sure why they're bothering. Free websites will use whatever the ISP gives them. People who own their websites, or small-medium companies, will use MySQL as a minimum. Large companies will have spare Oracle licenses down the back of the sofa.

So.. why?

What the hell is the "SQL relational model"?

We have the relational model, which is fundamental. Oh, and it's a model.

We have SQL, which is the language aspect of a dubious partial implementation of the relational model. It's not a model.

Conflating the two is unhelpful, especially in this context.

<grrrr>

PhilK

Given that prepared statements are touted as one of the best defences against SQL injection expect to see a lot of insecure webapps appearing on the horizon.

Seriously, who thought that dropping prepared statements, instead of making them mandatory, was a good idea? Considering they can also be more efficient and faster for repetitive tasks than ordinary queries this has to be a mis-quote.

Performance is soooooooo overrated. I mean, if you can't afford hardware upgrade, your business model is probably worth reconsidering. And, if you make your developers wasting time using inferior technology, you should probably step down.

"Specifically, Drizzle does not have stored procedures, views, triggers, query cache and prepared statements."

Oh great ... it seems like the mastermind(s) behind Drizzle seem to be the bad lot from the MySQL team. You know, the ones that said "We don't need no steeeenking transactions!" and proceeded to give DBA wannabe's a broken mindset for years to come.

The "transactions are for losers" mindset from the MySQL team was precisely what made me back off and return to PostgreSQL for serious apps. Of course, there are worse "creations" out there, like MUMPS...

Look no further than SQLITE.

Full ANSI 92 SQL support, blinding fast, runs on any hardware/OS combination you are likely to blag or buy.

A truly excellent pice of software!

of course, web site index pages never have the equivalent of this

select * from news order by post_date desc

so there would be no point caching it... and really, the qc is probably the simplist bit of code in mysql, the query string has to be an exact match, its not doing anything clever.

What this story is on about but the bloke in the photo looks like Francis Dollarhyde, the psycho killer in Michael Manns' movie Manhunter.

Yeah he kinda does. although that guy was bigger. Awsome movei too bad the sequels sucked

I thought he looked like the bad guy out of last action hero, the on screen one with the axe and yellow rain coat.

Anyway stoopid name for software but I like that they are drawing a line against M$

"...went on to compare it to Sony as a "non-innovator"." Oh, WOW !! He seems to *NOT* have heard of the Walkman, Discman and a whole host of Sony "non-inventions" !!

Reading between the lines, what this guy is saying is "I'm not a good enough techie to challenge the techies of the big companies, so I'll win by declaring their good features as useless" !! Meanwhile, I'm taking *MY* ball home so you can play by yourselves !! He's not the first I know of with this attitude !!

I shall pay absolutely strict attention to any spectacular success of this new product !! Til then, please don't wake me for anything less !!

My favorite was "Given that prepared statements are touted as one of the best defences against SQL injection expect to see a lot of insecure webapps appearing on the horizon."

Oh I see, you pushed off security to your DBA and now you think you are secure.

Please... step away from the keyboard.

"Not offering Windows support because 'Mircosoft is irelivent to the future of software development" gives them away as FOSS zelots, again someone anyone with a large infrastructure isn't going to trust. Also, almost anyone with a large infrastructure is going to have a shitload of Windows servers."

Not offering Windows support because MS is "irrelevant" is pretty stupid, but not for the reasons you mentioned. Sure people with large infrastructures have a shitload of Windows servers, but I highly doubt that they are paying MS license fees to run an entire cloud of processing like this is designed to run on. Most likely candidates are Fedora or other free Linux. Anyone that would put a large DB installation on cluster or a cloud of Windows servers, IMHO, just doesn't get it. Is Win Server OK for a mid to large server? Yep. But for a cloud of whiteboxes, paying more in Windows licenses than the hardware costs is indefensible...

Damn straight they are,

I've been using remote farms and Grids for years now. Never ever seen them run on anything but Linux / UNIX.

Had a look at SUNs latest cloud - compile your code to run on Solaris 10 and then submit it to their batch farm. Pay-per-CPU-hour. Way of the future.

SQL injection attacks are actually trivial to defeat. All you need to do is perform -- in the application layer -- a regular expression substitution on any incoming form data to ensure that nothing in there can be mistaken for a closing speech mark.

PHP actually used to do that by default ..... until some people started changing their local defaults not to be the same as the default defaults, and what should have been secure by default ended up insecure by default.

I guess dat's default of de one dat changed de settings .....

What a pile of cock!

PHP's "magic quotes" do not prevent SQL injection but they do fill the database full of \shit (please check some manuals on quoting strategies in different (R)DBMS - MySQL MyASM doesn't qualify for the R). But please stick with it if you like it and don't drag your ignorance into our systems.

For anyone else still reading: prepared statements don't entirely remove the threat of SQL injection, as the DB still has to quote the parameters properly and this is open to attack (at least this means that only the DB has to worry and not the client), but it does allow th DB to cache the compiled statement which can bring significant performance improvements particularly on long statements.

Tut, tut. Blaming the programming language for your own inability to read the manual pages for stripslashes() and addslashes().

With that attitude, you are obviously management material. Get yourself some subordinates at once -- it feels even better to blame *people* for your own shortcomings.

haha. Unfortunately I didn't put the shit it their and I'm my client isn't PHP.

I suppose this guy thinks BluRay invented itself, then?

Paris, because she gets Akers of news coverage for not very much as well