Hello, 2007/4/23, Matt Boersma <[EMAIL PROTECTED]>: [...] > Having the db_tablespace parameter makes at least the models under > your control more self-documenting. But it's not perfect. Here are > the three options I can think of: > - Leave as-is, realizing it helps somewhat
-0, it may lead to false expectations, as Ben Khoo's one. > - Drop the "db_tablespace" and index tablespace keywords altogether to > avoid this confusion +0 > - Add a mechanism for a default global tablespace and global index > tablespace that apply unless overridden in a specific model or column +1, as it seems to accomplish the most of the basic needs with minimal hassle (c) -- Carlo C8E Miron --~--~---------~--~----~------------~-------~--~----~ 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 -~----------~----~----~----~------~----~------~--~---
