On Feb 23, 8:09 am, "Aidas Bendoraitis" <[EMAIL PROTECTED]> wrote: > I think, you should rather create that field as a separate project, > just as Jannis Leidel did with geoposition > field:http://code.google.com/p/django-coordinatesfield/. > If it is useful to others as well as to you, maybe somebody will add > it to the core. >
mmhh, good idea. > Also personally I think that a custom validator is enough for such a > restriction that you need. And it would be much more important to > implement BLOB fields for saving binary files in the database. > Could be, however if IntegerField was enough why PositiveIntegerField() and others was developed? Also, is a custom validator able to generate SQL code for check constraints. IMO, there's nothing better to leave the database handle those things. Regards! > --~--~---------~--~----~------------~-------~--~----~ You received this message because you are subscribed to the Google Groups "Django developers" group. To post to this group, send email to django-developers@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-developers?hl=en -~----------~----~----~----~------~----~------~--~---
