Re: multiple db's

This WebDNA talk-list message is from

2003

It keeps the original formatting. numero = 47399
interpreted = N
texte = Thanks for the info. I had a feeling all would be OKI started renaming a few of the db's today after I started to get a little confused with similar database names. I was getting confused keeping track of which one I was working on and where. Renaming them consistently made it all clearer . . .At 09:30 AM 2/4/03 -0800, you wrote:>WebDNA has no problem dealing with multiple databases having fields with >the same name. Sometimes Developers do, however.>>A primary example comes up when you nest searches.... Say you have two >databases - a.db and b.db - that both have a field named name.>>[search db=a.db...][founditems]>[search db=b.db...][founditems]>[name] - comes from b.db - you can't see the one from a.db here>[/founditems][/search]>[/founditems][/search]>>Basically, WebDNA searches the innermost scope for a >field/variable/lineitem field/orderfile header/formvariable/WebDNA tag >first, then moves outward to the next scope until an identifier of the >specified name is found.>>Note the oft-lamented problem incurred by the presence of a header named >date in order files, which prevents access to the WebDNA tag of the same >name when within an orderfile context.>>For my own clarity and peace of mind, I always name database fields with a >three-letter prefix indicating the database the field is from - for >example, proName for a products db and memName for a members db.>>- brian>>On Tuesday, February 4, 2003, at 07:32 AM, Lester Emo wrote:>>>As I was placing another site on a server this morning a question came to >>mind.>>>>I never use the same name for 2 db's no matter where they are stored.>>(same directory or /globals directory)>>BUT>>I sometimes use the exact same names for some of the fields in these >>different databases.>>>>This wouldn't cause any problems somewhere down the line would it??>>>>Webdna keeps track of what is what and who is who when it keeps db's in >>memory??>>>>>>Thanks>>lester>>-- Brian Fries, BrainScan Software -- http://www.brainscansoftware.com -->>>------------------------------------------------------------->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 >>Web Archive of this list is at: http://webdna.smithmicro.com/-------------------------------------------------------------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 Web Archive of this list is at: http://webdna.smithmicro.com/ Associated Messages, from the most recent to the oldest:

Re: multiple db's (Gary Krockover 2003)
Re: multiple db's (Kenneth Grome 2003)
Re: multiple db's (Lester Emo 2003)
Re: multiple db's (Alex McCombie 2003)
Re: multiple db's (Brian Fries 2003)
Re: multiple db's (Alex McCombie 2003)
Re: multiple db's (Donovan 2003)
multiple db's (Lester Emo 2003)

Thanks for the info. I had a feeling all would be OKI started renaming a few of the db's today after I started to get a little confused with similar database names. I was getting confused keeping track of which one I was working on and where. Renaming them consistently made it all clearer . . .At 09:30 AM 2/4/03 -0800, you wrote:>WebDNA has no problem dealing with multiple databases having fields with >the same name. Sometimes Developers do, however.>>A primary example comes up when you nest searches.... Say you have two >databases - a.db and b.db - that both have a field named name.>>[search db=a.db...][founditems]>[search db=b.db...][founditems]>[name] - comes from b.db - you can't see the one from a.db here>[/founditems][/search]>[/founditems][/search]>>Basically, WebDNA searches the innermost scope for a >field/variable/lineitem field/orderfile header/formvariable/WebDNA tag >first, then moves outward to the next scope until an identifier of the >specified name is found.>>Note the oft-lamented problem incurred by the presence of a header named >date in order files, which prevents access to the WebDNA tag of the same >name when within an orderfile context.>>For my own clarity and peace of mind, I always name database fields with a >three-letter prefix indicating the database the field is from - for >example, proName for a products db and memName for a members db.>>- brian>>On Tuesday, February 4, 2003, at 07:32 AM, Lester Emo wrote:>>>As I was placing another site on a server this morning a question came to >>mind.>>>>I never use the same name for 2 db's no matter where they are stored.>>(same directory or /globals directory)>>BUT>>I sometimes use the exact same names for some of the fields in these >>different databases.>>>>This wouldn't cause any problems somewhere down the line would it??>>>>Webdna keeps track of what is what and who is who when it keeps db's in >>memory??>>>>>>Thanks>>lester>>-- Brian Fries, BrainScan Software -- http://www.brainscansoftware.com -->>>------------------------------------------------------------->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 >>Web Archive of this list is at: http://webdna.smithmicro.com/-------------------------------------------------------------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 Web Archive of this list is at: http://webdna.smithmicro.com/ Lester Emo

DOWNLOAD WEBDNA NOW!

Re: multiple db's

2003

Top Articles:

Related Readings: