Comments on: The promise of Drizzle http://www.protocolostomy.com/2008/07/27/the-promise-of-drizzle/ Made with only the finest 1's and 0's Thu, 08 Jan 2009 11:25:13 +0000 http://wordpress.org/?v=2.7 hourly 1 By: Log Buffer #108: A Carnival of the Vanities for DBAs http://www.protocolostomy.com/2008/07/27/the-promise-of-drizzle/comment-page-1/#comment-2614 Log Buffer #108: A Carnival of the Vanities for DBAs Fri, 01 Aug 2008 17:05:33 +0000 http://www.protocolostomy.com/?p=344#comment-2614 [...] downpour! Here’s Jay Pipes with Why I Am Involved in Drizzle. Musings of an Anonymous Geek on The Promise of Drizzle. Lukas Kahwe Smith says, “Drizzle, I welcome [...] [...] downpour! Here’s Jay Pipes with Why I Am Involved in Drizzle. Musings of an Anonymous Geek on The Promise of Drizzle. Lukas Kahwe Smith says, “Drizzle, I welcome [...]

]]> By: m0j0 http://www.protocolostomy.com/2008/07/27/the-promise-of-drizzle/comment-page-1/#comment-2596 m0j0 Thu, 31 Jul 2008 00:32:21 +0000 http://www.protocolostomy.com/?p=344#comment-2596 @Frank The scale doesn't really matter in terms of the code involved. You should be free to vertically pad temporal data using whatever granularity is supported by the engine. So, in other words, if MySQL supports date comparison based on day, week, month, year, or century (I'm not aware of century support, but hacks can be had), you should be able to vertically pad that data, because in order to do a comparison, MySQL already has to know what values are valid within the range. As for the join, it's discussed in the post, along with the issues that arise from that (the most obvious one in my case is, ironically, "scale"-related) @Frank

The scale doesn’t really matter in terms of the code involved. You should be free to vertically pad temporal data using whatever granularity is supported by the engine. So, in other words, if MySQL supports date comparison based on day, week, month, year, or century (I’m not aware of century support, but hacks can be had), you should be able to vertically pad that data, because in order to do a comparison, MySQL already has to know what values are valid within the range.

As for the join, it’s discussed in the post, along with the issues that arise from that (the most obvious one in my case is, ironically, “scale”-related)

]]> By: Frank Flynn http://www.protocolostomy.com/2008/07/27/the-promise-of-drizzle/comment-page-1/#comment-2595 Frank Flynn Thu, 31 Jul 2008 00:22:47 +0000 http://www.protocolostomy.com/?p=344#comment-2595 One problem "vertical data-padding" is the scale - if I'm studying genetics in a fruit fly population hours might be more appropriate; if I'm studying geology perhaps centuries. Should MySQL support every possible scale? You could create a table of dates at the granularity you were interested in (in your case it sounded like days) and open join to it. This gives you several other important advantages. I wrote a short tutorial on this at http://www.declan.com/frank/projects/dates/index.php look down about 2/3's to see the specific application for your date-padding issue. One problem “vertical data-padding” is the scale - if I’m studying genetics in a fruit fly population hours might be more appropriate; if I’m studying geology perhaps centuries. Should MySQL support every possible scale?
You could create a table of dates at the granularity you were interested in (in your case it sounded like days) and open join to it. This gives you several other important advantages.

I wrote a short tutorial on this at
http://www.declan.com/frank/projects/dates/index.php
look down about 2/3’s to see the specific application for your date-padding issue.

]]> By: Nome do Jogo » Artigo » Rails Podcast Brasil - Episódio 25 http://www.protocolostomy.com/2008/07/27/the-promise-of-drizzle/comment-page-1/#comment-2563 Nome do Jogo » Artigo » Rails Podcast Brasil - Episódio 25 Tue, 29 Jul 2008 15:15:02 +0000 http://www.protocolostomy.com/?p=344#comment-2563 [...] The promise of Drizzle [...] [...] The promise of Drizzle [...]

]]> By: Parvesh Garg http://www.protocolostomy.com/2008/07/27/the-promise-of-drizzle/comment-page-1/#comment-2557 Parvesh Garg Tue, 29 Jul 2008 05:25:25 +0000 http://www.protocolostomy.com/?p=344#comment-2557 Just last week I was also asked on "query fragments" in one of my sessions on MySQL. I felt it to be good if used (and/or implemented) with caution. For me, something like "no query having more than 5-10% (or configurable) of table rows should be cached" kind of policy will work. Just last week I was also asked on “query fragments” in one of my sessions on MySQL. I felt it to be good if used (and/or implemented) with caution.

For me, something like “no query having more than 5-10% (or configurable) of table rows should be cached” kind of policy will work.

]]>