> I was expecting that response. Though I've seen many benchmarks and > quality articles that argue it's a viable solution. Afterall, why else > would MySQL bother to implement it? ;) And I'll never know which is > better if I don't try...
Last I heard, flickr stored all of it's images in MySQL. I think images in databases can be acceptable, if you've tuned your database servers, if you handle (or specifically don't want) last-modified and 304, and if there's a lot of metadata associated with the images. Also, in possible answer to your main question, the fields argument needs the table names to be in the form of model names. So instead of users.name I would need to use `User`.name. Hope that helps --~--~---------~--~----~------------~-------~--~----~ 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 -~----------~----~----~----~------~----~------~--~---
