On 8/23/06, keukaman <[EMAIL PROTECTED]> wrote: > > Thank you. I took your advice and changed "photoid" to "entry". I'm new > to this, so can you elaborate a bit on why it's better to name that > field 'entry'?
I will assume I'm actually in the same channel that Chris here. On django models, every table has already an 'id' column (as every table should :), and external references to a column (foreignkeys) are named 'somecolumn_id', so photo_id could be misinterpreted to be a reference to another table. And if your table is named "photo" (almost) nothing should be named photo inside it, because is repetitive :), 'entry' is a generic understandable name for a common thing :) Max -- -----BEGIN GEEK CODE BLOCK----- Version: 3.12 GS/S d- s: a-29 C++(+++) ULAHI+++ P+ L++>+++ E--- W++ N* o-- K- w++++ O- M-- V-- PS+ PE Y-- PGP++ t- 5- X+ R tv++ b+ DI+++ D- G++ e++ h+ r+ z** ------END GEEK CODE BLOCK------ --~--~---------~--~----~------------~-------~--~----~ 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 -~----------~----~----~----~------~----~------~--~---
