Re: & Aftermath

This WebDNA talk-list message is from

1999


It keeps the original formatting.
numero = 25597
interpreted = N
texte = Mooseman, the reason this whole thing came up is because SM tech support told me yesterday to never allow an & to get into my db if I am using unix webcat. So I asked the list if this is right since it didn't feel right to me... I mean really *never* allow an amperasand into any db??! Ken says you are safe if you use [URL] in all the right places... SM's Store builder apparently does not do that from what I can gather. If anyone knows why there is a good reason to *not* allow an & into any db on unix or other platform (even when one is careful to use [URL]), then I wold love to hear it. If unix webcat and mac webcat behave differently I would love to hear that.-JohnKenneth Grome wrote:> >Kenny G said > >>The & is written to the db, just try it then look in your db and you'll see it > >for yourself ... > > > > > >Thats all I was asking with even the sloppy examples.... > > > >after all the [URLing] when I look in the database > >the & is there. > > > >So do I want it there as a & ; > >or as a %26 > >or as some other ascii text I don't know about? > > The ampersand is fine in the db, and in fact that's exatly what is supposed to be stored in the db. > > If you always enter whatever text you actually want stored in the db into your forms, then make sure to wrap the form field tag in a [url] context when appending or replacing to the db on the next page, you will never have a problem. > > If you use the [url] context every time, around every value in your append and replace contexts, you can enter any text you feel like in your forms ... that's why using [url] is so highly recommended. It fixes all database data entry problems when used consistently and properly ... :) > > ================================ > Kenneth Grome, WebDNA Consultant > 808-737-6499, http://webdna.net > ================================ > > ------------------------------------------------------------- > Brought to you by CommuniGate Pro - The Buzz Word Compliant Messaging Server. > To end your Mail problems go 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 ------------------------------------------------------------- Brought to you by CommuniGate Pro - The Buzz Word Compliant Messaging Server. To end your Mail problems go 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:

    
Mooseman, the reason this whole thing came up is because SM tech support told me yesterday to never allow an & to get into my db if I am using unix webcat. So I asked the list if this is right since it didn't feel right to me... I mean really *never* allow an amperasand into any db??! Ken says you are safe if you use [url] in all the right places... SM's Store builder apparently does not do that from what I can gather. If anyone knows why there is a good reason to *not* allow an & into any db on unix or other platform (even when one is careful to use [url]), then I wold love to hear it. If unix webcat and mac webcat behave differently I would love to hear that.-JohnKenneth Grome wrote:> >Kenny G said > >>The & is written to the db, just try it then look in your db and you'll see it > >for yourself ... > > > > > >Thats all I was asking with even the sloppy examples.... > > > >after all the [URLing] when I look in the database > >the & is there. > > > >So do I want it there as a & ; > >or as a %26 > >or as some other ascii text I don't know about? > > The ampersand is fine in the db, and in fact that's exatly what is supposed to be stored in the db. > > If you always enter whatever text you actually want stored in the db into your forms, then make sure to wrap the form field tag in a [url] context when appending or replacing to the db on the next page, you will never have a problem. > > If you use the [url] context every time, around every value in your append and replace contexts, you can enter any text you feel like in your forms ... that's why using [url] is so highly recommended. It fixes all database data entry problems when used consistently and properly ... :) > > ================================ > Kenneth Grome, WebDNA Consultant > 808-737-6499, http://webdna.net > ================================ > > ------------------------------------------------------------- > Brought to you by CommuniGate Pro - The Buzz Word Compliant Messaging Server. > To end your Mail problems go 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 ------------------------------------------------------------- Brought to you by CommuniGate Pro - The Buzz Word Compliant Messaging Server. To end your Mail problems go 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:

[cart]'s ever get recycled? (2000) Sami (1998) Bad cookie (1998) Re:no [search] with NT (1997) WebCat2b13MacPlugIn - [include] doesn't allow creator (1997) webcat- multiple selection in input field (1997) Nested vs conditional (1997) $Replace with [founditems] (1997) inconsistent webcat calculation? (1997) Download Question (1997) Bug or syntax error on my part? (1997) Shownext problems (1999) OT: WebSTAR Modify Rules (2006) Out of the woodwork (2007) WebCatb15 Mac CGI -- [purchase] (1997) taxTotal, grandTotal (1997) Search Question (2000) TCPconnect issue (2000) Nesting WebDNA in JavaScript (2003) UPDATE PROBLEM (1997)