Glenn Tenney wrote: > As a friend of mine reminded me, part of your perception feeding that > conception is that you're still thinking of these as being columns in > a table... when in fact they are classes derived from FormField (and > you can derive your own classes from FormField or even from other > field types).
I think you didn't understood me... Classes from django.forms are derived from django.forms.FormField, but classes in django.db.models.fields aren't. They are derived from django.db.models.fields.Field, and they are conceptually different but still haveing the same naming convention *Field... I was just talking about naming convetion. It doesn't metter if they are columns in tables or pigeons on trees :) (IntegerColumn... was just a dumb suggestion) I was taling about them beeing apples and pears but still beeing named same... Sorry, for continuing closed topic :( I'll get used to Django... Eventually... :) --~--~---------~--~----~------------~-------~--~----~ 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 -~----------~----~----~----~------~----~------~--~---
