On 17-Aug-07, at 6:15 AM, [EMAIL PROTECTED] wrote:
> There seems to be some trickery in updating a model that already has > database entries. There is no trickery involved. One thing people forget is that Django is a framework made up of python, sql, html, css and javascript. It simplifies and makes tasks easier, but in the last analysis, it is still python, sql, html, css and javascript. One of the givens in sql is the necessity of altering database structure after going into production. So far, django devels have not found a safe and sure way of automating the alteration made within a table - although there are several projects to implement schema evolution going. So in this case you do what you would anyway - fall back on sql and do it 'the hard way'. When you make a change within a model, run sqlall before the change, run sqlall after the change, compare the two, create a script to change the table and manually run that. -- regards kg http://lawgon.livejournal.com http://nrcfosshelpline.in/web/ --~--~---------~--~----~------------~-------~--~----~ You received this message because you are subscribed to the Google Groups "Django users" group. To post to this group, send email to django-users@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-users?hl=en -~----------~----~----~----~------~----~------~--~---
