Hi All,

Just thought I'd chip in...

If focus is brought to bear on the source of the problem - which has 
been mentioned before (http://www.google.com/search?
hl=en&client=firefox-a&rls=org.mozilla%3Aes-ES
%3Aofficial&q=mysql_fetch_field+wrong+table+VIEWS&btnG=Search) - It 
might become aparent why the cake team probably are not so interested 
in 'fixing' this. Adding code to handle the errors of 3rd party code 
isn't really inline with the "no-bloat" approach of the Cake team. 
Does the patch in ticket 1307 have any sideffects (i.e. fixes the 
posed question, but breaks normal queries, adds to execution time, 
etc. I would assume not, but..)?

On Jan 29, 6:48 am, Bernard Grosperrin <[EMAIL PROTECTED]> 
wrote:
<snip>
> But I don't want to be constrained by the Framework, on the contrary....

How about just using the method rawQuery (or whichever is the lowest 
common-denominator model query method)? I'm sure there will be a way 
to bypass the ActiveRecord-yness that is there by default if needed. 
It would be a pity to dismiss 80% of the usefulness because for 20% of 
the time it's necessary to do things the normal/pseudo-normal way. 
Cake is rather flexible, there is pretty much always a way to achieve 
something.

> And I want a framework to not have to reinvent the wheel when I need users to 
> login, for example.
You mean like having a repository full of stuff you can just include 
(Bakery)? Btw, Have a look at the new classes in the 1.2 svn branch.

HTH,

AD7six
PS. what does it mean to be a "cake"?
Please note:
The manual/bakery is a good place to start any quest for info.
the IRC Channel (you can access it with just a browser
here:http://irc.cakephp.org).


--~--~---------~--~----~------------~-------~--~----~
You received this message because you are subscribed to the Google Groups "Cake 
PHP" group.
To post to this group, send email to [email protected]
To unsubscribe from this group, send email to [EMAIL PROTECTED]
For more options, visit this group at 
http://groups.google.com/group/cake-php?hl=en
-~----------~----~----~----~------~----~------~--~---

Reply via email to