quote:but for a large development team, especially one with new developers, this might become very confusion.
quote:One other note, the use of Underscores seems to swing in and out of favor. With the release of .NET, they are out of favor and SQL is supposed to be moving in that direction.
quote:Nice article and well written.
quote:To me, this has pitfalls similar to Hungarian naming - too often you run into situations where the name doesnt fit but you're stuck with it
quote:, or you end up violating the convention for a 'special case'.
quote:I can see where it might boost productivity in some cases - do you find that it does so enough to offset the increased time/effort it takes to enforce the convention?[quote]Oh, yes, certainly. Whenever I get called on to work on a system where the method is not used, I find I miss it dearly. Maybe that's because I'm so used to it, it's hard to tell, but I find great benefits.[quote]Thanks for writing the article, good to get some different points of view on here! Hope we see more stuff from you in the future.
quote:My question regards foreign keys: what if two tables have a foriegn key to the same field on a third table - how is this column then named?
quote:Mattias: my FK question really concerns a column on a table which is a foreign key in more than one instance. It may be a foreign key on it's own to table A and part of a combined FK to table B. Admittedly this is a slightly unusual situation, but how would the naming cope with this?
quote:(another such problematic 'exception' would be self-joins).