Re: Confused about Grep Syntax
This WebDNA talk-list message is from 2004
It keeps the original formatting.
numero = 56857
interpreted = N
texte = >>>For the sake of discussion, when is it not appropriate to wrap >>>parameters or user input in [url] tags? >> >>In forms you should always put the values inside input contexts, >>not url contexts. > >Well, yes, [input] for displaying textarea values. Not just for textarea fields, for regular text fields too. This is a good standard practice because (for example): 1- If you import your db from another source and if any value in any field *might* have a converted CR character in it, you will need the input context to keep your form field from 'breaking' if you use values in that field to populate regular text fields in the form. 2- I haven't tested this (or maybe I have and that's why I'm thinking about it now) but I think it is possible to 'copy and paste' a CR into a regular text field even though you cannot physsically type a CR into a text field directly. If this is true, the CR that you 'copied and pasted' into that field will end up in a database field that you thought would never contain this kind of character. Thus when you use this value to populate a text field in a form, that field will break unless you have put it inside an input context. 3- If you use a textarea field for data input and you write that data to a db, then later you 'change your forms' and decide to use a regular text field to display the data from this field, the CR's that were entered while using the textarea field will still be in the db and therefore you will need to use an input context to populate your text field with this data to prevent the form from breaking. Are there other situations in which a CR might be saved to a db field without your knowing or expecting it? If so, these would be even more good reasons to use input in all your form fields that display data, not just the textarea values. -- Kenneth Grome WebDNA Programmer Outsource Service Provider Phone: +6332 255-6591 ------------------------------------------------------------- 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:
>>>For the sake of discussion, when is it not appropriate to wrap >>>parameters or user input in [url] tags? >> >>In forms you should always put the values inside input contexts, >>not url contexts. > >Well, yes, [input] for displaying textarea values. Not just for textarea fields, for regular text fields too. This is a good standard practice because (for example): 1- If you import your db from another source and if any value in any field *might* have a converted CR character in it, you will need the input context to keep your form field from 'breaking' if you use values in that field to populate regular text fields in the form. 2- I haven't tested this (or maybe I have and that's why I'm thinking about it now) but I think it is possible to 'copy and paste' a CR into a regular text field even though you cannot physsically type a CR into a text field directly. If this is true, the CR that you 'copied and pasted' into that field will end up in a database field that you thought would never contain this kind of character. Thus when you use this value to populate a text field in a form, that field will break unless you have put it inside an input context. 3- If you use a textarea field for data input and you write that data to a db, then later you 'change your forms' and decide to use a regular text field to display the data from this field, the CR's that were entered while using the textarea field will still be in the db and therefore you will need to use an input context to populate your text field with this data to prevent the form from breaking. Are there other situations in which a CR might be saved to a db field without your knowing or expecting it? If so, these would be even more good reasons to use input in all your form fields that display data, not just the textarea values. -- Kenneth Grome WebDNA Programmer Outsource Service Provider Phone: +6332 255-6591 ------------------------------------------------------------- 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/
Kenneth Grome
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:
rotating thumbnails (1997)
Credit card processing options. . . (1997)
Re[2]: Field Problem (2000)
Help!!!! (1997)
WebDNA 6 vs. Lasso 7 (2004)
[username][password] not showing up! HELP! (1999)
Loops N Variables (1998)
ShowNext (1997)
Using Plug-In while running 1.6.1 (1997)
Not really WebCat (1997)
Issue with plug-in Webcat, webstar 4.x, SSL and IE when using the backbuttom (2000)
RE: OK, here goes... (1997)
Shopping Cart Limits? (1998)
Sending HTML messages with [sendmail] (2002)
shipcost (1997)
Founditems context returning only 1 item (1997)
Sendmail on OSX (2000)
Requiring that certain fields be completed (1997)
multiple credit card merchant accounts/processors (1997)
requiring form fields? (2000)