Comments on: Return of the “Top 5 MySQL Wishlist” and looking at Drizzle http://www.flamingspork.com/blog/2009/10/14/return-of-the-top-5-mysql-wishlist-and-looking-at-drizzle/ Ramblings which occasionally resemble reality. This is the blog of Stewart Smith. Mon, 30 Aug 2010 10:19:35 +0000 hourly 1 http://wordpress.org/?v=3.0.1 By: Brian Aker http://www.flamingspork.com/blog/2009/10/14/return-of-the-top-5-mysql-wishlist-and-looking-at-drizzle/comment-page-1/#comment-90542 Brian Aker Wed, 14 Oct 2009 16:34:48 +0000 http://www.flamingspork.com/blog/?p=1738#comment-90542 @Callaghan HPUX was a mess of ifdef. I suspect a modern version of HPUX might just work, but we started with support for 10.20... and that was just too old. @Callaghan HPUX was a mess of ifdef. I suspect a modern version of HPUX might just work, but we started with support for 10.20… and that was just too old.

]]> By: Mark Callaghan http://www.flamingspork.com/blog/2009/10/14/return-of-the-top-5-mysql-wishlist-and-looking-at-drizzle/comment-page-1/#comment-90541 Mark Callaghan Wed, 14 Oct 2009 15:30:05 +0000 http://www.flamingspork.com/blog/?p=1738#comment-90541 Was HPUX support the thing that required ifdefs to reverse the results for one or more library functions (result = !result if using HPUX)? Was HPUX support the thing that required ifdefs to reverse the results for one or more library functions (result = !result if using HPUX)?

]]> By: Daniel van Eeden http://www.flamingspork.com/blog/2009/10/14/return-of-the-top-5-mysql-wishlist-and-looking-at-drizzle/comment-page-1/#comment-90540 Daniel van Eeden Wed, 14 Oct 2009 14:12:36 +0000 http://www.flamingspork.com/blog/?p=1738#comment-90540 Hi Stewart, Thanks for info :) I will try to find some time and I will give it a try. It looks very promising Regards, Daniel Hi Stewart,

Thanks for info :)
I will try to find some time and I will give it a try. It looks very promising

Regards,

Daniel

]]> By: Stewart Smith http://www.flamingspork.com/blog/2009/10/14/return-of-the-top-5-mysql-wishlist-and-looking-at-drizzle/comment-page-1/#comment-90537 Stewart Smith Wed, 14 Oct 2009 11:41:57 +0000 http://www.flamingspork.com/blog/?p=1738#comment-90537 1. Per user and/or per database quota Nothing yet.... although you could write a plugin that hooks into the right places that grants/denys based on usage. 2. External authentication Already possible in Drizzle. we have a couple of plugins, including auth_pam. 3. Database locator Something will be coming to help with sharding in libdrizzle soon. I suggest you take this to the drizzle-discuss mailing list as a request, and Eric can probably figure something out that works for both. 4. Saving extra metadata about the database. Nothing in this direction yet. Perhaps propose something? Probably tricky to get right though... and does this really belong in the database server? Perhaps a table with foreign keys to the data dict? 5. better protection against run-away queries Interesting idea, nothing that I'm really aware of.... but I have some ideas on how to properly do this. 6. restore manager This'd be neat. Especially if we create a dump and restore tool that takes the replication protobuf format, then it should be rather easy to write such filter/ui tools in any language (e.g. python) 7. SNMP for statistics If you know how to put SNMP on the wire, it'd be easy to write a Drizzle plugin to do this. In fact, I really encourage you to! 8. SNMP for alerting See above, very much would love to see a patch. 8. Auditing We have a pluggable logging infrastructure, so if there isn't already, it'd be trivial to write such a plugin. hope that helps, stewart 1. Per user and/or per database quota

Nothing yet…. although you could write a plugin that hooks into the right places that grants/denys based on usage.

2. External authentication

Already possible in Drizzle. we have a couple of plugins, including auth_pam.

3. Database locator

Something will be coming to help with sharding in libdrizzle soon. I suggest you take this to the drizzle-discuss mailing list as a request, and Eric can probably figure something out that works for both.

4. Saving extra metadata about the database.

Nothing in this direction yet. Perhaps propose something? Probably tricky to get right though… and does this really belong in the database server? Perhaps a table with foreign keys to the data dict?

5. better protection against run-away queries

Interesting idea, nothing that I’m really aware of…. but I have some ideas on how to properly do this.

6. restore manager

This’d be neat. Especially if we create a dump and restore tool that takes the replication protobuf format, then it should be rather easy to write such filter/ui tools in any language (e.g. python)

7. SNMP for statistics

If you know how to put SNMP on the wire, it’d be easy to write a Drizzle plugin to do this. In fact, I really encourage you to!

8. SNMP for alerting

See above, very much would love to see a patch.

8. Auditing

We have a pluggable logging infrastructure, so if there isn’t already, it’d be trivial to write such a plugin.

hope that helps,
stewart

]]> By: Daniel van Eeden http://www.flamingspork.com/blog/2009/10/14/return-of-the-top-5-mysql-wishlist-and-looking-at-drizzle/comment-page-1/#comment-90536 Daniel van Eeden Wed, 14 Oct 2009 11:21:00 +0000 http://www.flamingspork.com/blog/?p=1738#comment-90536 Hi, I also mad a wishlist: http://dveeden.livejournal.com/7769.html If I'm well informed then my second point (authentication) should be possible using drizzle. What about the other points? Regards, Daniel Hi,

I also mad a wishlist:
http://dveeden.livejournal.com/7769.html

If I’m well informed then my second point (authentication) should be possible using drizzle. What about the other points?

Regards,

Daniel

]]>