Hi Malcolm, Malcolm Tredinnick wrote: > On Mon, 2006-07-17 at 12:15 +0200, Geert Vanderkelen wrote: >> A follow-up on my previous post, with a patch attached to make the >> db_table_options work, which was easy to put in. >> >> Any comments on this patch, or something I looked over? Otherwise I make a >> feature request with it, unless I missed it while searching for an existing >> one.. > > I'm not too familiar with how the different engines interact with MySQL, > but does using a different engine imply using a different db connection? > If so, is this something that would work reasonably seamlessly on top of > J Pellerin's multi-database Summer of Code work (different engines => > different connections => essentially different database for that model, > so it falls out of his configuration changes)?
MySQL storage engines can interact with each other of course. You can join a MyISAM, InnoDB, Cluster, MERGE, MEMORY, etc, with each other in one query. No need for different connections at all. This is not only for MySQL, it's for most other backends as well. -- Geert Vanderkelen http://some-abstract-type.com --~--~---------~--~----~------------~-------~--~----~ 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 -~----------~----~----~----~------~----~------~--~---
