Thanks! On Wed, May 26, 2010 at 5:32 AM, Daniel Roseman <[email protected]>wrote:
> On May 25, 10:49 pm, Jonathan Hayward > <[email protected]> wrote: > > For CharField, EmailField, URLField, etc., is VARCHAR implementation > > (meaning a fixed limit on length) absolutely non-negotiable, or there a > way > > to make e.g. a CharField that won't truncate if you cross some arbitrary > > length? > > > > (If you don't specify a length, does it assign a default length, or use > TEXT > > instead of VARCHAR so that a field of indefinite length is accommodated, > > resources permitting?) > > EmailField is a subclass of CharField, so it always uses a varchar. As > the documentation notes, the default length if you don't specify one > is 75. > > If you really want an email field based on TEXT, you could subclass > EmailField with a get_internal_type method that returns 'TextField'. > -- > DR. > > -- > You received this message because you are subscribed to the Google Groups > "Django users" group. > To post to this group, send email to [email protected]. > To unsubscribe from this group, send email to > [email protected]<django-users%[email protected]> > . > For more options, visit this group at > http://groups.google.com/group/django-users?hl=en. > > -- → Jonathan Hayward, [email protected] → An Orthodox Christian author: theology, literature, et cetera. → My award-winning collection is available for free reading online: ☩ I invite you to visit my main site at http://JonathansCorner.com/ -- You received this message because you are subscribed to the Google Groups "Django users" group. To post to this group, send email to [email protected]. To unsubscribe from this group, send email to [email protected]. For more options, visit this group at http://groups.google.com/group/django-users?hl=en.
