NOTE: use Perl; is on undef hiatus. You can read content, but you can't post it. More info will be forthcoming forthcomingly.
All the Perl that's Practical to Extract and Report
Stories, comments, journals, and other submissions on use Perl; are Copyright 1998-2006, their respective owners.
USING is bad anyway (Score:1)
I prefer to name my primary key column `id` and use `foo_id` as the name for foreign key columns. Then I use `ON` explicitly.
Overall the query becomes more verbose, but I prefer it that way. It makes my schemata much more easily readable when columns immediately reveal themselves for what they are by their name.
Re: (Score:2)
That still doesn't fix the bug :)
Re:USING is bad anyway (Score:1)
I’m saying that you got bitten this easily because you combined two bad ideas.
Although now that I think of it, the naming scheme I use means that any join would lead to duplicate
idcolumns.Good thing I avoid
SELECT *like the pest, then. Hmm, looking at some of my own source code, I find I do use the star quite a lot in the older parts. However, it’s always qualified with a table name, which explains why I never ran into your bug.Reply to This
Parent