On Fri, 2007-06-08 at 15:27 +0000, [EMAIL PROTECTED] wrote:
> Right...I understand that.... although, based on information from
> another post (yesterday I believe) I don't think that is working right
> now, unless the poster was doing something incorrectly... he hasn't
> answered my reply, so I'm not sure as of yet.
> 
> But in the case that one was using the same database backend, it would
> be nice to be able to do this, and in the case that all of the
> databases were on the same mysql server, and had the same login
> credentials, it would most likely  work in the trunk too if all of the
> fields were fully qualified ... I'm not saying they'd want to
> officially support it or anything... it was just something I had
> thought about and figured I'd mention.

Absolutely, Carole. By all means use it when it's available and that's
quite probably a good strategy to investigate when constructing queries.
I was wanting to highlight that your idea of just including
db.tablename.columnname for every field was not the easy fix it seems to
be (and actually loses information, because you need to know the type of
the backend at the time you construct the query, not just the db+table
+column name tuple). You will still have to do some organisation prior
to creating the query in the general case.

By the way, cross-database single query support is only fairly minimal
in PostgreSQL (and not at all in SQLite). This is actually a PostgreSQL
FAQ because people migrating from MySQL want it. So although it's
something to exploit when using MySQL, multi-db code has to be based on
alternative measures as it's primary means, even for single backend
cases.

Regards,
Malcolm




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

Reply via email to