| List: | General Discussion | « Previous MessageNext Message » | |
| From: | Thimble Smith | Date: | July 27 1999 6:51pm |
| Subject: | Re: Restrict Access | ||
| View as plain text | |||
At 15:29, 19990727, sinisa@stripped wrote: >toxalot@stripped writes: > > Access to the database requires a piad subscription and we don't want > > companies buying one subscription and then letting all employess use the > > same user name. > >select get_lock("user_name",10000); >......... > >select release_lock("user_name"); Since the lock names are global (i.e., not qualified by the database or user or anything else), I would suggest using a longer name for your locks, which includes a unique identifier for YOU, one for the COMPANY you're dealing with, and finally the specific USER you are locking out. For example, you might use select get_lock("YOUR-DB-NAME;The Company;user_name", 10000); You don't know who else is using locks on the database system that you're running. Huh, that makes me wonder - what privileges are required to select get_lock()? Would it be possible, on a shared system (like at an ISP that provides MySQL support), for someone to deny service to a totally unrelated account by acquiring locks that they depend on, and not releasing them? Tim
| Thread | ||
|---|---|---|
| • Restrict Access | toxalot | 27 Jul |
| • Restrict Access | sinisa | 27 Jul |
| • Re: Restrict Access | Thimble Smith | 27 Jul |
| • Re: Restrict Access | Paul DuBois | 27 Jul |
| • Re: Restrict Access | Martin Ramsch | 27 Jul |
| • Re: Restrict Access | Paul DuBois | 28 Jul |
| • Re: Restrict Access | Thimble Smith | 28 Jul |
| • Re: Restrict Access | sinisa | 28 Jul |
| • Re: Restrict Access | toxalot | 28 Jul |
| • On GET_LOCK () | sinisa | 28 Jul |
| • Re: On GET_LOCK () | Benjamin Pflugmann | 28 Jul |
| • Re: On GET_LOCK () | sinisa | 28 Jul |
| • Re: On GET_LOCK () | Paul DuBois | 28 Jul |
| • Re: On GET_LOCK () | Jim Faucette | 28 Jul |
| • Re: On GET_LOCK () | Paul DuBois | 28 Jul |
| • Re: On GET_LOCK () | Thimble Smith | 28 Jul |
| • Re: On GET_LOCK () | Gerald Clark | 28 Jul |
| • Re: On GET_LOCK () | Paul DuBois | 28 Jul |
| • Re: On GET_LOCK () | sinisa | 28 Jul |
| • Re: On GET_LOCK () | Paul DuBois | 28 Jul |
| • Re: On GET_LOCK () | Scott Hess | 28 Jul |
| • getting rid of duplicates | Joel Bremson | 28 Jul |
| • Re: getting rid of duplicates | Christian Mack | 28 Jul |
| • Re: On GET_LOCK () | sinisa | 29 Jul |
| • Re: On GET_LOCK () | Paul DuBois | 29 Jul |
| • Re: On GET_LOCK () | Scott Hess | 29 Jul |
| • Re: On GET_LOCK () | toxalot | 28 Jul |
| • Re: On GET_LOCK () | sinisa | 28 Jul |
| • Re: On GET_LOCK () | Benjamin Pflugmann | 29 Jul |
| • Re: On GET_LOCK () | Sasha Pachev | 29 Jul |
| • Re: On GET_LOCK () | Benjamin Pflugmann | 31 Jul |
| • Re: On GET_LOCK () | Thimble Smith | 29 Jul |
| • Re: On GET_LOCK () | Fraser MacKenzie | 29 Jul |
| • Re: On GET_LOCK () | Thimble Smith | 29 Jul |
| • Re: On GET_LOCK () | Fraser MacKenzie | 29 Jul |
| • Re: On GET_LOCK() | R. Mentink | 31 Jul |
