On Tue, 22 Sep 2009, D. Richard Hipp wrote: > The question is this: Should the no-op UPDATE statement (x=x) cause the > ON UPDATE SET NULL foreign key constraint to set t2.y to NULL or not? > > PostgreSQL says "no" - the t2.y value is not nulled unless the t1.x > value really does change values.
Richard, Given the choices, I would go with postgres. It is rational and logical that if the t1.x value has not changed then the referential t2.x value should not be changed either. > And a related question: Does anybody really care about ON UPDATE SET > NULL? Has anybody ever actually seen ON UPDATE SET NULL used in practice? Not I. Rich -- Richard B. Shepard, Ph.D. | Integrity Credibility Applied Ecosystem Services, Inc. | Innovation <http://www.appl-ecosys.com> Voice: 503-667-4517 Fax: 503-667-8863 _______________________________________________ sqlite-users mailing list sqlite-users@sqlite.org http://sqlite.org:8080/cgi-bin/mailman/listinfo/sqlite-users
