Re: Showif date > other date
This WebDNA talk-list message is from 2004
It keeps the original formatting.
numero = 56783
interpreted = N
texte = Nice one Thanks for all that very valuable information, I'm glad I asked now :D I am very interested in the concept of the generic append / replace (I must check the archives) I have to say and it should definitely be documented somewhere or added to one of the many webdna resources. Has anybody done anything like a fusebox model for webdna as this sounds like the sort of thing that would plug into a "fusebox"? Cheers Alan P.S. I have only really skimmed the topic of fuseboxes but it seems like a good solid model that could be implemented within our community if not already. on 3/12/04 4:00 AM, Kenneth Grome at webdna@kengrome.com wrote: >> On Mar 11, 2004, at 7:19 PM, Kenneth Grome wrote: >> >>> Actually I haven't had to do any range searches on the dates we >>> store like this, but if I did I would probably just add a >>> "daysSince0000" field to my db first, then run the range search on >>> that new field. >> >> Only reason I ask is it just seems easier to store the dates as >> numbers or normal dates in one field and split it apart using >> [getchars] than to do all that. :) > > > In some situations you're right, I agree with you. For those who > need to put a lot of range searches into their code, using a single > field may same more time than using the techniques I've described. > > It's just that in my experience I find a greater time saving by > storing my dates as three separate components, because for one thing > this technique *also* allows me to use generic append and replace > code that looks something like this: > > [replace > db=xxx.db&eqskudata=[sku]][formvariables][name]=[url][value][/url]&[/formvaria > bles][/replace] > > Coding with generic append and replace contexts saves me tons of > time. I'm always adding new fields or changing field names or > deleting fields in my db's as I develop my sites, and this technique > saves me from having to change all my append and replace contexts > every time I change a db field. > > And since I don't need to do range searches on my dates very often, > this approach is the best for me in many cases. But it's not the > best for everyone, nor is is the best for me in every situation. > > Still, it is something to consider: > > 1- if you find yourself spending too much time writing customized > appends and replaces, and/or ... > > 2- if you find it easier to populate form fields directly -- by using > the *entire* field -- value rather than extracting parts of the value > via getchars, middle, listwords, etc. > > :) ------------------------------------------------------------- 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:
Nice one Thanks for all that very valuable information, I'm glad I asked now :D I am very interested in the concept of the generic append / replace (I must check the archives) I have to say and it should definitely be documented somewhere or added to one of the many webdna resources. Has anybody done anything like a fusebox model for webdna as this sounds like the sort of thing that would plug into a "fusebox"? Cheers Alan P.S. I have only really skimmed the topic of fuseboxes but it seems like a good solid model that could be implemented within our community if not already. on 3/12/04 4:00 AM, Kenneth Grome at webdna@kengrome.com wrote: >> On Mar 11, 2004, at 7:19 PM, Kenneth Grome wrote: >> >>> Actually I haven't had to do any range searches on the dates we >>> store like this, but if I did I would probably just add a >>> "daysSince0000" field to my db first, then run the range search on >>> that new field. >> >> Only reason I ask is it just seems easier to store the dates as >> numbers or normal dates in one field and split it apart using >> [getchars] than to do all that. :) > > > In some situations you're right, I agree with you. For those who > need to put a lot of range searches into their code, using a single > field may same more time than using the techniques I've described. > > It's just that in my experience I find a greater time saving by > storing my dates as three separate components, because for one thing > this technique *also* allows me to use generic append and replace > code that looks something like this: > > [replace > db=xxx.db&eqskudata=[sku]][formvariables][name]=[url][value][/url]&[/formvaria > bles][/replace] > > Coding with generic append and replace contexts saves me tons of > time. I'm always adding new fields or changing field names or > deleting fields in my db's as I develop my sites, and this technique > saves me from having to change all my append and replace contexts > every time I change a db field. > > And since I don't need to do range searches on my dates very often, > this approach is the best for me in many cases. But it's not the > best for everyone, nor is is the best for me in every situation. > > Still, it is something to consider: > > 1- if you find yourself spending too much time writing customized > appends and replaces, and/or ... > > 2- if you find it easier to populate form fields directly -- by using > the *entire* field -- value rather than extracting parts of the value > via getchars, middle, listwords, etc. > > :) ------------------------------------------------------------- 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/
Alan White
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:
WebDNA Solutions ... sorry! (1997)
HELP WITH DATES (1997)
Ok here is a question? (1997)
Time sort - Flushdatabases (2000)
Attn:SMSI WebDNA Developers Edition (2002)
Problems with emailer cutting off carriage returns (Crossplatform issue?) (1999)
problems with 2 tags shakur (1997)
A Global Variable (1997)
Sorting by date (1997)
Unix 4.0.2b5 (2000)
WCS Newbie question (1997)
Parameter Passing Value (2002)
Mac/network guy - newsfeed (2004)
Summing fields (1997)
Major Security Hole IIS NT (1998)
OH CRAP!!!!!- Template not found error!!! (1999)
shipping help (1998)
Forms Search Questions (1997)
Search returns all, not 20 (1997)
$Replace with [founditems] (1997)