I would really hate to be the one maintaining code like that.
What happens if someone adds a column, or rearranges the columns? I know some folks that will change their column order whenever they add a column to a table so that their auditing columns are always the last columns in the table. Guaranteed breakage.
I would think that:
my $q=$dbh->query("INSERT INTO foo (col1, col2, col3, col4, col5) V +ALUES (?,?,?,?,?); $q->execute($bar, $baz, $qx, $qux, $quux);
would be more robust as it doesn't make any assumptions about either the column order or the number of columns (assuming any columns not listed are nullable). Also, wouldn't naming the columns make the code more readable and maintainable (by virtue of being able search on the column names)?
In reply to Re: Database field names in code
by gsiems
in thread Database field names in code
by disciple
| For: | Use: | ||
| & | & | ||
| < | < | ||
| > | > | ||
| [ | [ | ||
| ] | ] |