Thx for the feedback guys. I agree that this problem is pretty fundamental. I don't know what worries me more, the fact that the problem exists or the architects don't see the problem.
I think in my case I can isolate the offending code and use some form of "double-buffering" technique to solve it. But, it's not going to be pretty. I've considered SqlObjects, but then I would perhaps just cut over to TurboGears. A colleague has recommended SqlAlchemy. I'll look at both. Cheers, Zeb --~--~---------~--~----~------------~-------~--~----~ You received this message because you are subscribed to the Google Groups "Django users" group. To post to this group, send email to django-users@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-users -~----------~----~----~----~------~----~------~--~---
