Hi Ferindo
>The intended effect is to get a timestamp field that inserts the
current system
>time on inserts and continues to update the field with the current
timestamp
>on updates without the application or use needing to specify it
are you
>saying that the timestamp attribute alone wil
Thanks Peter. I did originally use this table in a Postgresql db. Thanks
for you advice. Your suggestions below allowed me to create this table
and I learned a thing t two about proper usage of the TIMESTAMP data
type. The intended effect is to get a timestamp field that inserts the
current sys
Ferindo
One problem is:
employment_status_id INTEGER REFERENCES employment_statuses(id) NOT
NULL,
NOT NULL should be before REFERENCES.
Also, in:
last_updated TIMESTAMP DEFAULT CURRENT_TIMESTAMP NOT NULL,
(i) NOT NULL is superfluous since the default is given by
CURRENT_TIMESTAMP.
(ii)
