Ok. This one is more of a "philosophy" question on django naming from someone who's learning django, webdev and databases at the same time.
If I understand right, one of django's aim at the ORM level is to abstract the sql level, including naming. This makes a lot of sense, and when you see : ManyToMany OneToOne you can see that the name of these relationships between models is very descriptive and non-sqlish. they describe the nature of the relationship desregarding the underlying implementation (which feels right). Now, for the many-to-one relations the name chosen was ForeignKey why is that? Isn't ForeignKey very sqlish and little descriptive? Doesn't it points too much on the implementation? --~--~---------~--~----~------------~-------~--~----~ You received this message because you are subscribed to the Google Groups "Django users" group. To post to this group, send email to django-users@googlegroups.com To unsubscribe from this group, send email to [EMAIL PROTECTED] For more options, visit this group at http://groups.google.com/group/django-users -~----------~----~----~----~------~----~------~--~---
