i didnt't realize why the use of views should
a) be not portable and
b) not indexable
?
nearly every database supports views, so i could't see a problem
there. and the columns listed in a view of course might be indexed in
the underlaying table. the only problem i see is that you might not be
Thanks, deefens. I didn't think I was totally crazy about the view
idea. :)
I did some research on the mysql pages, and you _can_ write to mysql
views. I also did some research here, and it appears that views aren't
officially supported in Cake, and some folks claimed they didn't work,
period.
The question of whether it's a waste of time, or is this a useful
endeavor depends largely on your level tolerance for ugly prefixes all
over your code. If you are going to do it, however, I would say
afterFind is not the answer. A far better bet would be to subclass
the MySQL driver and
Thanks, nate. Thats useful info.
The datasource doesn't have direct access to the model, does it? The
column prefixes are different by table, so (if I understand it right),
if I extend the mySQL driver, I'll have to extend other classes to
pass the model name (or at least the column prefix
The DataSource has direct access to the model all over the place.
Look at all the places in DboSouce/DboMysql where it says $model.
On Jan 12, 12:35 am, Robby Anderson [EMAIL PROTECTED] wrote:
Thanks, nate. Thats useful info.
The datasource doesn't have direct access to the model, does it?
