>a.) connect to multiple databases: ex. Legacy database A and new
>database B for a single application ?
Even though magic-removal doesn't address this directly, there is a lot
of what is done in magic-removal that will make this possible in the
future. The main thing is the concept of managers,
It looks like magic-removal doesn't allow more than one database
connection 'out of the box', but I guess you could use a view that has
something like;
import MySQLdb
result = curs.fetchall()
in it and carry on from there, with judicious use of
result['fieldname'] in the newobj.save() argum
On 1/31/06, [EMAIL PROTECTED] <[EMAIL PROTECTED]> wrote:
> Sorry if these are just rehash questions, I wasn't able to find the
> ansewers on the DJ site. Proabably user error :)
A full list of the changes being made in the magic-removal branch is
online here:
http://code.djangoproject.com/wiki/
All,
After the magic removal, will it be possible to:
a.) connect to multiple databases: ex. Legacy database A and new
database B for a single application ?
b.) Be more specific when defining data types in the model: ex.
using big-serial rather than serial for the primary key?
Sorry if
4 matches
Mail list logo
