Re: Model Codng/Model Usage Pitfall?

Thanks. I'll look into them. On Feb 14, 1:55 pm, Xavier Ordoquy wrote: > Hi > > You have several options depending on what you're ready to do. > > 1) Drop the database, recreate it and resync it (fine as long as you don't > have data to keep) > 2) Install django command

Re: Model Codng/Model Usage Pitfall?

Hi You have several options depending on what you're ready to do. 1) Drop the database, recreate it and resync it (fine as long as you don't have data to keep) 2) Install django command extension (http://code.google.com/p/django-command-extensions/) and take sqldiff output to modify your DB

Re: Model Codng/Model Usage Pitfall?

I think you're right. So how do I update the table manually, or maybe a better question is how do I completely delete it and then put it back the way I need to have? Can you point me to somewhere in the documenation for where to find this, or can you give me a step by step process for how to keep

Re: Model Codng/Model Usage Pitfall?

On Monday, February 14, 2011 09:25:58 am Tom Evans wrote: > Django does not take care of maintaining the structure of your tables. > If you change your model definition to add a new attribute, django > will not update your database to add the new column to your table, you > must do it manually. >

Re: Model Codng/Model Usage Pitfall?

On Mon, Feb 14, 2011 at 5:34 PM, hank23 wrote: > OK. I will change it to an EmailField and see if that helps. However I > have a further question. When making changes like this to existing > tables, do I always need to run the syncdb command to make sure that > everything

Re: Model Codng/Model Usage Pitfall?

On Mon, Feb 14, 2011 at 5:28 PM, wrote: > Tom, > > How does he do that? > Sent from my BlackBerry wireless device from MTN > Follow the instructions in the fine manual for the chosen DB engine. For example, in MySQL, you would do something like this: > $ python

Re: Model Codng/Model Usage Pitfall?

users@googlegroups.com> > Reply-To: django-users@googlegroups.com > Subject: Re: Model Codng/Model Usage Pitfall? > > On Mon, Feb 14, 2011 at 5:21 PM, hank23 <hversem...@stchas.edu> wrote: > > I have coded a table which looks like this: > > > class Comme

Re: Model Codng/Model Usage Pitfall?

legroups.com Subject: Re: Model Codng/Model Usage Pitfall? On Mon, Feb 14, 2011 at 5:21 PM, hank23 <hversem...@stchas.edu> wrote: > I have coded a table which looks like this: > > class Comment(models.Model): >    title = models.CharField(max_length=1,choices=TITLE_CHOICES) >

Re: Model Codng/Model Usage Pitfall?

Model Codng/Model Usage Pitfall? I have coded a table which looks like this: class Comment(models.Model): title = models.CharField(max_length=1,choices=TITLE_CHOICES) firstname = models.CharField(max_length=15) lastname = models.CharField(max_length=25) commenttext = models.CharFiel

Re: Model Codng/Model Usage Pitfall?

On Mon, Feb 14, 2011 at 5:21 PM, hank23 wrote: > I have coded a table which looks like this: > > class Comment(models.Model): >    title = models.CharField(max_length=1,choices=TITLE_CHOICES) >    firstname = models.CharField(max_length=15) >    lastname =

Model Codng/Model Usage Pitfall?

I have coded a table which looks like this: class Comment(models.Model): title = models.CharField(max_length=1,choices=TITLE_CHOICES) firstname = models.CharField(max_length=15) lastname = models.CharField(max_length=25) commenttext = models.CharField(max_length=500)