Yup that's bad style and lazy coding. I always specify the column
list just to avoid assumptions about the column order in the
underlying table--which could change and existing code would then be
wrong.

On Feb 21, 2008, at 10:05 AM, Peter Hickman wrote:

> Serg Koren wrote:
>> That's what I get trying to when I'm not awake. I misread his
>> code and missed the VALUES keyword. My apologies.
>>
>
>
> Actually the syntax you proposed is also valid but was not what was
> wrong with his code. However I would never recommend the "INSERT
> INTO tablename VALUES (x, y, z);" format as the it can appear to be
> correct but be stuffing the values into the wrong columns
>
> Thats just soooo much fun to debug.
>
> Caffine good.
>
>