On 2/20/06, Ian Holsman <[EMAIL PROTECTED]> wrote:
>
> I'm not sure what they were designed for, but I make use of both of
> these heavily.
>
> I use the content-types to make generic tables which can hold
> references to several tables in a single spot.
In models, it also supplies get_app(app_la
I'm not sure what they were designed for, but I make use of both of
these heavily.
I use the content-types to make generic tables which can hold
references to several tables in a single spot.
for example, the comment table uses content-type so that you can
easily add comments to any other model/
I don't understand much about Package and ContentType model, can
someone explain it for me? Thanks.
I see that they are used to restoring app_label and model_name. Why we
need this? If are they used for models outside the current project?
--
I like python!
My Blog: http://www.donews.net/limodou
I plan on making a migration solution after Magic-Removal trunks. I
have a partial-solution now, but I don't want to work on it just to
need to redo everything afterwords.
On 2/19/06, Ken Kennedy <[EMAIL PROTECTED]> wrote:
>
> I have to concur with Max here. I know it sounds like a pain to migra
I have to concur with Max here. I know it sounds like a pain to migrate
schema changes BY HAND...but trust me, the tools don't help that much.
I'm a DBA in my day job (MS SQL, Oracle, and Postgresql primarily), and
the majority of the problems that occur when developers are trying to
do applicatio
xamdam wrote:
> No, I am talking about altering the DB schema of your app. (I started
> off withthe noMagic branch, so there is nothing to migrate)
Right now there is no automatic way to do schema migration, as it's a
very serious thing to do (ie, do you want an automatic tool potentially
destr
Nice, thanks!
--~--~-~--~~~---~--~~
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 P
When working with and troubleshooting forms, it can be a common
mistake to have a particular field be required yet not present in the
form. Currently, such a case will lead to a "please correct the
error(s) below" message without those errors in question actually
being displayed, as the errors are
On 19/02/06, xamdam <[EMAIL PROTECTED]> wrote:
>
> Django models can already be manipulated outside of the web app with
> manage.py shell
> I am looking for a way to have a regular python script (say, running a
> batch job) use the model classes. It seems like I just have to import
> the right stuf
Django models can already be manipulated outside of the web app with
manage.py shell
I am looking for a way to have a regular python script (say, running a
batch job) use the model classes. It seems like I just have to import
the right stuff (which 'shell' option does automagically), but I
haven't
No, I am talking about altering the DB schema of your app. (I started
off withthe noMagic branch, so there is nothing to migrate)
--~--~-~--~~~---~--~~
You received this message because you are subscribed to the Google Groups
"Django developers" group.
To post to
I assume here you're referring to the schema alterations associated with the next version of Django? If that's the case, follow the magical link: http://code.djangoproject.com/wiki/RemovingTheMagic
On 2/19/06, xamdam <[EMAIL PROTECTED]> wrote:
I have not found anything in the docs about this (DB m
I have not found anything in the docs about this (DB migration), and
searching this group yields only two measly irrelevant results (which
freaks me out).
What's the current suggested approach for changing the DB schema with
django? What are the best practices for handling migrations without
loos
13 matches
Mail list logo
