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:

Non-Cart Files in Shopping Cart Folder (1997) Date Range Sorting (1997) File Uploads... (1997) Navigator Parsing (1997) test (2006) [WebDNA] How can I check if rewrite and fastcgi is loaded correct? (2013) MacAuthorize hub, no modal password dialog? (1997) Duplicate Emails being sent (2004) Universal root for WC errors? (1997) I'm new be kind (1997) Country & Ship-to address & other fields ? (1997) Authenticating users without dialog box (1997) problems with 2 tags (1997) question: webdelivery folder and file (1997) WebCat 2.1beta etc (1997) [WebDNA] Two stores one db (2011) WebDNA Promo Sound Bite (2003) Permission denied? (2004) WC 2.0 frames feature (1997) Server Load Tester (2000)