Re: [WebDNA] users.db

This WebDNA talk-list message is from

2009


It keeps the original formatting.
numero = 103306
interpreted = N
texte = Eddie Z wrote: > Is naming a database users.db a no no? I’m pretty sure I just found out > the hard way that it is, but wanted to clarify. I’m not sure why I added > an s to the end of a database I normally would call user.db, but for > some reason I did and then I couldn’t figure out why my searches weren’t > working. This is a good time to revisit 'convensions' once again I think. ;-) Because WebDNA is written in basic English, it is *always* a good idea to use naming conventions that are not basic English... such as: Text vars prefixed with "T_": [text]T_name=Donovan[/text] Form vars prefixed with "F_": Math vars prefixed with "M_": [math show=f]M_total=3000[/math] Global text vars "G_": [text scope=global]G_T_var=somevalue[/text] Customers Database that is specific to a site called "yourdomain" could be called "YD_customers.db", then the fields: [YDC_NAME] [YDC_ADDRESS] etc.. You don't have to use what I have above, rather roll your own. Conventions help insure that you don't run into reserved names, and they can make it much clearer for a 3rd party programmer to see what is going on. Just my .02¢ :-) Donovan -- Donovan Brooke WebDNA Software Corporation http://www.webdna.us **[Square Bracket Utopia]** Associated Messages, from the most recent to the oldest:

    
  1. Re: [WebDNA] users.db (John Butler 2009)
  2. Re: [WebDNA] users.db (Donovan Brooke 2009)
  3. Re: [WebDNA] users.db (Donovan Brooke 2009)
  4. Re: [WebDNA] users.db (John Butler 2009)
  5. Re: [WebDNA] users.db (William DeVaul 2009)
  6. Re: [WebDNA] users.db (Eddie Z 2009)
  7. Re: [WebDNA] users.db (John Butler 2009)
  8. Re: [WebDNA] users.db (Bert Votsis 2009)
  9. [WebDNA] users.db (Eddie Z 2009)
Eddie Z wrote: > Is naming a database users.db a no no? I’m pretty sure I just found out > the hard way that it is, but wanted to clarify. I’m not sure why I added > an s to the end of a database I normally would call user.db, but for > some reason I did and then I couldn’t figure out why my searches weren’t > working. This is a good time to revisit 'convensions' once again I think. ;-) Because WebDNA is written in basic English, it is *always* a good idea to use naming conventions that are not basic English... such as: Text vars prefixed with "T_": [text]T_name=Donovan[/text] Form vars prefixed with "F_": Math vars prefixed with "M_": [math show=f]M_total=3000[/math] Global text vars "G_": [text scope=global]G_T_var=somevalue[/text] Customers Database that is specific to a site called "yourdomain" could be called "YD_customers.db", then the fields: [YDC_NAME] [YDC_ADDRESS] etc.. You don't have to use what I have above, rather roll your own. Conventions help insure that you don't run into reserved names, and they can make it much clearer for a 3rd party programmer to see what is going on. Just my .02¢ :-) Donovan -- Donovan Brooke WebDNA Software Corporation http://www.webdna.us **[Square Bracket Utopia]** Donovan Brooke

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:

encripted storage (1998) WebCat2b12--[searchstring] bug (1997) Enhanced Master Counter? (1997) Log-in Scheme (2003) multiple databases (1997) Ampersand Character (&) (1997) [WebDNA] preventing hackers from posting their own (2009) Just Testing (1997) [referrer] tag (1997) Multiple security dbs (1997) [sendmail] questions... (1997) mac hack (1997) Generating Report Totals (1997) More Applescript (1997) Re:2nd WebCatalog2 Feature Request (1996) off topic fetch vs PCS photomaster (1997) WebCat2 beta 11 - new prefs ... (1997) Multiple Pulldowns (1997) America Online Issues (1998) Append (1999)