Well I managed to get introspectdb working with schemas, but I don't know if it's the right solution. What I'm doing right now is modifying the schema search path.
If you think it's a good idea, I'd probably suggest looking at adding a per project per app setting that specifies a schema. It would need to add the create schema statement during the initsql process. For subsequent accesses, we would set the default search path for the life of connection to match the schema specifed in the settings. Is this worth pursuing? --~--~---------~--~----~------------~-------~--~----~ You received this message because you are subscribed to the Google Groups "Django users" 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-users -~----------~----~----~----~------~----~------~--~---
