On Thu, Dec 3, 2009 at 12:59 PM, Mario Briggs <mario.bri...@in.ibm.com> wrote: > Russ, > > I dont agree to the *it works* theory here - Ian rightly said 'If you > ask me, > anybody foolish enough to use a TextField as a primary key deserves > what they get' and you agreed 'Your comment about foolishness is > definitely correct '
I can point at countless Django installations that have perfectly functioning admin interfaces. I'm sorry to break this to you, but that means that Django's admin works. Django assumes that it is possible to do a lookup on a TextField. This behavior is implemented and usable on SQLite, Postgres, MySQL and Oracle. Oracle has a slight caveat (4k character limit) on this capability, but that doesn't place any practical limitations on the unconventional way that Django uses TextField in the admin. If the DB2 backend doesn't support lookups on TextFields, then that is a problem with the DB2 backend, not Django. > Putting it in context, this is in the 'user control area' and the fact > that one can go ahead and change the type in the LogEntry definition > like Helgi did means it not a blockade I'm not sure what you mean by "user control area", but if you want to propose manual table modification as a solution to this problem, that's between you and your userbase. > (though it would be good if > Django got i right first time). Django *did* get it right first time. I've already explained why the code is the way it is. *None* of the officially supported Django backends have any problem with this usage. To my reading, this is *entirely* a problem with the DB2 backend. Now, if you want to propose a modification to Django that will make it easier for you to implement the DB2 backend, I'm open to suggestions. I've already made one such suggestion, which based on your reaction, you don't like. Now it's your turn to make a counterproposal. > I have another question though but that is due to my lack of wide > usage of Django - so you mentioned that u were scared to make the > changes becuase of problems with migrations - once Helgi makes that > change and the next time he is upgrading to the a higher version of > Django, is there anything he needs to do ? Once Django has rolled out a table, it doesn't try to recreate or validate that the table is the same at the database level. As long as the database-level table definition is functionally compatible with the model definition, you shouldn't have any problems. 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.
