>However, I don't like it if it's going to be introduced as a scaling >solution; I'd rather have the various tiers of infrastructure (load >balancing at the front, application in the middle, database in the >back) remain as loosely coupled as possible.
Absolutly, scaling is the last reason to introduce it and is not in anyway why it a such feature gap. As mentioned, there are dozens of scenarios in modern cororations where you have access multiple databases. I could a several tens. Take the company I work at now. We have an ERP system in oracle. The ERP system itself splits its data in 3 seperate instances (SYSTEM/CONTROL/DATA). We then have business intellgence system. We have EDI systems. We have a zillion dodgy access databases. We have home grown maintaince systems. A lot of the requirements for building websites is to show data from multiple of these systems. While this can be done with pure SQL now, it would be nicer if it could done through the ORM because of all the benefits that brings in Django. --~--~---------~--~----~------------~-------~--~----~ 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 -~----------~----~----~----~------~----~------~--~---
