Re: Vote totals for SET in aborted transaction
От | Philip Warner |
---|---|
Тема | Re: Vote totals for SET in aborted transaction |
Дата | |
Msg-id | 5.1.0.14.0.20020427114144.029f6ec0@mail.rhyme.com.au обсуждение исходный текст |
Ответ на | Re: Vote totals for SET in aborted transaction (Bruce Momjian <pgman@candle.pha.pa.us>) |
Ответы |
Re: Vote totals for SET in aborted transaction
|
Список | pgsql-hackers |
At 11:50 25/04/02 -0400, Bruce Momjian wrote: >Marc G. Fournier wrote: > > > > Just curious here, but has anyone taken the time to see how others are > > doing this? For instance, if we go with 1, are going against how everyone > > else handles it? IMHO, its not a popularity contest ... Dec/RDB (and I think Oracle as well) ignores transactions. Even configuration commands (eg. setting date formats etc) ignore transactions. I think the key thing here is that they view variables as part of a programming language built on top of the database backend (like plpgsql). As a result they separate variable management from database management. FWIW, I would be in the '?' camp - assuming that means some kind of session-specific setting...failing that, I'd probably start looking for an interactive form of plpgsql, so I could get persistant variables.
В списке pgsql-hackers по дате отправления: