The last time we discussed this [1] I think everyone sort of concluded that a binary field was a sensible idea as long as it's PRIMARILY for storing small chunks of binary info, and not an easy-I-want-to-store- binaries-in-my-database type of thing.
>From memory, most of the issues in that discussion have been rounded up and sort-of dealt with in #2417 [2]. Someone (a BDFL-type) needs to look over that and work out what we want in Django, and someone else needs to champion the issue. 2417 certainly needs to be updated to include things like Oracle, and needs tests. Aside: can we make it easy for people to make their own field types? There's a lot of tickets out there with all sorts of weird and wonderful field things that we probably don't need to add to Django, but if people know how to customise them, then they can do what they want. --Simon G. [1] http://groups.google.com/group/django-developers/browse_thread/thread/266565a23b765ea2 [2] http://code.djangoproject.com/ticket/2417 --~--~---------~--~----~------------~-------~--~----~ You received this message because you are subscribed to the Google Groups "Django developers" 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-developers?hl=en -~----------~----~----~----~------~----~------~--~---
