ralph, that's the problem.. the idea is good, it will work and you
can't say much against it.
but, you also need to look in the future.. when you will need to
refactor, it will go easier when doing it the one-table-for-each-type
method.
--~--~-~--~~~---~--~~
TWIOF wrote:
I'm using one db table for all images (there won't be that many
over all) - so can i have a hasOne and add a condition to only pick
thumbs, and a hasMany with a condition only to pick illustrations.
I don't see why you need to use a separate hasOne. I think you could
just use one
your method is fine, if you have a column called category or
something like that
--~--~-~--~~~---~--~~
You received this message because you are subscribed to the Google Groups
Cake PHP group.
To post to this group, send email to cake-php@googlegroups.com
To
HI Everyone,
I've been making an images system for my site. There are various types
of image (e.g. thumb nails and illustrations). As far as the models go
an article might use hasOne for the thumb nails and hasMany for
illustrations.
BUT, i'm using one db table for all images (there won't be
On 11/14/06, TWIOF [EMAIL PROTECTED] wrote:
HI Everyone,
I've been making an images system for my site. There are various types
of image (e.g. thumb nails and illustrations). As far as the models go
an article might use hasOne for the thumb nails and hasMany for
illustrations.
BUT, i'm
(although, i would personally also use different tables because it's
more future-proof, like Chris said. If you don't have a good reason to
do it your way, i would do it our way ;-)
--~--~-~--~~~---~--~~
You received this message because you are subscribed to
By using phpThumb you could simplify your application logic and abstract
image size to the views.
olivvv
TWIOF wrote:
HI Everyone,
I've been making an images system for my site. There are various types
of image (e.g. thumb nails and illustrations). As far as the models go
an article might
