Re: [Django] #9349: CharField create a varchar column

[Django]

#9349: CharField create a varchar column
---+
  Reporter:  aiev  | Owner:  nobody 
  
Status:  closed| Milestone: 
  
 Component:  Database layer (models, ORM)  |   Version:  SVN
  
Resolution:  wontfix   |  Keywords:  char, 
varchar
 Stage:  Unreviewed| Has_patch:  0  
  
Needs_docs:  0 |   Needs_tests:  0  
  
Needs_better_patch:  0 |  
---+
Changes (by mtredinnick):

  * status:  new => closed
  * needs_better_patch:  => 0
  * resolution:  => wontfix
  * needs_tests:  => 0
  * needs_docs:  => 0

Comment:

 If you really need a `char` type at the database level, then you can write
 a custom model field that does that (it's documented how to write custom
 fields). This isn't needed in Django core, however, since the number of
 cases where you really need a fixed-length field right-padded with spaces
 is very minimal. The `varchar` type can handle all those cases (possible,
 again, with a custom model field if you really want the right-padding).

-- 
Ticket URL: 
Django 
The Web framework for perfectionists with deadlines.
--~--~-~--~~~---~--~~
You received this message because you are subscribed to the Google Groups 
"Django updates" group.
To post to this group, send email to django-updates@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-updates?hl=en
-~--~~~~--~~--~--~---

[Django] #9349: CharField create a varchar column

[Django]

#9349: CharField create a varchar column
--+-
 Reporter:  aiev  |   Owner:  nobody
   Status:  new   |   Milestone:
Component:  Database layer (models, ORM)  | Version:  SVN   
 Keywords:  char, varchar |   Stage:  Unreviewed
Has_patch:  0 |  
--+-
 I know that in most situations we have to use an varchar column, but not
 always!

 CharField intuitively mean an char column.
 The semantics of my database is wrong when I need to create a column of
 type char unless I change it directly in the database, but its not
 elegant.

 An FixedCharField (or something else) could resolve it. :/
 This is a small detail, sorry if this has no importance

 Regards

-- 
Ticket URL: 
Django 
The Web framework for perfectionists with deadlines.
--~--~-~--~~~---~--~~
You received this message because you are subscribed to the Google Groups 
"Django updates" group.
To post to this group, send email to django-updates@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-updates?hl=en
-~--~~~~--~~--~--~---