Log message #590170

# At Username Text
# Mar 13th 2009, 12:56 alkemann so the question is, how do we given the current situation (ie bakery 1.0) welcome the contribution of the concept while dealing with the problems of the presented solution?
# Mar 13th 2009, 12:55 AD7six but maybe I'm thinking too linearly..
# Mar 13th 2009, 12:55 jperras it should almost be a plugin. perhaps a datasource + custom view
# Mar 13th 2009, 12:55 AD7six I don't think it's fair or appropriate to say "you should create your own datasource to do that"
# Mar 13th 2009, 12:54 jperras it's even more obviously a datasource addition since it's highly dbo dependent
# Mar 13th 2009, 12:54 alkemann right. so he is combining model and view stuff into one component
# Mar 13th 2009, 12:54 jperras yeah
# Mar 13th 2009, 12:53 alkemann nm, still earlier in us
# Mar 13th 2009, 12:53 _nate_ jperras: the logging part, sure
# Mar 13th 2009, 12:53 jperras _nate_: I agree that query logging isn't perfect as it is now. however, query logging seems to me as a datasource/dbo level operatoin
# Mar 13th 2009, 12:52 alkemann shouldnt u be out celebrating nate?
# Mar 13th 2009, 12:52 _nate_ well, it's glue
# Mar 13th 2009, 12:52 alkemann i like the concept of adding it to the debug kit. i dont like posting it as it is, because it continues a widespread overuse of components for stuff that belongs either in model or view level
# Mar 13th 2009, 12:49 AD7six you'd still need a component for collecting your data to send to the view though (I currently assume)
# Mar 13th 2009, 12:49 _nate_ yeah, it's definitely a concept
# Mar 13th 2009, 12:49 AD7six another panel
# Mar 13th 2009, 12:49 alkemann yes, with bakery2.0 we could have posted it with "good concept but probably wrong implementation"-marker to inspire someone to rewrite it
# Mar 13th 2009, 12:48 AD7six I suggested it be implemented as an extension to debug_kit
# Mar 13th 2009, 12:48 _nate_ jperras: well, the whole current approach to query logging right now is wrong
# Mar 13th 2009, 12:48 AD7six how do you implement it another way without overriding all your datasources
# Mar 13th 2009, 12:48 AD7six "I dunno"
# Mar 13th 2009, 12:48 jperras A component is the wrong choice for that
# Mar 13th 2009, 12:46 _nate_ yup
# Mar 13th 2009, 12:46 AD7six _nate_: that one ^
# Mar 13th 2009, 12:45 alkemann questionable use, probably bad implementation.
# Mar 13th 2009, 12:45 alkemann http://bakery.cakephp.org/articles/view/auto-sql-explain-component
# Mar 13th 2009, 12:45 jperras the what now?
# Mar 13th 2009, 12:44 alkemann AD7six: have u come to any decission or gotten a second opinion about the SQL explain component?
# Mar 13th 2009, 12:44 jperras thanks
# Mar 13th 2009, 12:44 alkemann ok, did
# Mar 13th 2009, 12:36 jperras alkemann: there was an issue the other day with 3 of the same article appearing
# Mar 13th 2009, 12:36 jperras alkemann: delete them
# Mar 13th 2009, 12:31 AD7six re (sorta) fixed - authors can delete comments (I think)
# Mar 13th 2009, 12:29 AD7six wiki page saved btw
# Mar 13th 2009, 12:29 AD7six on the wiki, or with the bakery itself?
# Mar 13th 2009, 12:20 alkemann i was thinking of slug rename problem
# Mar 13th 2009, 12:20 alkemann AD7six: sure
# Mar 13th 2009, 12:20 alkemann jperras: two of those LDAP articles u talked about are currently in pending. did u need them there or can i softdelete em?
# Mar 13th 2009, 12:19 AD7six well, it's misleading. name it "markers"? I'm editing it right now anyway
# Mar 13th 2009, 12:18 alkemann admad correctly pointed out that this isnt moderation, but i think of it as moderation tools.. maybe not worth the hassle of rename?
# Mar 13th 2009, 12:18 AD7six I'm adding a note to articles/moderation regarding deprecated -> marker + taken out of indexes.