Hello Michael: > alter table in_wrong_place move tablespace new_tablespace; > alter index in_wrong_place_ix rebuild tablespace new_index_tablespace; > In my office for example, politics and procedures indicate that before creating Oracle tables, I must coordinate with DBA about the definition of tablespaces and sizes. There is a clear separation between data and indexes at the tablespace level. During the creation of the tables and indexes, I must clearly define where to put tables and where to put indexes. No "alters" is allowed in this phase, it is seen as a lack of planning.
> In summary: while a tweakable setting for the default tablespace > initially sounds like a good idea it duplicates functionality already > present in Oracle (the users default tablespace) without adding much > in the way of value. IMHO this should not hold up a merge (and > therefore more widespread testing). > Personally, I am doing some testings. The nice Django project for Oracle is in this phase also. All is working well for me by the moment. The only trouble I have (scope trouble) is with the interfase cx_Oracle which, by now, does not support Unicode and Decimals but, with the help of this helpful group I adapted some tricks. Regards. --~--~---------~--~----~------------~-------~--~----~ 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 -~----------~----~----~----~------~----~------~--~---
