| # |
Mar 13th 2009, 13:04 |
AD7six |
I think if it was a debug kit extension it /could/ be. as it would demonstate how to add to it in addition to being interesting if not useful to some. |
| # |
Mar 13th 2009, 13:04 |
alkemann |
"The topic should be of interest to a broad range of CakePHP developers." - in my eyes it a hacky solution that will generate more bad components than it will help developers debug their sql |
| # |
Mar 13th 2009, 13:03 |
jperras |
I'm not sure. |
| # |
Mar 13th 2009, 13:02 |
alkemann |
ok. let me ask in a different way, does this article fufill the rule of being generally useful for a significant part of the community? |
| # |
Mar 13th 2009, 13:01 |
AD7six |
in addition to: "someone please help with my spelling" |
| # |
Mar 13th 2009, 13:01 |
AD7six |
jperras: the other thought I had was simpley: is it needed at all (mysql slow query log, other db analysis tools)? |
| # |
Mar 13th 2009, 13:00 |
AD7six |
jperras: yeah exactly |
| # |
Mar 13th 2009, 13:00 |
alkemann |
personally i dont really see the added value, but im not a database guy.. wouldnt it be possible to extend overwrite the existing debug 2 instead of adding another element? |
| # |
Mar 13th 2009, 13:00 |
jperras |
AD7six: problem is that, currently, there is no easy way to accomplish what he wants in a CakePHP-centric manner. |
| # |
Mar 13th 2009, 13:00 |
AD7six |
anyway I'm glad I asked/punted ;). |
| # |
Mar 13th 2009, 12:59 |
AD7six |
or summarized as drop-in-ability |
| # |
Mar 13th 2009, 12:58 |
AD7six |
hmm I think the compactness of what he's proposing (given current code base) should be weighed against how many class he'd need to touch to do it another way. |
| # |
Mar 13th 2009, 12:57 |
alkemann |
as in add.ctp |
| # |
Mar 13th 2009, 12:57 |
AD7six |
view as in element? |
| # |
Mar 13th 2009, 12:57 |
alkemann |
i think he meant view, not View |
| # |
Mar 13th 2009, 12:56 |
AD7six |
I never like it wehenver a new view class is the answer - can only extend one. |
| # |
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. |