Sorry, but this is very poor advice. It's always better to list the columns in an insert statement rather than depending on column order in the table. It costs you nothing (other than typing ;-), clarifies your intent, and protects you against future changes to the table. The syntax has been standard since at least SQL-89, so any self-respecting RDBMS will support it.
I think your other example is confusing UPDATE statements with INSERT statements. It's UPDATE table SET col = val, ...There is no SET clause in an INSERT statement in any dialect of SQL I know.
In reply to Re: Re: It won't insert
by VSarkiss
in thread Problem with insert using DBI
by mnlight
| For: | Use: | ||
| & | & | ||
| < | < | ||
| > | > | ||
| [ | [ | ||
| ] | ] |