Re: [replace] has protection feature like [delete]?

This WebDNA talk-list message is from

2000


It keeps the original formatting.
numero = 31541
interpreted = N
texte = otherwise how does one allow differing levels of administrators to [replace] *only* their alloted records in a db which is accessed by ALL level of admin? (ie. prevent them from editing records that do not belong to their authenticate group?)-JohnJohn Butler wrote:> [DELETE db=DatabasePath&eqNAMEdata=Fred] > ... Note: if the database has username and password fields, then the records will not > be deleted unless the visitor's web browser username/password match the record's > username/password. > > is this behaviour also true for the [replace] context? There is no mention of it in > the docs, but it would be nice to have that option so I ask... > > -John > > ------------------------------------------------------------- > This message is sent to you because you are subscribed to > the mailing list . > To unsubscribe, E-mail to: > To switch to the DIGEST mode, E-mail to ------------------------------------------------------------- This message is sent to you because you are subscribed to the mailing list . To unsubscribe, E-mail to: To switch to the DIGEST mode, E-mail to Associated Messages, from the most recent to the oldest:

    
  1. Re: [replace] has protection feature like [delete]? (John Butler 2000)
  2. Re: [replace] has protection feature like [delete]? (WebDNA Support 2000)
  3. Re: [replace] has protection feature like [delete]? (John Butler 2000)
  4. Re: [replace] has protection feature like [delete]? (Kenneth Grome 2000)
  5. [replace] has protection feature like [delete]? (John Butler 2000)
otherwise how does one allow differing levels of administrators to [replace] *only* their alloted records in a db which is accessed by ALL level of admin? (ie. prevent them from editing records that do not belong to their authenticate group?)-JohnJohn Butler wrote:> [DELETE db=DatabasePath&eqNAMEdata=Fred] > ... Note: if the database has username and password fields, then the records will not > be deleted unless the visitor's web browser username/password match the record's > username/password. > > is this behaviour also true for the [replace] context? There is no mention of it in > the docs, but it would be nice to have that option so I ask... > > -John > > ------------------------------------------------------------- > This message is sent to you because you are subscribed to > the mailing list . > To unsubscribe, E-mail to: > To switch to the DIGEST mode, E-mail to ------------------------------------------------------------- This message is sent to you because you are subscribed to the mailing list . To unsubscribe, E-mail to: To switch to the DIGEST mode, E-mail to John Butler

DOWNLOAD WEBDNA NOW!

Top Articles:

Talk List

The WebDNA community talk-list is the best place to get some help: several hundred extremely proficient programmers with an excellent knowledge of WebDNA and an excellent spirit will deliver all the tips and tricks you can imagine...

Related Readings:

Listserver problem (1997) Help name our technology! (1997) Nested vs conditional (1997) Multiple Passwords (1997) emailer problem on OS X - unsent emails (2003) WebMerchant 3.0? (1998) Different Drive (2003) Disappearing HTML/WebDNA (1998) process SSI (1998) Storefornts (1997) Submit buttons not working.... (1999) [WebDNA] Query re: autonumber (2010) Shopping carts and reloading pages (1997) Nested vs conditional (1997) Apoligy (1997) Re:2nd WebCatalog2 Feature Request (1996) Spreadsheet Interface. (1998) WebCat2b12 CGI Mac - [shownext] problem (1997) WebCat2.0b15-to many nested [xx] tags (1997) [ShowNext] feature in 2.0 (1997)