I was using the same shell. I also tried shutting down the server,
rebooting the machine and opening everything up again to see if that
would make any difference but it did not.
However, then a few hours later - it started to work again. I still
don't fully understand the reason. I can only
On 3/20/07, Merric Mercer <[EMAIL PROTECTED]> wrote:
>
> Another observation after more investigation.
>
> I decided to do the following:-
>
> 1. Drop the table (again) from the DB.
> 2. Alter the Model in Django. This time I deleted one of the original
> fields named "rrp".
>
> Then:-
>
> 1. I
Another observation after more investigation.
I decided to do the following:-
1. Drop the table (again) from the DB.
2. Alter the Model in Django. This time I deleted one of the original
fields named "rrp".
Then:-
1. I re-ran syncdb. This confirmed the creating of a new table in the db
2.
This is a follow on from my previous email. Things have got even
stranger and unpredicable.
I dropped the table from the database and then ran syncdb to re-create
a completely new and empty db. However I STILL
cannot get the new fields to be recognized. All the previous fields
are available.
When I want to add a new field to a database, with existing data, I
normally don't have a problem as long as I follow these steps.
1. Alter the django model.
2. Manually adjust the database table ( mySQL)
3. Run syncdb
However, I used these steps this morning and it has not worked. The new
5 matches
Mail list logo