Re: Logical locking beyond pg_advisory

On 17/09/2018 14:27 , Chris Travers wrote:
>
>
> On Mon, Sep 17, 2018 at 6:04 PM marcelo <marcelo(dot)nicolet(at)gmail(dot)com
> <mailto:marcelo(dot)nicolet(at)gmail(dot)com>> wrote:
>
>
>
> I´m using an ORM (Devart´s) to access the database, so, I cannot
> "select ... FOR UPDATE". The application paradigm is that a user
> have a list of records (after a query) and she could update or
> delete any of them as the business rules allows it. So, at least
> an advisory lock is a must.
> I´m convinced by now: I would stay with advisory locks...
> expecting no app crash could occur...
>
>
> I would say to fix this in the ORM rather than reinvent what the
> database already gives you in the database.
>
You are right. But you know...
>
> Thank you all.
> Marcelo
>
> <https://www.avast.com/sig-email?utm_medium=email&utm_source=link&utm_campaign=sig-email&utm_content=emailclient>
> Libre de virus. www.avast.com
> <https://www.avast.com/sig-email?utm_medium=email&utm_source=link&utm_campaign=sig-email&utm_content=emailclient>
>
>
> <#m_-9091154853724945458_DAB4FAD8-2DD7-40BB-A1B8-4E2AA1F9FDF2>
>
>
>
> --
> Best Wishes,
> Chris Travers
>
> Efficito:  Hosted Accounting and ERP.  Robust and Flexible.  No vendor
> lock-in.
> http://www.efficito.com/learn_more

---
El software de antivirus Avast ha analizado este correo electrónico en busca de virus.
https://www.avast.com/antivirus