On 4/4/07, Max Derkachev <[EMAIL PROTECTED]> wrote: > That's not a problem. The API lookup can be easily emulated in custom > class. The problem is that it tries to load the profile from django's > internal models cache, and that can't be easily emulated. One needs to > cheat django the hard way for this task to be completed for a foreign > object.
If you're already going to write a custom class to emulate a Django DB lookup, why not instead write a two-line shortcut that takes a Django auth.User object (or an attribute of one, like username or email address) and does the lookup? I can't speak for anyone else, but I'm OK with that solution -- it's less work for the user of a third-party system than what you seem to be proposing (which requires them to write custom adapter classes and emulate APIs and do all sorts of other stuff). -- "Bureaucrat Conrad, you are technically correct -- the best kind of correct." --~--~---------~--~----~------------~-------~--~----~ 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 -~----------~----~----~----~------~----~------~--~---
