re 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
[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 us
Hi, I'm currently starting a project in django, and there's some data
already in another database.
We're planning to go and use that information (more specifically user
information) in the django application.
However, this forms several problems:
1) There are 2 different databases. A django setti
3 matches
Mail list logo
