Re: Multiple 'Users.db' files not possible

This WebDNA talk-list message is from

1997


It keeps the original formatting.
numero = 15821
interpreted = N
texte = Hi Kenneth! I think you are missing my point. Specifically, I want my customer to be able to add and delete dealers as needed from a database that protects info in the web site. I don't want my customer to be able to modify any other user accounts outside of their domain, nor do I really want to give them access to the admin group. Tha't why I think a subusers.db for a given website would be a good solution, don't you?Brian B. Burton---------------------------------------------- Protect your right to own and arm bears. -------------------------------------------------------- ->From: Kenneth Grome ->To: WebDNA-Talk@smithmicro.com ->Subject: Re: Multiple 'Users.db' files not possible ->Date: Fri, 26 Dec 1997 16:07:24 -0800 -> ->>I'm sorry if this has been covered, but I still don't get it. I have a ->>customer who wants to basicallly have their own users.db to see certain info ->>on their shoppable website. -> ->Why would you want to create a separate database just for that group? -> ->>Specifically, they have in excess of 5000 dealer ->>customers who will need to log on with their account number and a password ->>to see the dealer pricing info from the website. I really don't think that ->>the only way to do this is to give an admin password to the users.db to my ->>customer, and the idea of 5000 records bloating my primary users.db makes me ->>shiver. -> ->Why? -> ->>I need to find some way of using the protect tag with a custom ->>dealer database which my customer can maintain. Any ideas? -> ->The protect tag calls the MultiGroupChecker file, so you can do ->something very similar to [protect] by duplicating the ->MultiGroupChecker file and giving it a new name, then changing ->users.db in the new file to a different db, then calling that new ->file with the [include newFileName] tag instead of using the ->[protect] tag in your templates. -> ->But I can tell you right now, you're all worried over nothing. I have ->16,000 users in my users.db and I cannot tell the difference in ->search speed between that 16,000 record db and a similar users.db ->with ONE record in it. In fact, I doubt you will notice any slowdown ->until your users.db gets to be WAY over 100,000 records ... :) -> ->Sincerely, ->Ken Grome ->ken@iav.com ->808-737-6499 ->WebDNA Solutions ->http://webdna.net/ -> -> -> Associated Messages, from the most recent to the oldest:

    
  1. Re: Multiple 'Users.db' files not possible (Grant Hulbert 1997)
  2. Re: Multiple 'Users.db' files not possible (Kenneth Grome 1997)
  3. Re: Multiple 'Users.db' files not possible (Gil Poulsen 1997)
  4. Re: Multiple 'Users.db' files not possible (Kenneth Grome 1997)
  5. Re: Multiple 'Users.db' files not possible (Brian B. Burton 1997)
  6. Re: Multiple 'Users.db' files not possible (Brian B. Burton 1997)
  7. Re: Multiple 'Users.db' files not possible (Kenneth Grome 1997)
  8. Re: Multiple 'Users.db' files not possible (John Hill 1997)
  9. Multiple 'Users.db' files not possible (Kenneth Grome 1997)
Hi Kenneth! I think you are missing my point. Specifically, I want my customer to be able to add and delete dealers as needed from a database that protects info in the web site. I don't want my customer to be able to modify any other user accounts outside of their domain, nor do I really want to give them access to the admin group. Tha't why I think a subusers.db for a given website would be a good solution, don't you?Brian B. Burton---------------------------------------------- Protect your right to own and arm bears. -------------------------------------------------------- ->From: Kenneth Grome ->To: WebDNA-Talk@smithmicro.com ->Subject: Re: Multiple 'Users.db' files not possible ->Date: Fri, 26 Dec 1997 16:07:24 -0800 -> ->>I'm sorry if this has been covered, but I still don't get it. I have a ->>customer who wants to basicallly have their own users.db to see certain info ->>on their shoppable website. -> ->Why would you want to create a separate database just for that group? -> ->>Specifically, they have in excess of 5000 dealer ->>customers who will need to log on with their account number and a password ->>to see the dealer pricing info from the website. I really don't think that ->>the only way to do this is to give an admin password to the users.db to my ->>customer, and the idea of 5000 records bloating my primary users.db makes me ->>shiver. -> ->Why? -> ->>I need to find some way of using the protect tag with a custom ->>dealer database which my customer can maintain. Any ideas? -> ->The protect tag calls the MultiGroupChecker file, so you can do ->something very similar to [protect] by duplicating the ->MultiGroupChecker file and giving it a new name, then changing ->users.db in the new file to a different db, then calling that new ->file with the [include newFileName] tag instead of using the ->[protect] tag in your templates. -> ->But I can tell you right now, you're all worried over nothing. I have ->16,000 users in my users.db and I cannot tell the difference in ->search speed between that 16,000 record db and a similar users.db ->with ONE record in it. In fact, I doubt you will notice any slowdown ->until your users.db gets to be WAY over 100,000 records ... :) -> ->Sincerely, ->Ken Grome ->ken@iav.com ->808-737-6499 ->WebDNA Solutions ->http://webdna.net/ -> -> -> Brian B. Burton

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:

[OT] Linux Mailservers (2003) ShowNext (1997) Error:Too many nested [xxx] contexts (1997) Hello??? (1997) PCS Frames (1997) Navigator 4.01 (1997) Num Sort Descending (2004) Undocumented changes create problems in webcat 4 ... (2000) Emailer help....! (1997) Creating folders and deleting files (1997) WebCat2.0 [format thousands .0f] no go (1997) Permissions with 3.06 Linux (2000) Error Lob.db records error message not name (1997) GrandTotal not right (1997) Follow-Up to: Removing [showif] makes a big difference in speed (1997) Problem: 3.0 doesn't update carts (1997) WebDelivery downloads alias, not original ? (1997) Cart Number Propagation (1997) Providing hard copy of database to client (1997) RE: WebCatalog2 for NT Beta Request (1997)