Hi, I have been using the Oracle branch now for a few months and it is looking really good.
I have a question regarding the use of the 'db_tablespace' option in the Meta class. I am able to set this option within my application and successfully perform a syncdb that will place all my tables in the correct tablespace. The question/issue that I am having is that I cannot see a way of instructing any other application (such as authentication) to also create its tables in the tablespace of my choosing. To my understanding the application will either create its tables in the tablespace specified in its own models.py or it create its tables in whatever the default tablespace happens to be. This results in tables being created in several different tablespaces. For my 2c worth, if this cannot already be done by the current Oracle database framework, I think that would be a beneficial addition if only to provide completeness to the option to assign tablespaces. Regards Ben Khoo On Apr 21, 1:54 am, Matt Boersma <[EMAIL PROTECTED]> wrote: > Ben Khoo already found a good bug (#4093) that we fixed, and in the > process we found a problem we'd created for Postgres that wasn't > caught by any of the tests. So we fixed that and added a "datatypes" > test to modeltests. > > So there is a slightly newer patch available > now:http://code.djangoproject.com/attachment/wiki/OracleBranch/django-ora... > > We'll try not to do this again so people can focus on the content of > the patch for a bit, but these two things needed to be fixed ASAP. If > you're testing the boulder-oracle-sprint branch directly, please > update. > > Matt > > On Apr 20, 10:03 am, "Adrian Holovaty" <[EMAIL PROTECTED]> wrote: > > > On 4/19/07, Matt Boersma <[EMAIL PROTECTED]> wrote: > > > > The "boulder-oracle-sprint" branch is ready to come home. > > > Congrats, guys! Thanks to all of you for your hard work. I'm +1 for > > merging it, too, once we've taken a look at it. > > > Let's organize the merge process. Malcolm, since you've been dealing > > with query.py and other databasey parts of Django, do you want to take > > the lead on the merge? Or Jacob? I could get to it next week if you > > guys are busy. > > > Adrian > > > -- > > Adrian Holovaty > > holovaty.com | djangoproject.com --~--~---------~--~----~------------~-------~--~----~ 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 -~----------~----~----~----~------~----~------~--~---
