On Mon, Feb 8, 2010 at 5:31 PM, Luc Saffre <luc.saf...@gmx.net> wrote:
> [snip] Okay, it's obvious that Luke's and Luc's understandings of that problem > are quite different. We both explained our points of views. The next > step would be to hear other people's opinions. > I agree with Luke. I'm also puzzled by your resistance to utilizing the field with _id appended to access the "empty" value in cases where you don't want to deal with the possibility of a DoesNotExist exception. That field, the one with _id on the end, is the direct map to a column in the database. The other is a convenience for accessing the entire model instance that is the representation of a row from another table. If that row doesn't exist, it makes sense to me that attempting to access it, whenever, raises DoesNotExist. > I personally won't insist > further, especially since Luke knows Django better than me. May I > suggest again to mark this ticket to something different than "duplicate > of an invalid ticket"? > What difference does it make? Karen -- 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.
