@Jeremy: Yes, I was cringing at the length of my post too, but I've
been thinking about this a while and I felt compelled to explain
fully. Thanks for time. It sounds like you got the point perfectly,
and your suggestions are right in line with my thinking. I'm happy :)
I imagine I'll want to use c
Does the public database is read only from the end user perspective?
If it is you can use MySql views as a model table.
Cake treat views as table.
I think its more easy to maintain read only data this way.
About the data structure it seems you are in the right way.
If you want to take an example f
It's a long post, so I hope I haven't missed the point...
I'd say that having a single, well thought out database is better than having
two, so you are going in the right direction.
Yes, you can access related data from the Schedule model, so long as they are
associated (and even if they are no
Hi,
My question is below, but first some info about the situation I'm in:
I am taking an app that I wrote years ago for scheduling people in
different areas of work at our Center, and re-writing it in cakePHP.
In the mean time, I'm doing all sorts of things better than ever
before ;)
Among many
