On Mon, Apr 15, 2013 at 1:51 AM, VernonCole <[email protected]> wrote:
> So -- is it worth my time to muck with direct database api support of uuid > fields? > Add the support. Each database backend defines the mapping for the core model field types (see DatabaseCreation.data_types) and any non-standard model fields can define their own mapping by overriding Field.db_type(). The app django-uuidfield [1] allows postgres to store UUIDs as it's uuid type and translates it to a hex string for the Django side of things. You could easily mimic the behavior or keep it as a UUID from end-to-end. If/when Django adds UUIDField to the core field types, each backend can define the appropriate column type (BINARY(16), CHAR(32), uuid, UNIQUEIDENTIFIER, etc). [1] https://github.com/dcramer/django-uuidfield/blob/master/uuidfield/fields.py Regards, Michael Manfre -- You received this message because you are subscribed to the Google Groups "Django developers" group. To unsubscribe from this group and stop receiving emails from it, send an email to [email protected]. To post to this group, send email to [email protected]. Visit this group at http://groups.google.com/group/django-developers?hl=en. For more options, visit https://groups.google.com/groups/opt_out.
