#7785: Add note about the requirement of integer primary keys in generic
relations
------------------------------------+---------------------------------------
Reporter: Rudolph | Owner: nobody
Status: new | Milestone:
Component: Documentation | Version: SVN
Resolution: | Keywords:
Stage: Unreviewed | Has_patch: 0
Needs_docs: 0 | Needs_tests: 0
Needs_better_patch: 0 |
------------------------------------+---------------------------------------
Changes (by charmless):
* needs_better_patch: => 0
* needs_tests: => 0
* needs_docs: => 0
Comment:
I've been using non-integer primary keys with my generic relations just
fine. In fact, with Postgres 8.2 (but not 8.3), integers are converted to
strings, so I can have my relations reference models with both string and
integer primary keys. I have no idea about dates. This mixing is a
Postgres 8.2-specific 'hack', but there's nothing standing in the way of
heterogeneous non-integer primary keys for generic relations.
So I'm a bit confused and worried regarding what this ticket is about.
--
Ticket URL: <http://code.djangoproject.com/ticket/7785#comment:1>
Django Code <http://code.djangoproject.com/>
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 [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-updates?hl=en
-~----------~----~----~----~------~----~------~--~---
