Funny, I just started re-doing a site for an independent label, also.
While I'm not creating separate sites for each artist, I've decided to
do pretty much all of the SELECTs based on the artists' slugs. So,
instead of doing a read(null, $id) I need to do a findBySlug($slug)
and adjust the routes accordingly.
If you're creating entirely separate Cake sites for each artist, you
could define('ARTIST_SLUG', 'whatever') in each bootstrap.php. Once
you've done your basic selection based on the slug you should be able
to leave your recursive associations based on the id, as normal.
On Mon, Apr 21, 2008 at 5:44 PM, tgies <[EMAIL PROTECTED]> wrote:
>
> I am setting up a website for an independent music publisher.
>
> Rather, I am setting up three websites: the label's own website and
> three artists' websites. We will call the artists foo, bar, and plugh.
>
> All of these sites use the same database. The rationale behind this is
> that each artist's catalog can be populated with their songs/albums
> from the label's central catalog, with the label's catalog displaying
> all songs/albums from all artists.
>
> All models are associated with a certain artist_id, which should make
> it possible for each artist's site to transparently only select its
> own database records. But how would I go about doing this? Is there
> something I can add to AppModel to automatically add this constraint
> to every find?
>
> Thanks,
> tgies
>
> >
>
--~--~---------~--~----~------------~-------~--~----~
You received this message because you are subscribed to the Google Groups
"CakePHP" group.
To post to this group, send email to cake-php@googlegroups.com
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
-~----------~----~----~----~------~----~------~--~---
