Thanks a lot for your help Malcom.
Malcolm Tredinnick escribió, El 18/08/2008 0:03:
>
> On Sun, 2008-08-17 at 23:51 +0200, MarC wrote:
>> Hi again,
>> I'm still fighting against it and reading related posts in the mailing list
>> archive with no
>> success... Now I just found it won't work eit
Hum... I thought that to be an AutoField it was mandatory that "_id"
would have to be added to the name of the field... Apparently not! :)
Thanks.
Ana
On Aug 9, 6:57 pm, Collin Grady <[EMAIL PROTECTED]> wrote:
> Why did you add _id to your model definition for levelID ? The column
> does not hav
Hum... I thought that to be an AutoField it was mandatory that "_id"
would have to be added to the name of the field... Apparently not! :)
Thanks.
Ana
On Aug 9, 6:57 pm, Collin Grady <[EMAIL PROTECTED]> wrote:
> Why did you add _id to your model definition for levelID ? The column
> does not hav
Why did you add _id to your model definition for levelID ? The column
does not have that.
--~--~-~--~~~---~--~~
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@googl
Hi all,
I'm working with a MySQL legacy DB which was changed.
This was our previous Level table:
+-+---+--+-+-+---+
| Field | Type | Null | Key | Default | Extra |
+-+---+--+-+-+---+
5 matches
Mail list logo