On Tue, Nov 24, 2009 at 1:07 PM, Mario Briggs <mario.bri...@in.ibm.com> wrote: >>> > What is stored in this field is a string-serialized representation of > the > primary key value. > << > > I agree that INTEGER is not the right choice, but then so too is CLOB. > How long is this string-serialized representation going to be? greater > than 4000 characters ? Varchar(X) where X is > 4000 or something is > then the right choice. This is validated by what Karen says is the > Oracle fix.
Well, Django doesn't make the decision to use CLOB - that's in the hands of your backend. In the same circumstances, SQLite and Postgres use 'text'. MySQL uses 'longtext'. Oracle uses 'NCLOB' In theory, the contents of the object_id field could be anything - including a string of arbitrary length (i.e., a TextField). However, in practice, I would be surprised to see 4000+ characters for object_id - most primary keys are going to be integers, and the ones that aren't are likely to be short strings or string-like datatypes. I can't comment on what would be an appropriate datatype for DB2 in this context. Yours, Russ Magee %-) -- You received this message because you are subscribed to the Google Groups "Django developers" group. To post to this group, send email to django-develop...@googlegroups.com. To unsubscribe from this group, send email to django-developers+unsubscr...@googlegroups.com. For more options, visit this group at http://groups.google.com/group/django-developers?hl=en.
