I was too harsh on the GenericKeyField. How about GenericKeyField
(length=x). I think the reason i put length in there is obvious, but i
can explain if need be.

In post #14 on this thread you suggested - " I'm not wild about the
idea of having underlying datatypes change based on attributes in a
field definition. To date, Django has maintained a clear mapping
between Field type and database type."

I am not suggesting that backends change the type in the DB based on
the 'length'. They should use 1 fixed type for GenericKeyField

regards
Mario




--

You received this message because you are subscribed to the Google Groups 
"Django developers" group.
To post to this group, send email to django-develop...@googlegroups.com.
To unsubscribe from this group, send email to 
django-developers+unsubscr...@googlegroups.com.
For more options, visit this group at 
http://groups.google.com/group/django-developers?hl=en.


Reply via email to