f which there aren't many).
Unfortunately it didn't work anyway. Django's escaping of the SQL
arguments means you end with a table called "SCHEMA_PREFIX.model" in
the public schema.
I'll do it your way.
Nick
On Apr 25, 1:29 pm, Doug Van Horn <[EMAIL PROTECTED]> wrot
Hello all.
I'm creating a CMS/e-commerce Django project for a client which will
ultimately be used to handle content for three different domains.
In terms of sharing of resources:
- content will not be shared between sites
- public templates will differ between sites
- the administration interfa
> files. The only problem I can see is if you specify a different DB in
> each settings.py, you'll need to create the same admin accounts in
> each.
>
> -Robin
>
> On Apr 24, 7:22 am, Nick Tidey <[EMAIL PROTECTED]> wrote:
>
> > Hello all.
>
> > I
3 matches
Mail list logo
