> Obviously the Django field types provide more semantics than the basic > database datatypes. Thus I assume that whenever there is a new type of > field which does not fit in the given categories, it is a good idea to > define such a new datatype. Correct?
most likely. > Example: I would like to model an ISIN code. The ISIN code is a 12- > character alpha-numerical code for financial instruments, like stocks, > bonds, etc with an internal structure including a check-digit. Now I > can model it with > isin = models.CharField(maxlength=12) > but I would prefer something like > isin = mymodels.IsinNumber() > because I would assume that then I can define the db types, the > widgets and standard validators. > > Can someone point me in the right direction? If you're running the bleedin' edge SVN version, this has been made considerably easier: http://www.djangoproject.com/documentation/model-api/#custom-field-types The above instructions show you exactly what you need to override. -tim --~--~---------~--~----~------------~-------~--~----~ 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 -~----------~----~----~----~------~----~------~--~---
