Re: Using Multiple databases

[Ryan Nowakowski]

On Wed, Apr 06, 2022 at 08:59:09AM -0700, Vasanth Mohan wrote:
> I'm building a PoC for a multi-tenant app where I'm trying to use the same 
> schema across multiple databases with Django instance. I've got a couple of 
> questions and I'd be happy to have some input
> 
> 1. Is there a way to define the *using()* function to use with Models via a 
> lib/middleware?
> 2. Is there a way to create admin users so that they have access to 
> specific databases? 

You probably want to create a custom database router[1].

[1] 
https://docs.djangoproject.com/en/4.0/topics/db/multi-db/#automatic-database-routing

-- 
You received this message because you are subscribed to the Google Groups 
"Django users" group.
To unsubscribe from this group and stop receiving emails from it, send an email 
to django-users+unsubscr...@googlegroups.com.
To view this discussion on the web visit 
https://groups.google.com/d/msgid/django-users/20220415180748.GC15520%40fattuba.com.

Re: Using multiple databases

[Ben Ford]

It won't be in 1.0. It's only really been kicked off recently, so you'll
have to wait a while :-)

2008/7/21 CPF_ <[EMAIL PROTECTED]>:

>
> Ben Ford wrote:
> > Hi There,
> >
> > It has been possible in the past to use multiple databases with
> > django. There was a branch for it and about a year ago it was bought
> > up to date with trunk. However that branch hasn't seen any activity
> > for some time and is effectively dead. There's now a (low key) effort
> > under way to come up with a new API and to take advantage of the
> > recent work in refactoring the database API to again make it possible
> > to use multiple databases in your django project. As it stands at the
> > moment it's at an early stage, and it's really unlikely that anything
> > significant will happen until django 1.0 arrives.
> >
> > My advice based on what you've said above would be to use django's ORM
> > for your authentication (and sessions, permissions, groups etc) if
> > it's a good fit for you. That way you'd get all of the great time
> > saving bits of django (like request.user, perms in the template
> > language, authentication cookies etc). In addition to that  maybe
> > you'd like to think about using a different ORM for talking to the
> > other database. There is a project underway on google code to make
> > using SQLAlchemy easier with django - this might be the way to go.
> >
> > I'm not sure what others on this mailing list would think about this
> > approach... I'd certainly be interested to hear any thoughts!
> >
> > Cheers,
> > Ben
> >
> > 2008/7/20 CPF_ <[EMAIL PROTECTED]
> > >:
> >
> >
> > [EMAIL PROTECTED]  wrote:
> > > Dan wrote:
> > >>
> > >> Most ideally we would like to have it so that the application
> > >> uses DB1
> > >> (defined in the settings.py file) as the main database, but
> > when
> > >> it's
> > >> down to users, uses DB2.user as the users table.
> > >> Currently we are thinking of using raw sql, but that would
> > only be a
> > >> last resort preferably. And at that point I'd be more
> scrambled
> > >> on how
> > >> to use authenticate together with it.
> > >>
> > >>
> > >> If you are using MySQL, you can use the federated engine for
> tables
> > >> that are only "symlinks" to real tables in another database but
> > will
> > >> act as normal tables when doing regular operations on them.
> > >>
> > >> It might be possible with other databases too, I don't know.
> > > Hi Dan, thanks for the reply.
> > > We are indeed using MySQL, and attemipting to symlink (as the mysql
> > > documentation at
> > >
> > http://dev.mysql.com/doc/refman/5.0/en/symbolic-links-to-tables.html)
> > > didn't work out ("SQL show index from `users` failed : Table
> > > 'bingo.users' doesn't exist" is what webmin said)
> > >
> > > If you're implying some other technique, I have no idea what you
> are
> > > talking about - could you please explain, or redirect to a page
> > > explaining it?
> > >
> > > Thanks.
> > Sorry for kicking this subject, but I'd really like to have an
> > answer to
> > that...
> >
> > Thanks in advance.
> >
> >
> >
> >
> >
> > --
> > Regards,
> > Ben Ford
> > [EMAIL PROTECTED] 
> > +447792598685
> Hi Ben,
> Thanks a lot for the explanation and the insight. I'll be looking up
> some of those ideas you mentioned, and the way you explain it is really
> the way I would like to do it.
> Currently I started development using a standard auth_users but at some
> time, I would like to use the users database already existing...
> There's the other possibility to change the project originally using the
> database. However, regardless, I would still know the way to use
> multiple databases, and if it will be integrated in the 1.0 release, I
> really believe that I will use the 1.0 a lot. Therefore I'll look for
> that feature.
>
> cpf_
>
> >
>


-- 
Regards,
Ben Ford
[EMAIL PROTECTED]
+447792598685

--~--~-~--~~~---~--~~
You received this message because you are subscribed to the Google Groups 
"Django users" group.
To post to this group, send email to django-users@googlegroups.com
To unsubscribe from this group, send email to [EMAIL PROTECTED]
For more options, visit this group at 
http://groups.google.com/group/django-users?hl=en
-~--~~~~--~~--~--~---

Re: Using multiple databases

[Amirouche]

Have a look a this http://code.djangoproject.com/ticket/4747 &
http://trac.woe-beti.de/

On 21 juil, 03:04, CPF_ <[EMAIL PROTECTED]> wrote:
> Ben Ford wrote:
> > Hi There,
>
> > It has been possible in the past to use multiple databases with
> > django. There was a branch for it and about a year ago it was bought
> > up to date with trunk. However that branch hasn't seen any activity
> > for some time and is effectively dead. There's now a (low key) effort
> > under way to come up with a new API and to take advantage of the
> > recent work in refactoring the database API to again make it possible
> > to use multiple databases in your django project. As it stands at the
> > moment it's at an early stage, and it's really unlikely that anything
> > significant will happen until django 1.0 arrives.
>
> > My advice based on what you've said above would be to use django's ORM
> > for your authentication (and sessions, permissions, groups etc) if
> > it's a good fit for you. That way you'd get all of the great time
> > saving bits of django (like request.user, perms in the template
> > language, authentication cookies etc). In addition to that  maybe
> > you'd like to think about using a different ORM for talking to the
> > other database. There is a project underway on google code to make
> > using SQLAlchemy easier with django - this might be the way to go.
>
> > I'm not sure what others on this mailing list would think about this
> > approach... I'd certainly be interested to hear any thoughts!
>
> > Cheers,
> > Ben
>
> > 2008/7/20 CPF_ <[EMAIL PROTECTED]
> > >:
>
> >     [EMAIL PROTECTED]  wrote:
> >     > Dan wrote:
>
> >     >>     Most ideally we would like to have it so that the application
> >     >> uses DB1
> >     >>     (defined in the settings.py file) as the main database, but
> >     when
> >     >> it's
> >     >>     down to users, uses DB2.user as the users table.
> >     >>     Currently we are thinking of using raw sql, but that would
> >     only be a
> >     >>     last resort preferably. And at that point I'd be more scrambled
> >     >> on how
> >     >>     to use authenticate together with it.
>
> >     >> If you are using MySQL, you can use the federated engine for tables
> >     >> that are only "symlinks" to real tables in another database but
> >     will
> >     >> act as normal tables when doing regular operations on them.
>
> >     >> It might be possible with other databases too, I don't know.
> >     > Hi Dan, thanks for the reply.
> >     > We are indeed using MySQL, and attemipting to symlink (as the mysql
> >     > documentation at
>
> >    http://dev.mysql.com/doc/refman/5.0/en/symbolic-links-to-tables.html)
> >     > didn't work out ("SQL show index from `users` failed : Table
> >     > 'bingo.users' doesn't exist" is what webmin said)
>
> >     > If you're implying some other technique, I have no idea what you are
> >     > talking about - could you please explain, or redirect to a page
> >     > explaining it?
>
> >     > Thanks.
> >     Sorry for kicking this subject, but I'd really like to have an
> >     answer to
> >     that...
>
> >     Thanks in advance.
>
> > --
> > Regards,
> > Ben Ford
> > [EMAIL PROTECTED] 
> > +447792598685
>
> Hi Ben,
> Thanks a lot for the explanation and the insight. I'll be looking up
> some of those ideas you mentioned, and the way you explain it is really
> the way I would like to do it.
> Currently I started development using a standard auth_users but at some
> time, I would like to use the users database already existing...
> There's the other possibility to change the project originally using the
> database. However, regardless, I would still know the way to use
> multiple databases, and if it will be integrated in the 1.0 release, I
> really believe that I will use the 1.0 a lot. Therefore I'll look for
> that feature.
>
> cpf_
--~--~-~--~~~---~--~~
You received this message because you are subscribed to the Google Groups 
"Django users" group.
To post to this group, send email to django-users@googlegroups.com
To unsubscribe from this group, send email to [EMAIL PROTECTED]
For more options, visit this group at 
http://groups.google.com/group/django-users?hl=en
-~--~~~~--~~--~--~---

Re: Using multiple databases

[CPF_]

Ben Ford wrote:
> Hi There,
>
> It has been possible in the past to use multiple databases with 
> django. There was a branch for it and about a year ago it was bought 
> up to date with trunk. However that branch hasn't seen any activity 
> for some time and is effectively dead. There's now a (low key) effort 
> under way to come up with a new API and to take advantage of the 
> recent work in refactoring the database API to again make it possible 
> to use multiple databases in your django project. As it stands at the 
> moment it's at an early stage, and it's really unlikely that anything 
> significant will happen until django 1.0 arrives.
>
> My advice based on what you've said above would be to use django's ORM 
> for your authentication (and sessions, permissions, groups etc) if 
> it's a good fit for you. That way you'd get all of the great time 
> saving bits of django (like request.user, perms in the template 
> language, authentication cookies etc). In addition to that  maybe 
> you'd like to think about using a different ORM for talking to the 
> other database. There is a project underway on google code to make 
> using SQLAlchemy easier with django - this might be the way to go.
>
> I'm not sure what others on this mailing list would think about this 
> approach... I'd certainly be interested to hear any thoughts!
>
> Cheers,
> Ben
>
> 2008/7/20 CPF_ <[EMAIL PROTECTED] 
> >:
>
>
> [EMAIL PROTECTED]  wrote:
> > Dan wrote:
> >>
> >> Most ideally we would like to have it so that the application
> >> uses DB1
> >> (defined in the settings.py file) as the main database, but
> when
> >> it's
> >> down to users, uses DB2.user as the users table.
> >> Currently we are thinking of using raw sql, but that would
> only be a
> >> last resort preferably. And at that point I'd be more scrambled
> >> on how
> >> to use authenticate together with it.
> >>
> >>
> >> If you are using MySQL, you can use the federated engine for tables
> >> that are only "symlinks" to real tables in another database but
> will
> >> act as normal tables when doing regular operations on them.
> >>
> >> It might be possible with other databases too, I don't know.
> > Hi Dan, thanks for the reply.
> > We are indeed using MySQL, and attemipting to symlink (as the mysql
> > documentation at
> >
> http://dev.mysql.com/doc/refman/5.0/en/symbolic-links-to-tables.html )
> > didn't work out ("SQL show index from `users` failed : Table
> > 'bingo.users' doesn't exist" is what webmin said)
> >
> > If you're implying some other technique, I have no idea what you are
> > talking about - could you please explain, or redirect to a page
> > explaining it?
> >
> > Thanks.
> Sorry for kicking this subject, but I'd really like to have an
> answer to
> that...
>
> Thanks in advance.
>
>
>
>
>
> -- 
> Regards,
> Ben Ford
> [EMAIL PROTECTED] 
> +447792598685
Hi Ben,
Thanks a lot for the explanation and the insight. I'll be looking up 
some of those ideas you mentioned, and the way you explain it is really 
the way I would like to do it.
Currently I started development using a standard auth_users but at some 
time, I would like to use the users database already existing...
There's the other possibility to change the project originally using the 
database. However, regardless, I would still know the way to use 
multiple databases, and if it will be integrated in the 1.0 release, I 
really believe that I will use the 1.0 a lot. Therefore I'll look for 
that feature.

cpf_

--~--~-~--~~~---~--~~
You received this message because you are subscribed to the Google Groups 
"Django users" group.
To post to this group, send email to django-users@googlegroups.com
To unsubscribe from this group, send email to [EMAIL PROTECTED]
For more options, visit this group at 
http://groups.google.com/group/django-users?hl=en
-~--~~~~--~~--~--~---

Re: Using multiple databases

[Ben Ford]

Hi There,

It has been possible in the past to use multiple databases with django.
There was a branch for it and about a year ago it was bought up to date with
trunk. However that branch hasn't seen any activity for some time and is
effectively dead. There's now a (low key) effort under way to come up with a
new API and to take advantage of the recent work in refactoring the database
API to again make it possible to use multiple databases in your django
project. As it stands at the moment it's at an early stage, and it's really
unlikely that anything significant will happen until django 1.0 arrives.

My advice based on what you've said above would be to use django's ORM for
your authentication (and sessions, permissions, groups etc) if it's a good
fit for you. That way you'd get all of the great time saving bits of django
(like request.user, perms in the template language, authentication cookies
etc). In addition to that  maybe you'd like to think about using a different
ORM for talking to the other database. There is a project underway on google
code to make using SQLAlchemy easier with django - this might be the way to
go.

I'm not sure what others on this mailing list would think about this
approach... I'd certainly be interested to hear any thoughts!

Cheers,
Ben

2008/7/20 CPF_ <[EMAIL PROTECTED]>:

>
> [EMAIL PROTECTED] wrote:
> > Dan wrote:
> >>
> >> Most ideally we would like to have it so that the application
> >> uses DB1
> >> (defined in the settings.py file) as the main database, but when
> >> it's
> >> down to users, uses DB2.user as the users table.
> >> Currently we are thinking of using raw sql, but that would only be a
> >> last resort preferably. And at that point I'd be more scrambled
> >> on how
> >> to use authenticate together with it.
> >>
> >>
> >> If you are using MySQL, you can use the federated engine for tables
> >> that are only "symlinks" to real tables in another database but will
> >> act as normal tables when doing regular operations on them.
> >>
> >> It might be possible with other databases too, I don't know.
> > Hi Dan, thanks for the reply.
> > We are indeed using MySQL, and attemipting to symlink (as the mysql
> > documentation at
> > http://dev.mysql.com/doc/refman/5.0/en/symbolic-links-to-tables.html )
> > didn't work out ("SQL show index from `users` failed : Table
> > 'bingo.users' doesn't exist" is what webmin said)
> >
> > If you're implying some other technique, I have no idea what you are
> > talking about - could you please explain, or redirect to a page
> > explaining it?
> >
> > Thanks.
> Sorry for kicking this subject, but I'd really like to have an answer to
> that...
>
> Thanks in advance.
>
> >
>


-- 
Regards,
Ben Ford
[EMAIL PROTECTED]
+447792598685

--~--~-~--~~~---~--~~
You received this message because you are subscribed to the Google Groups 
"Django users" group.
To post to this group, send email to django-users@googlegroups.com
To unsubscribe from this group, send email to [EMAIL PROTECTED]
For more options, visit this group at 
http://groups.google.com/group/django-users?hl=en
-~--~~~~--~~--~--~---

Re: Using multiple databases

[CPF_]

[EMAIL PROTECTED] wrote:
> Dan wrote:
>>
>> Most ideally we would like to have it so that the application 
>> uses DB1
>> (defined in the settings.py file) as the main database, but when 
>> it's
>> down to users, uses DB2.user as the users table.
>> Currently we are thinking of using raw sql, but that would only be a
>> last resort preferably. And at that point I'd be more scrambled 
>> on how
>> to use authenticate together with it.
>>
>>
>> If you are using MySQL, you can use the federated engine for tables 
>> that are only "symlinks" to real tables in another database but will 
>> act as normal tables when doing regular operations on them.
>>
>> It might be possible with other databases too, I don't know.
> Hi Dan, thanks for the reply.
> We are indeed using MySQL, and attemipting to symlink (as the mysql 
> documentation at 
> http://dev.mysql.com/doc/refman/5.0/en/symbolic-links-to-tables.html ) 
> didn't work out ("SQL show index from `users` failed : Table 
> 'bingo.users' doesn't exist" is what webmin said)
>
> If you're implying some other technique, I have no idea what you are 
> talking about - could you please explain, or redirect to a page 
> explaining it?
>
> Thanks.
Sorry for kicking this subject, but I'd really like to have an answer to 
that...

Thanks in advance.

--~--~-~--~~~---~--~~
You received this message because you are subscribed to the Google Groups 
"Django users" group.
To post to this group, send email to django-users@googlegroups.com
To unsubscribe from this group, send email to [EMAIL PROTECTED]
For more options, visit this group at 
http://groups.google.com/group/django-users?hl=en
-~--~~~~--~~--~--~---

Re: Using multiple databases

[[EMAIL PROTECTED]]

Dan wrote:
>
> Most ideally we would like to have it so that the application uses DB1
> (defined in the settings.py file) as the main database, but when it's
> down to users, uses DB2.user as the users table.
> Currently we are thinking of using raw sql, but that would only be a
> last resort preferably. And at that point I'd be more scrambled on how
> to use authenticate together with it.
>
>
> If you are using MySQL, you can use the federated engine for tables 
> that are only "symlinks" to real tables in another database but will 
> act as normal tables when doing regular operations on them.
>
> It might be possible with other databases too, I don't know.
Hi Dan, thanks for the reply.
We are indeed using MySQL, and attemipting to symlink (as the mysql 
documentation at 
http://dev.mysql.com/doc/refman/5.0/en/symbolic-links-to-tables.html ) 
didn't work out ("SQL show index from `users` failed : Table 
'bingo.users' doesn't exist" is what webmin said)

If you're implying some other technique, I have no idea what you are 
talking about - could you please explain, or redirect to a page 
explaining it?

Thanks.

--~--~-~--~~~---~--~~
You received this message because you are subscribed to the Google Groups 
"Django users" group.
To post to this group, send email to django-users@googlegroups.com
To unsubscribe from this group, send email to [EMAIL PROTECTED]
For more options, visit this group at 
http://groups.google.com/group/django-users?hl=en
-~--~~~~--~~--~--~---

Re: Using multiple databases

[Dan]

> Most ideally we would like to have it so that the application uses DB1
> (defined in the settings.py file) as the main database, but when it's
> down to users, uses DB2.user as the users table.
> Currently we are thinking of using raw sql, but that would only be a
> last resort preferably. And at that point I'd be more scrambled on how
> to use authenticate together with it.
>
>
If you are using MySQL, you can use the federated engine for tables that are
only "symlinks" to real tables in another database but will act as normal
tables when doing regular operations on them.

It might be possible with other databases too, I don't know.

--~--~-~--~~~---~--~~
You received this message because you are subscribed to the Google Groups 
"Django users" group.
To post to this group, send email to django-users@googlegroups.com
To unsubscribe from this group, send email to [EMAIL PROTECTED]
For more options, visit this group at 
http://groups.google.com/group/django-users?hl=en
-~--~~~~--~~--~--~---

Re: using multiple databases

[Ben Ford]

You can use the multi-db branch as is and use it for a different app for
each db if you want as per the instructions. However you'll lose a lot of
the recent functionality from trunk that way. I'd suggest checking out trunk
at r 6100 and then patching against that. Contact me off list and I'll send
you the patch if you want it. Note that I haven't used the patch yet.
Ben

On 18/09/2007, msoulier <[EMAIL PROTECTED]> wrote:
>
>
> On Sep 17, 11:00 pm, "Ben Ford" <[EMAIL PROTECTED]> wrote:
> > Hi Mike,
> > There is a branch that supports multiple databases in the repository.
> It's
> > quite out of date in the SVN repo but Koen put in some stirling work
> over
> > the period of the sprint and produced a patch against trunk at around
> r6100.
>
> Hmm. Looking at the repository, it looks like 0.96 was r4810. Sounds
> like a lot
> was done since then. :)
>
> > Multiple-db support is a feature that is asked for very regularly,
> > unfortunately there have been issues getting the latest changes into the
> > repo so others can use the branch. This is mainly due -as I understand
> it -
> > to quality of the code, lack of working tests, and the fact that the
> core
> > devs are busy on other things. I can send you a copy of the patch if you
> > like, or there's an earlier patch attached to ticket 4747 which is the
> > current version I'm using in production.
>
> Something that could just patch 0.96 would be nice. I don't mind
> trying it out.
>
> > Koen is busy this week I think, but we're probably going to discuss
> > refactoring the multi-db branch to take advantage of recent changes in
> the
> > backend code in the near future.
> > At present multi-db is usable, and as I said I have it in one of my
> projects
> > right now. Having said that, it's quite beta and to get the most out of
> it
> > you're going to have to be pretty happy digging through django's
> internals.
> > If  you are happy doing that we'd love some help with it, as there's
> still a
> > lot to be done! If you want either patch then send me a mail, and of
> course
> > if you have any problem/comments/suggestions I'm more than happy to
> help.
>
> I was hoping to just point each application at a different database,
> nothing more.
> If the patch accomplishes that, then I don't mind looking.
>
> Thanks,
> Mike
>
>
> >
>


-- 
Regards,
Ben Ford
[EMAIL PROTECTED]
+6281317958862

--~--~-~--~~~---~--~~
You received this message because you are subscribed to the Google Groups 
"Django users" group.
To post to this group, send email to django-users@googlegroups.com
To unsubscribe from this group, send email to [EMAIL PROTECTED]
For more options, visit this group at 
http://groups.google.com/group/django-users?hl=en
-~--~~~~--~~--~--~---

Re: using multiple databases

[msoulier]

On Sep 17, 11:00 pm, "Ben Ford" <[EMAIL PROTECTED]> wrote:
> Hi Mike,
> There is a branch that supports multiple databases in the repository. It's
> quite out of date in the SVN repo but Koen put in some stirling work over
> the period of the sprint and produced a patch against trunk at around r6100.

Hmm. Looking at the repository, it looks like 0.96 was r4810. Sounds
like a lot
was done since then. :)

> Multiple-db support is a feature that is asked for very regularly,
> unfortunately there have been issues getting the latest changes into the
> repo so others can use the branch. This is mainly due -as I understand it -
> to quality of the code, lack of working tests, and the fact that the core
> devs are busy on other things. I can send you a copy of the patch if you
> like, or there's an earlier patch attached to ticket 4747 which is the
> current version I'm using in production.

Something that could just patch 0.96 would be nice. I don't mind
trying it out.

> Koen is busy this week I think, but we're probably going to discuss
> refactoring the multi-db branch to take advantage of recent changes in the
> backend code in the near future.
> At present multi-db is usable, and as I said I have it in one of my projects
> right now. Having said that, it's quite beta and to get the most out of it
> you're going to have to be pretty happy digging through django's internals.
> If  you are happy doing that we'd love some help with it, as there's still a
> lot to be done! If you want either patch then send me a mail, and of course
> if you have any problem/comments/suggestions I'm more than happy to help.

I was hoping to just point each application at a different database,
nothing more.
If the patch accomplishes that, then I don't mind looking.

Thanks,
Mike


--~--~-~--~~~---~--~~
You received this message because you are subscribed to the Google Groups 
"Django users" group.
To post to this group, send email to django-users@googlegroups.com
To unsubscribe from this group, send email to [EMAIL PROTECTED]
For more options, visit this group at 
http://groups.google.com/group/django-users?hl=en
-~--~~~~--~~--~--~---

Re: using multiple databases

[Ben Ford]

Hi Mike,
There is a branch that supports multiple databases in the repository. It's
quite out of date in the SVN repo but Koen put in some stirling work over
the period of the sprint and produced a patch against trunk at around r6100.
Multiple-db support is a feature that is asked for very regularly,
unfortunately there have been issues getting the latest changes into the
repo so others can use the branch. This is mainly due -as I understand it -
to quality of the code, lack of working tests, and the fact that the core
devs are busy on other things. I can send you a copy of the patch if you
like, or there's an earlier patch attached to ticket 4747 which is the
current version I'm using in production.
Koen is busy this week I think, but we're probably going to discuss
refactoring the multi-db branch to take advantage of recent changes in the
backend code in the near future.
At present multi-db is usable, and as I said I have it in one of my projects
right now. Having said that, it's quite beta and to get the most out of it
you're going to have to be pretty happy digging through django's internals.
If  you are happy doing that we'd love some help with it, as there's still a
lot to be done! If you want either patch then send me a mail, and of course
if you have any problem/comments/suggestions I'm more than happy to help.
Cheers,
Ben

On 18/09/2007, msoulier <[EMAIL PROTECTED]> wrote:
>
>
> I was hoping to use Django in a web management UI for a server that I
> support, where new UIs are added as new applications are installed.
>
> Due to this plugin requirement, I had planned to model that with one
> large Django project, where each new plugin was a Django application.
> Unfortunately it would appear that this would not work, as each
> application potentially needs its own database, and Django only
> permits a single one to be specified.
>
> In Rails I can specify new dbs at the model level to override the
> default. Is there any way to do this in Django? Surely the requirement
> for more than one database to drive an entire site's content is
> present.
>
> If not, I could use multiple Django projects, with one project per
> plugin, but I would still like to share some common code for inclusion
> tags, templates, etc., to ensure that the pages all have the same look
> and feel. Is there a recommended way to do this?
>
> Thank you for any help that you can offer.
>
> Mike
>
>
> >
>


-- 
Regards,
Ben Ford
[EMAIL PROTECTED]
+628111880346

--~--~-~--~~~---~--~~
You received this message because you are subscribed to the Google Groups 
"Django users" group.
To post to this group, send email to django-users@googlegroups.com
To unsubscribe from this group, send email to [EMAIL PROTECTED]
For more options, visit this group at 
http://groups.google.com/group/django-users?hl=en
-~--~~~~--~~--~--~---