Catch up on stories from the past week (and beyond) at the Slashdot story archive


Forgot your password?
Databases Programming Software Data Storage The Internet IT

Slimmed Down MySQL Offshoot Drizzle is Built For the Web 370

Incon writes "Builder AU reports that Brian Aker, MySQL's director of architecture, has unveiled Drizzle, a database project aimed at powering websites with massive concurrency as well as trimming superfluous functionality from MySQL. Drizzle will have a micro-kernel architecture with code being removed from the Drizzle core and moved through interfaces into modules. Aker has already selected particular functionality for removal: modes, views, triggers, prepared statements, stored procedures, query cache, data conversion inserts, access control lists and some data types."
This discussion has been archived. No new comments can be posted.

Slimmed Down MySQL Offshoot Drizzle is Built For the Web

Comments Filter:
  • Oh man. (Score:4, Interesting)

    by Hero Zzyzzx ( 525153 ) <> on Wednesday July 23, 2008 @09:09AM (#24302857) Homepage

    One man's "superfluous" is another man's key feature. No views? No prepared statements? Holy carp. Isn't MySQL crippled enough as it is?

    At first glance it's hard for me to see where Drizzle would fit where SQLite doesn't.

  • SQLite? (Score:4, Interesting)

    by Anonymous Coward on Wednesday July 23, 2008 @09:15AM (#24302961)

    I always thought SQLite did a perfect job of filling in the space between the need for a full blown database and the weight it adds to the server setup. SQLite, as its name suggests, is very lightweight. Where exactly will Drizzle fit in?

  • by MBGMorden ( 803437 ) on Wednesday July 23, 2008 @09:24AM (#24303113)

    Why would anyone in their right mind set up a Web/SQL platform using MS products?

    You'd be surprised. Our web team recently got on an "I love MS!" kick for some reason. They'd been on Linux for years but a lot of the new/shinny buzzword stuff that they wished to install wanted Active Directory, IIS, and other non-sense. Because the Linux setup didn't lend itself well to installing all that proprietary stuff, and because they convinced themselves (somehow) that the most popular software is always the most insecure anyways (so Apache being the most popular webserver is the most insecure), they switched to Windows + IIS (+MySQL, but SQL Server is being pushed hard) to host the website.

    Now I've even had pressure to convert my servers from Linux to Windows where possible to "standardize".

    On a more on-topic note though, I'm not sure where this leaves MySQL itself. As a "real" database, it naturally can't compare to SQL Server or Oracle, but even competing in the free segment, PostgreSQL blows it away. Traditionally MySQL was just the toy database for non-critical stuff that you wanted speed out of (and little else). If Drizzle accomplishes that, then I don't see a real place for the mainline MySQL anymore. Drizzle if you want speed, PostgreSQL if you want features/stability, and Oracle if you gots money to spend.

  • Re:No views?! (Score:4, Interesting)

    by ghoti ( 60903 ) on Wednesday July 23, 2008 @09:42AM (#24303365) Homepage

    Which is exactly what the majority of CMSs do today. They treat the DB as dumb storage, and make very little use of its capabilities.

  • Re:Oh man. (Score:4, Interesting)

    by ricebowl ( 999467 ) on Wednesday July 23, 2008 @09:44AM (#24303391)

    I realise that this is hugely off topic, but is there any chance anyone can highlight the benefits of prepared/stored statements? I've been trying to read around on the subject but it seems to be hard to pin down the benefits, and then I come across this: [], which offers an insight, but seems moderately biased against it "because he's never bothered with it yet, why bother with it now. And get off my lawn!"

    Thanks for any help with this...

  • by CastrTroy ( 595695 ) on Wednesday July 23, 2008 @09:52AM (#24303515) Homepage
    The thing is, is that not everybody needs a full ACID compliant transactional database. All that stuff tends to slow down the whole database. It would be much nicer for many people to just have a simple non-transactional database. Think about how many web apps are out there that don't use transactions, and have not need for them. Many applications would benefit from increased speed over increased transactional capabilities.

    On another note, what's with the lack of hosting services providing PostgreSQL? I would love to use it, at least for some projects, but the fact that it's not available on many hosts makes it quite a hard decision to make. I don't want to pick up another hosting provider, or switch over all my stuff just to use a different database.
  • by bingo_cannon ( 779085 ) on Wednesday July 23, 2008 @09:55AM (#24303573)
    Umm..errrr! Drizzle will have a micro-kernel architecture with code being removed from the Drizzle core and moved through interfaces into modules. Akers has already selected particular functionality for removal: modes, views, triggers, prepared statements, stored procedures, query cache, data conversion inserts, access control lists and some data types."
  • Re:Oh man. (Score:3, Interesting)

    by pjt33 ( 739471 ) on Wednesday July 23, 2008 @10:00AM (#24303637)
    It's rather hard to do a successful SQL injection attack against a prepared statement. It's not trivial to validate your inputs so as to avoid an SQL injection attack without them. That is IMO the number one reason for using them.
  • All for it (Score:5, Interesting)

    by spinkham ( 56603 ) on Wednesday July 23, 2008 @10:01AM (#24303649)

    From my point of view, this is MySQL finally embracing their target market.
    These features are great and important, but if you're doing small scale web programming through a framework that uses an ORM, or just very simple SQL, why not slim the program down?
    If you want real database features, you probably shouldn't be using MySQL in the first place in my opinion.

  • by drew ( 2081 ) on Wednesday July 23, 2008 @10:30AM (#24304091) Homepage

    That was exactly my thought. Hooray, we just jumped 10 years backwards. Hopefully this time they've fixed the database corruption issues that had me truncating table files once a week.

    Of course this just confirms my belief (and the reason I've never yet used MySQL in an environment where I was given the choice) that even when these guys added these features they either didn't understand them or didn't believe that they were ever important.

  • Re:No views?! (Score:3, Interesting)

    by GooberToo ( 74388 ) on Wednesday July 23, 2008 @10:31AM (#24304105)

    While kind of hackish (it uses dia as its GUI), cool projects like tedia2sql [] make it easy to develop a single schema which works on 8 or 9 major RDMS, for free. It's even possible to generate customized triggers and/or schema sections on a per RDBMS basis.

    I don't think it covers stored procedures. It has been a long time since I've used it, but regardless, considering stored procedures are often ignored, it may or may not be a factor for your next project.

  • by ultranova ( 717540 ) on Wednesday July 23, 2008 @10:37AM (#24304209)

    If you don't use prepared statements in your web application, you don't need to have them in your database server.

    Seeing how prepared statements are meant to make repeated queries faster, by allowing reuse of the plan, I'd say that this was a stupid thing to remove. Not as stupid as views, though, since those are basically just stored and named queries and as such trivial to implement/maintain.

  • by GNUPublicLicense ( 1242094 ) on Wednesday July 23, 2008 @10:38AM (#24304217)
    Really tiring... really... Still C++... should require C compiler complexity only
    Bazare is ... well, should go for GIT instead.
    And GPL for what, since we have to surrender our GPL rights to a for-profit organisation(Sun upper management and board) and in no case I would like to have my code in their closed proprietary forks...
    We need a Linux-spirit-like SQL DB engine for God Sake!
  • by ducomputergeek ( 595742 ) on Wednesday July 23, 2008 @11:24AM (#24305045)

    I used to do the same thing, reach for MySQL for web applications first simply because there are more hosting companies supporting MySQL for a large number of reasons. I reached for PostgreSQL for intranet or business application where clients could use the features, but maybe could not afford or wanted to spend the money on SQL Server or Oracle. But in the last couple years, I've noticed more hosting companies offering PG support as well. However this changed for me in the past six months when SUN purchased MySQL.

    But SUN buying MySQL and then not really having any what I would call "firm plans" on what they were going to do with it was enough for me to look at PostgreSQL as the db of choice for the latest application I was hired to develop. At this point, PG development seems to be more of a known quantity.

    I could be wrong and Sun might create something that is absolutely amazing and the best. thing. ever. But until then, I'll stick with what I know till something better comes along.

  • by mini me ( 132455 ) on Wednesday July 23, 2008 @04:13PM (#24310145)

    Modern web frameworks these days just use it as a over-glorified hash store anyway. The other features are useless in that context. However, I feel we'll see a move to document databases, such as CouchDB, by those frameworks in the near future leaving MySQL out of the game completely.

  • by ultranova ( 717540 ) on Wednesday July 23, 2008 @04:20PM (#24310241)

    They are also used as a security feature, since you can feed an array of arguments without needing to sanitise them first.

    Yes; and in fact I haven't found another safe way to feed parameters to a database in Java. There doesn't appear to be any kind "sanitize/escape" function nor paremetrized input for non-prepared statements in the JAVA SQL API, so either you write one yourself or stick to PreparedStatements.

    BTW: PostgreSQL supports such out-of-band delivery of parameters even for non-prepared statements.

  • by jlarocco ( 851450 ) on Wednesday July 23, 2008 @04:31PM (#24310411) Homepage

    I think what drives everybody crazy are the people using MySQL who act like they're database experts because of it.

    Just because it does what most people want, doesn't mean it's a very good example of DBMS software.

As of next Tuesday, C will be flushed in favor of COBOL. Please update your programs.