I believe I can "set constraints" to achieve the same thing? I just don't want the check to happen until commit time. The users may make many row changes, the later ones "fixing" what the earlier ones would otherwise flag as problematic with the check. -----Original Message----- From: Tom Lane [mailto:tgl@xxxxxxxxxxxxx] Sent: Monday, September 14, 2009 7:19 PM To: Gauthier, Dave Cc: pgsql-general@xxxxxxxxxxxxxx Subject: Re: syntax troubles using "deferrable initially deferred" "Gauthier, Dave" <dave.gauthier@xxxxxxxxx> writes: > create table templates > ( > template text, > constraint template_not_null_check (template is nit null) deferrable initially deferred); > ERROR syntax error at or near "DEFERRABLE" > LINE 4: ...nt template_not_null_check (template is not null) DEFERRABLE... Sorry, there are no deferrable check constraints in Postgres. We only handle deferrable foreign keys (8.5 will have deferrable unique also). By and large there isn't any good reason that I can see for a deferrable check constraint --- you might as well check the row when it goes in. (If you are trying something cute that depends on the timing of the check, be advised that it probably wouldn't work reliably anyway.) regards, tom lane -- Sent via pgsql-general mailing list (pgsql-general@xxxxxxxxxxxxxx) To make changes to your subscription: http://www.postgresql.org/mailpref/pgsql-general
