Brox ... Nice writeup! Many thanks!
Now for my thoughts... I have been using PyTables as an adjunct datastore along with the Django ORM for almost a year. To me, BigTable looks a lot like PyTables and, as such, I know that it can be be a great supplement to the Django ORM in certain scenarios. GQL may or may not be a great idea, but I certainly don't think that it is a bad idea as I have had similar thoughts when contemplating improving the integration of PyTables and Django. The key to me is multiple database support. Then we can keep the ORM and also develop a OTM (ObjectTableMapper) perhaps targeting GQL and take advantage of both datastorage models. Plug in a GQL front-end to PyTables and much of the anguish of being tied to the GoogleAppEngine starts to disapate. I guess I will have to review the work that has been going on for multiple DB support and see if it needs to be extended to also include support for multiple model mappers. --~--~---------~--~----~------------~-------~--~----~ 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?hl=en -~----------~----~----~----~------~----~------~--~---
