Re: question about changing model/table names and attributes ... (still learnin')

[Guy]

Thanks, for the advice.  I am checking it out.To clarify, my table
names have changed when I realize styling erros have been
incorporated, (ie. capitalization errors, etc). I wouldn't expect
the table names to change in the operational db.

Thanks again.
Guy

On Dec 10, 12:32 pm, Shawn Milochik  wrote:
> The current best tool for this is South:http://south.aeracode.org/
>
> You can do complicated data and database migrations smoothly, with the 
> ability to roll-back changes.
> I don't know why you mention changing table names, since that should never be 
> necessary. But anything is possible.
>
> If you're doing "major" changes, defined (by me) as creating a new thing 
> (field or table, A.K.A. attribute or model), moving data out of an existing 
> thing into it, then deleting the original thing, you'll want to carefully 
> read and understand South's excellent strategy for doing 
> this;http://south.aeracode.org/wiki/Tutorial3
>
> All your normal stuff, such as adding attributes to models, changing 
> properties (required or not, default values, and so on) are a piece of cake 
> with South.
>
> Shawn

--

You received this message because you are subscribed to the Google Groups 
"Django users" group.
To post to this group, send email to django-us...@googlegroups.com.
To unsubscribe from this group, send email to 
django-users+unsubscr...@googlegroups.com.
For more options, visit this group at 
http://groups.google.com/group/django-users?hl=en.

Re: question about changing model/table names and attributes ... (still learnin')

[Shawn Milochik]

The current best tool for this is South: http://south.aeracode.org/

You can do complicated data and database migrations smoothly, with the ability 
to roll-back changes.
I don't know why you mention changing table names, since that should never be 
necessary. But anything is possible.

If you're doing "major" changes, defined (by me) as creating a new thing (field 
or table, A.K.A. attribute or model), moving data out of an existing thing into 
it, then deleting the original thing, you'll want to carefully read and 
understand South's excellent strategy for doing this;
http://south.aeracode.org/wiki/Tutorial3

All your normal stuff, such as adding attributes to models, changing properties 
(required or not, default values, and so on) are a piece of cake with South.

Shawn


--

You received this message because you are subscribed to the Google Groups 
"Django users" group.
To post to this group, send email to django-us...@googlegroups.com.
To unsubscribe from this group, send email to 
django-users+unsubscr...@googlegroups.com.
For more options, visit this group at 
http://groups.google.com/group/django-users?hl=en.

question about changing model/table names and attributes ... (still learnin')

[Guy]

What is the "best practice" for editing table names or attributes
after they have been established by manage.py syncdb?

Since I am in the very early stages, I either delete the database and
create a new one with syncdb, or manually change the table names (I
generally use the SQLite manager plugin for firefox to assist with the
SQL).

Is there a better way of doing this?  Destroying the database and
building a new one works now when I only have some test entries, but I
am concerned that this would be impractical once my db is fully
populated with real data. Likewise, I want to be careful when editing
tables that contain valuable data.

Can someone point me to a good write-up of this process, or good
software?

Go easy on me, I spent my education in biology and am just getting
started trying to understand silicon rather than carbon based systems.

Thanks.
Guy

--

You received this message because you are subscribed to the Google Groups 
"Django users" group.
To post to this group, send email to django-us...@googlegroups.com.
To unsubscribe from this group, send email to 
django-users+unsubscr...@googlegroups.com.
For more options, visit this group at 
http://groups.google.com/group/django-users?hl=en.