Drizzle is characterized not as a product of Sun/MySQL, but an independent open source (GPLv2) project of its own.

The question asked:
Would some of the features introduced in MySQL 5.0 such as stored procedures, triggers, and so on work against scala…

Some questions/comments:

1. A DBMS features “…Stored Procedures, Views, Triggers, Query Cache, and Prepared Statements…” and you don’t need them. So, you don’t use them. Is it still a performance hit then? How much? Enough to drive people to genuinely fork/create a niche database?

2. You state that “…stored procedures, triggers, and so on will work against scalability by pushing business logic back to the database…” Now, I would argue that it is not the availability of the features doing that, but rather the lack of discipline in developers that would keep them from doing that. I keep the business logic in its layer, but I still need triggers and such to *guarantee fundamental integrity constraints of data* at the database layer. Of course, in a project where only one app layer hits one database, this can be forgiven. But in an environment where multiple teams with multiple apps hit the database, you need some integrity logic in the database to help prevent one errant developer from mucking it up for everyone, don’t you?

Notice that Drizzle lacks the current Fulltext index support of MySQL. Do not be surprised if you see us do something very radical toward solving this problem.

Also, Drizzle is just the first piece of a much larger project.

Cheers,
-Brian