Re: Showif date > other date

This WebDNA talk-list message is from

2004


It keeps the original formatting.
numero = 56781
interpreted = N
texte = >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]&[/formvariables][/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. :) -- 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:

    
  1. Re: Showif date > other date ( Alan White 2004)
  2. Re: Showif date > other date ( Kenneth Grome 2004)
  3. Re: Showif date > other date ( Jesse Proudman 2004)
  4. Re: Showif date > other date ( Kenneth Grome 2004)
  5. Re: Showif date > other date ( Tim Robinson 2004)
  6. Re: Showif date > other date ( Jesse Proudman 2004)
  7. Re: Showif date > other date ( Kenneth Grome 2004)
  8. Re: Showif date > other date ( "Gary Krockover" 2004)
  9. Re: Showif date > other date ( Jesse Proudman 2004)
  10. Re: Showif date > other date ( Kenneth Grome 2004)
  11. Re: Showif date > other date ( Tim Robinson 2004)
  12. Re: Showif date > other date ( Kenneth Grome 2004)
  13. Re: Showif date > other date ( Stuart Tremain 2004)
  14. Re: Showif date > other date ( Kenneth Grome 2004)
  15. Re: Showif date > other date ( Stuart Tremain 2004)
  16. Re: Showif date > other date ( Stuart Tremain 2004)
  17. Re: Showif date > other date ( Alan White 2004)
  18. Re: Showif date > other date ( devaulw@onebox.com 2004)
  19. Showif date > other date ( Alan White 2004)
>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]&[/formvariables][/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. :) -- 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:

Duplicate Cart Numbers (1999) Verisigns SDK (pay flo pro) (2002) no template caching (1997) [WebDNA] Version 7.x: webdna.ini and EmailerPrefs (2012) Which GUI HTML editors work with WC ? (1997) WC2.0 Memory Requirements (1997) 4.5 Upgrade (2003) New Site Announcement (1998) apostrophe in search item (1997) automating a POST (2002) Sku numbers (1997) Follow-up to listfiles bug report ... (2003) Snake Bites (1997) Frames and WebCat (1997) WebCatalog for guestbook ? (1997) Using Cookie for client specific info? (1997) HTML Editors (1997) passing the variable (1999) test for John (1999) [delete] problem (1997)