Hi Matt, I can see where you are going regarding the manual "massaging" of "sqlall" output to create the database tables. My primary reason for the post was to ensure that I did not miss a piece of documentation showing how the tablespace could be set for other applications.
To clear up potential misconceptions, I am most certainly not an Oracle DBA. Far from it. I am merely a lowly programmer who is currently working with Django. For the moment, I have worked around the issue of tables appearing in different tablespaces by creating an Oracle user configured to use a specific default tablespace which is the same as the db_tablespace. This means that for applications like auth where the db_tablespace is not specified, Oracle will create the table in my configured default tablespace. All of this of course happens at the user creation level in Oracle and makes the explicit setting of the db_tablespace option redundant. In my personal opinion (that I encourage those with higher powers to overrule as required) I think that it is leaving the db_tablespace option "as is" would be completely acceptable with the addition of a note to prevent misconceptions like mine. The only disadvantage that I can see with this path is that this option is a "halfway solution" as you put it and only applies to Oracle. This may lead to a longer term cluttering of the Django API for limited gain. Ben --~--~---------~--~----~------------~-------~--~----~ You received this message because you are subscribed to the Google Groups "Django developers" 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-developers?hl=en -~----------~----~----~----~------~----~------~--~---
