OK then. Here is my concept for 2 small hooks...
Let the backend do it's thing and create the table creation SQL in the normal manner. Right before executing that SQL call a hook function, if present, gets to modify the SQL or change it to None to suppress the SQL call entirely. There is also a second similar hook for index creation. I cannot imagine a more minimal approach than that. If you don't like Meta, maybe these callbacks could be in the model manager, or perhaps a new class, a model representation factory. I kinda like the new class approach as creating that class may provide an opportunity to clean up several aspects of the db backend design which may be generally useful as Django gets extended to handle multiple databases and non-relational databases. But this last thought is really just conjecture based on a cursory look at the code. I may have different ideas after doing a deep dive. --~--~---------~--~----~------------~-------~--~----~ 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?hl=en -~----------~----~----~----~------~----~------~--~---
