Simon Willison wrote:
> That sounds smart to me. There are cases where you want to select from > one database and then save to another (moving data between different > database servers, re-sharding data for whatever reason) but the common > case will be as you describe. This means an ORM object should have a > special property on it recording which database connection it was > loaded from. It also presumes we won't ever want to support the case I apologize for my ignorance as to how django DB connections work, but will this lead to thread safety issues if one thread loads an object and passes it into another thread? Or is the underlying Django connection thread safe? Also, what if the connection has closed for whatever reason since the object was loaded (due to DB connection timeout, DB restart, etc)? --~--~---------~--~----~------------~-------~--~----~ You received this message because you are subscribed to the Google Groups "Django developers" group. To post to this group, send email to django-developers@googlegroups.com 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 -~----------~----~----~----~------~----~------~--~---
