Same here. I just spend several days profiling some of our code only to find that 50% of the CPU was being used for date formatting using a pigish Perl module. Thankfully I was able to fix that without having to beat on MySQL, but DATE_FORMAT() is used all over the freaking place...
Jeremy On Wed, Feb 4, 2009 at 10:34 AM, Brian Aker <[email protected]> wrote: > Hi! > > On Feb 4, 2009, at 2:07 AM, Jay Pipes wrote: > > I would actually argue that DATE_FORMAT() is the function that is overly >>> complex... >>> >> >> Agreed. >> > > I use the hell out of this function :) > > Though, I have told people over and over again to put this sort of thing up > in their display logic and get it out of their SQL. > > The problem has been that there have been few/fast date manipulation > libraries available (especially in perl). So you fall back to using the > database to do the heavy lifting for you. > > Cheers, > -Brian > > > -- > _______________________________________________________ > Brian "Krow" Aker, brian at tangent.org > Seattle, Washington > http://krow.net/ <-- Me > http://tangent.org/ <-- Software > _______________________________________________________ > You can't grep a dead tree. > > > > > > _______________________________________________ > Mailing list: > https://launchpad.net/~drizzle-discuss<https://launchpad.net/%7Edrizzle-discuss> > Post to : [email protected] > Unsubscribe : > https://launchpad.net/~drizzle-discuss<https://launchpad.net/%7Edrizzle-discuss> > More help : https://help.launchpad.net/ListHelp >
_______________________________________________ Mailing list: https://launchpad.net/~drizzle-discuss Post to : [email protected] Unsubscribe : https://launchpad.net/~drizzle-discuss More help : https://help.launchpad.net/ListHelp
