thanks, I´ll check out the different possibilities.
Am 23.06.2006 um 22:07 schrieb Jacob Kaplan-Moss:
>
> On Jun 23, 2006, at 2:44 PM, patrickk wrote:
>> another reason for splitting databases:
>> we have several websites sharing the same userdata (so that users
>> only have to register once). w
On Jun 23, 2006, at 12:39 PM, Jacob Kaplan-Moss wrote:
>
> On Jun 23, 2006, at 11:51 AM, sean wrote:
>> The only reason I wanted to split the db in the first place is that I
>> don't really like the thought of having the application data (like
>> auth, flatpages etc.) and the production database
On Jun 23, 2006, at 2:44 PM, patrickk wrote:
> another reason for splitting databases:
> we have several websites sharing the same userdata (so that users
> only have to register once). with every app having about 300 tables,
> one database may not be the right decision.
>
> any ideas on how to so
another reason for splitting databases:
we have several websites sharing the same userdata (so that users
only have to register once). with every app having about 300 tables,
one database may not be the right decision.
any ideas on how to solve this?
thanks,
patrick
Am 23.06.2006 um 21:39 s
On Jun 23, 2006, at 11:51 AM, sean wrote:
> The only reason I wanted to split the db in the first place is that I
> don't really like the thought of having the application data (like
> auth, flatpages etc.) and the production database (which is also
> accessed by other applications) in one db. I g
This sounds interesting.
The only reason I wanted to split the db in the first place is that I
don't really like the thought of having the application data (like
auth, flatpages etc.) and the production database (which is also
accessed by other applications) in one db. I guess a few extra columns
Jason Pellerin is currently working on multi database support, is this
the sort of thing you need?
http://code.djangoproject.com/wiki/MultipleDatabaseSupport
Jay P.
--~--~-~--~~~---~--~~
You received this message because you are subscribed to the Google Groups
"D
This is not quite precise. I use two different databases on a single
installation. In fact, using the virtual hosting capability of apache
and modpython, I have one set of Django applications uses a PostgreSQL
database and an entirely different set of Django applications that use
a MySQL database.
On 6/23/06, sean <[EMAIL PROTECTED]> wrote:
> Ok.
> Thanks for the quick reply.
Since you seem to be particularly worried about the auth system, you
might want to either
A) take a look at how the auth system salts and hashes the stored
passwords and controls access to the user system.
B) take a
Ok.
Thanks for the quick reply.
--~--~-~--~~~---~--~~
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
On 6/23/06, sean <[EMAIL PROTECTED]> wrote:
> I was wondering if django provides the possibility to split up the
> database. I don't feel comfortable with having all the auth tables, the
> flatpages, the comment system and such in the same db as the content.
> Maybe it's as easy as overwriting the
11 matches
Mail list logo
