On Jul 23, 2008, at 12:00 PM, Shane Ambler wrote:
To be honest I hadn't seen the use of INSERT INTO table (fld_x,
fld_y,fld_z) VALUES (DEFAULT, 'y','z') before, I have always gone
with INSERT INTO table (fld_x, fld_y,fld_z) VALUES (NULL, 'y','z')
is DEFAULT a better option than using NULL? or is it just a
preference to spell out the implied default entry?
I've only used DEFAULT in CREATE TABLE(...)
The semantics of using DEFAULT or NULL is completely different. If the
column has a default value (for example, 0), then including DEFAULT in
your insert list will give you the default value of zero. But if you
include NULL in your insert list -- you'll get NULL, not zero. If
nothing is included for the column in your insert list, you'll get the
column default if it has one, otherwise NULL.
John DeSoi, Ph.D.
--
Sent via pgsql-general mailing list (pgsql-general@postgresql.org)
To make changes to your subscription:
http://www.postgresql.org/mailpref/pgsql-general
