On 25/02/2013 2:59pm, laxmikant ratnaparkhi wrote:
Does anybody can answer this?
Try changing your model from FK_Formats = models.ForeignKey(Formats) to ...
FK_Format = models.ForeignKey(Formats)Â Â
... and see what happens to the error.
Mike
Let me know if anything extra is required?
Does anybody can answer this?
Let me know if anything extra is required?
Thanks in advance...
Laxmikant
On Wed, Feb 20, 2013 at 6:23 PM, laxmikant ratnaparkhi
wrote:
> Hello all,
>
> I just run a command to Add foreign key to the existing table. and the
> command was like this:
>
> *ALTER
Can you look at the database in some way and see if FK_Formats_id
actually exists in the table?
If you added that to the model after you had already synced it then
running another syncdb will not create the new field. I would suggest
looking into South which will handle database migrations for yo
I strongly recommend South (http://south.aeracode.org/) for adding new
fields to existing models. As far as I know it is recommended by the Django
core team as well, and they are looking at moving it into Django proper.
On Wednesday, February 20, 2013 6:53:39 AM UTC-6, laxglx wrote:
>
> Hello a
4 matches
Mail list logo