Well, the problem here is that, generally, ForeignKeys across multiple
databases isn't possible, and so I'm not likely to support it soon.
South's multiple database support is limited at best at the moment, and
this is only possible using MySQL with both databases the same host, so
there's other more pressing issues we need to solve first.
Andrew
I guess this could be done at the South level (if someone created a
patch for it), but as Andrew says, it is not high priority, so it
might be easier to fix it in your migration instead.
--
Sindre
I'm... very impressed they're working at the Django level. I'll have to
look into it (there must be a whole new, inefficient query-running
system for those - cross-database joins are one of the most inefficient
operations ever).
Still, considering I've never heard of this before, and because it's a
really, really crazy schema, it's still low priority. As Sindre says,
just make the raw field types either end rather than a ForeignKey field
type for now.
Andrew