From: | "NTPT" <ntpt(at)centrum(dot)cz> |
---|---|
To: | "Chris Travers" <chris(at)travelamericas(dot)com>, "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-25 01:09:02 |
Message-ID: | 003a01c3e2df$e7a15440$d300a8c0@webpropag.cz |
Views: | Raw Message | Whole Thread | Download mbox | Resend email |
Thread: | |
Lists: | pgsql-announce pgsql-general |
And why in POSTGRESQL there is not just an appropriate DATATYPE for creating a column type touch_timestamp in table (I suggest touch_timestamp to be the same in one transaction... ) ?
I thing that it might be useful (and add no overhead) for lot of tasks ......
----- Puvodní zpráva -----
Od: "Chris Travers" <chris(at)travelamericas(dot)com>
Komu: "Chris Boget" <chris(at)wild(dot)net>; "Doug McNaught" <doug(at)mcnaught(dot)org>
Kopie: "PostgreSQL-general" <pgsql-general(at)postgresql(dot)org>
Odesláno: 24. ledna 2004 4:27
Predmet: Re: [GENERAL] Touch row ?
> > 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
>
>
> ---------------------------(end of broadcast)---------------------------
> TIP 8: explain analyze is your friend
>
>
From | Date | Subject | |
---|---|---|---|
Next Message | Chris Travers | 2004-01-25 05:45:04 | Re: Touch row ? |
Previous Message | Eric Ridge | 2004-01-24 21:19:23 | Re: Touch row ? |
From | Date | Subject | |
---|---|---|---|
Next Message | Bruce Momjian | 2004-01-25 02:29:12 | Re: FAQ (disk space) |
Previous Message | Bruce Momjian | 2004-01-25 00:54:08 | Re: fixed-length row |