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
--Larry Wall in perl.c from the perl source code
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: (Score:2)
I don't actually see the bug, yet, but I'm still a little groggy this AM. I do agree with your principle. But you may have to help me along to see this specific bug. :)
J. David works really hard, has a passion for writing good software, and knows many of the world's best Perl programmers
Re:USING is bad anyway (Score:2)
Major Hint: what are we joining on and what data structure is Perl using?
Reply to This
Parent