Re: ZEOS or PGDAC - How to lock a resource?

Поиск
Список
Период
Сортировка
От Mark Morgan Lloyd
Тема Re: ZEOS or PGDAC - How to lock a resource?
Дата
Msg-id iq0q3v$op0$1@pye-srv-01.telemetry.co.uk
обсуждение исходный текст
Ответ на Re: ZEOS or PGDAC - How to lock a resource?  (Merlin Moncure <mmoncure@gmail.com>)
Список pgsql-general
Merlin Moncure wrote:
> 2011/5/4 durumdara <durumdara@gmail.com>:
>> Hi!
>>
>> We will porting an application to PGSQL from some table based app (BDE
>> like).
>>
>> The older application used a special technic of the driver: if a record
>> edited, some exclusive (over transaction), "forever living" lock put on it.
>> On exit, cancel, or post this lock removed.
>>
>> We used this to lock the main resource from concurrent edits.

> advisory locks
> http://www.postgresql.org/docs/current/interactive/functions-admin.html#FUNCTIONS-ADVISORY-LOCKS
>
> (aside: borland delphi is increasingly obsolete in the scheme of
> things, but zeos is one of the best postgres drivers ever written!)

I don't use Zeos, but a few months ago I was using listen/notify via
FPC's standard classes to good effect so I'd be surprised if there were
any problems.

--
Mark Morgan Lloyd
markMLl .AT. telemetry.co .DOT. uk

[Opinions above are the author's, not those of his employers or colleagues]

В списке pgsql-general по дате отправления:

Предыдущее
От: Misa Simic
Дата:
Сообщение: Re: Multiple table relationship constraints
Следующее
От: Andrew Sullivan
Дата:
Сообщение: Re: Bidirectional replication