Re: Touch row ?
От | NTPT |
---|---|
Тема | Re: Touch row ? |
Дата | |
Msg-id | 003a01c3e2df$e7a15440$d300a8c0@webpropag.cz обсуждение исходный текст |
Ответ на | Re: Upcoming events (Bruce Momjian <pgman@candle.pha.pa.us>) |
Ответы |
Re: Touch row ?
|
Список | 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@travelamericas.com> Komu: "Chris Boget" <chris@wild.net>; "Doug McNaught" <doug@mcnaught.org> Kopie: "PostgreSQL-general" <pgsql-general@postgresql.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 > >
В списке pgsql-general по дате отправления: