| From: | "Chris Travers" <chris(at)travelamericas(dot)com> |
|---|---|
| To: | "Chris Boget" <chris(at)wild(dot)net>, "Doug McNaught" <doug(at)mcnaught(dot)org> |
| Cc: | "PostgreSQL-general" <pgsql-general(at)postgresql(dot)org> |
| Subject: | Re: Touch row ? |
| Date: | 2004-01-24 03:27:23 |
| Message-ID: | 015001c3e23a$fa5fd1b0$97285e3d@winxp |
| Views: | Raw Message | Whole Thread | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-announce pgsql-general |
> Interesting. Yet another item to tack onto my list of differences between
> MySQL and Postgres.
Does MySQL apply defaults to updates?
If so, I can only stare in amazement.... Something like "update customer
set address = '1 my road' where customer_id = '123' SHOULD NOT touch any
other tables unless one has specifically enabled such a tracking using a
trigger...
Best Wishes,
Chris Travers
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Chris Travers | 2004-01-24 05:36:19 | Re: Touch row ? |
| Previous Message | Eric B.Ridge | 2004-01-24 02:44:25 | Re: Touch row ? |
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Dan Langille | 2004-01-24 05:32:06 | Re: LIVE Coverage of LinuxWorld Conference & Expo |
| Previous Message | Christopher Murtagh | 2004-01-24 03:20:28 | Re: Calling triggers with arguments |