Re: Negative number search

This WebDNA talk-list message is from

2000


It keeps the original formatting.
numero = 28598
interpreted = N
texte = > > > >I think webcat only deals with whole numbers, so it sees them all as >unsigned values, which makes them all 'positive' instead of some >positive and some negative. > >Here's a solution, add a NEWNUM field to the db, then write an >admin template that runs thru the db and replaces the value in the >NEWNUM field with the value of SEARCH_FIELD plus XXX. > >The value of XXX will have to be greater than the absolute value >of the smallest negative value in the db, so if the smallest >negative value is -99 then add 100. Then in your search parameters, >compare the values in the NEWNUM field instead of SEARCH_FIELD >field. > >Maybe there's an easier way, but this will work as long as you >remember to also write a value to the NEWNUM field after every >append or replace ... :) >This is where a trigger based on a database change would be very useful :-(|--------------------------------------| | Get Real Gear, Inc. | P.O. Box 11199 | Aspen, CO 81612 | fax/voice (970)544-0527 | paul@gearworld.com | http://www.gearworld.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 Associated Messages, from the most recent to the oldest:

    
  1. Re: Negative number search (Paul Fowler 2000)
  2. Re: Negative number search (Kenneth Grome 2000)
  3. Negative number search (Paul Fowler 2000)
> > > >I think webcat only deals with whole numbers, so it sees them all as >unsigned values, which makes them all 'positive' instead of some >positive and some negative. > >Here's a solution, add a NEWNUM field to the db, then write an >admin template that runs thru the db and replaces the value in the >NEWNUM field with the value of SEARCH_FIELD plus XXX. > >The value of XXX will have to be greater than the absolute value >of the smallest negative value in the db, so if the smallest >negative value is -99 then add 100. Then in your search parameters, >compare the values in the NEWNUM field instead of SEARCH_FIELD >field. > >Maybe there's an easier way, but this will work as long as you >remember to also write a value to the NEWNUM field after every >append or replace ... :) >This is where a trigger based on a database change would be very useful :-(|--------------------------------------| | Get Real Gear, Inc. | P.O. Box 11199 | Aspen, CO 81612 | fax/voice (970)544-0527 | paul@gearworld.com | http://www.gearworld.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 Paul Fowler

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:

Explorer 3.0/ Access Denied! (1997) Cart Numbers (1997) How is it done? (1998) [WebDNA] WebDNA Showcase? (2008) webcat2b12 CGI -- Date comparisons (1997) Now when I send TeaRoom Order fields it does not post in Invoice. (1997) Shopping Cart Problem (1998) security (1997) WebCatalog/Mac 2.1b2 - PIXO (1997) Emailer (1997) Problems with ^ could be solved with [REPLACE CHARACTERS] (1997) taxTotal (1997) multi-paragraph fields (1997) did I miss anything (1997) (1997) Emailer (1997) Server Traffic Simulation (1998) User / Pass in TCP connect (2007) Problem with updating to 2.1.1 (1998) off topic - dna snipets (1997)