Hi all. I agree with Benjamin completely. I hate Identity Map and synchronization approach. They break database logic like trigger or view.
2007/2/5, Benjamin Slavin <[EMAIL PROTECTED]>: > > I've also given this some consideration -- I haven't found any > information on this either. > > It would be nice if the DB API could make use of the cache system > (memcached) if you attempt the lookup by ID. Synchronization becomes > more of a problem... and it certainly removes transactional safety > from the system if implemented improperly. > > Anyone have any experience with this sort of setup under Django? > > - Ben > > > On 2/2/07, Sergey Kirillov <[EMAIL PROTECTED]> wrote: > > > > Greetings, > > > > I'd like to ask, why Django ORM has no concept of Identity Map? It is > > strange for me that if I call get() five times I will get five object > > instances, instead of five references to a single instance. > > > > Was it a design decision? I'm unable to find any discussions of this. > > Or I'm the first one who asks about this? > > > > > > > > > > > > > --~--~---------~--~----~------------~-------~--~----~ 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 -~----------~----~----~----~------~----~------~--~---
