• Open Menu Close Menu
  • Apple
  • Shopping Bag
  • Apple
  • Mac
  • iPad
  • iPhone
  • Watch
  • TV
  • Music
  • Support
  • Search apple.com
  • Shopping Bag

Lists

Open Menu Close Menu
  • Terms and Conditions
  • Lists hosted on this site
  • Email the Postmaster
  • Tips for posting to public mailing lists
Re: locking DB through a dedicated lock table
[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

Re: locking DB through a dedicated lock table


  • Subject: Re: locking DB through a dedicated lock table
  • From: Ken Anderson <email@hidden>
  • Date: Mon, 05 Jan 2015 15:21:41 -0500

Can you explain your use case a little more?

In my experience, locking records through a database creates more work and doesn’t really solve the problem.  Under what circumstances do you need these locks?

Ken


On Jan 3, 2015, at 1:52 PM, OC <email@hidden> wrote:

> Hello there,
>
> I'm about to implement the support for reliable both inter- and intra-instance locking; most probably based on a separate table with different rows for different „locks“, or something like that.
>
> Presumably this is one case where fixed PKs are beneficial (so that two instances can't insert same lock row at once). Before I dive into all the possible race conditions and other gotchas, I wonder -- this being a pretty common need, isn't there somewhere already implemented appropriate support in WOnder?
>
> Thanks,
> OC
>
>
> _______________________________________________
> Do not post admin requests to the list. They will be ignored.
> Webobjects-dev mailing list      (email@hidden)
> Help/Unsubscribe/Update your Subscription:
>
> This email sent to email@hidden


 _______________________________________________
Do not post admin requests to the list. They will be ignored.
Webobjects-dev mailing list      (email@hidden)
Help/Unsubscribe/Update your Subscription:

This email sent to email@hidden


References: 
 >locking DB through a dedicated lock table (From: OC <email@hidden>)

  • Prev by Date: locking DB through a dedicated lock table
  • Next by Date: Re: Starting second instance=app not available
  • Previous by thread: locking DB through a dedicated lock table
  • Next by thread: Re: Starting second instance=app not available
  • Index(es):
    • Date
    • Thread