Re: [WebDNA] Searching for multiple bits of data in one field or use multiple fields for each bit of data?
This WebDNA talk-list message is from 2016
It keeps the original formatting.
numero = 113026
interpreted = N
texte = 614 I did something like that once. A database field had to store the type of invitation we had to send to = the customer it was something like an agenda: = cocktail-press-exhibition-embassy-catalog-museum-wife=E2=80=A6 Each customer could belong to several categories. In one field, I stored data like 00101100=E2=80=A6=20 [showif [GetChars start=3D2&end=3D2][agenda][/GetChars]=3D1] etc=E2=80=A6 you get the idea. - chris > On Sep 30, 2016, at 20:23, dale
wrote: >=20 > Hello Patrick, >=20 > Interesting idea. I've not tried that in the past. Any possible = examples of how you would do that? It definitely sounds like a good way = to go. >=20 > Thank you, >=20 > Dale >=20 > On Fri, Sep 30, 2016 at 10:06 AM, Patrick McCormick = wrote: > I think you should store each alarm condition as one bit in a binary = number long enough to accommodate all alarm conditions. Then, each base = 10 value of that binary number represents a unique alarm or combination = of alarms. >=20 >=20 > > On Sep 29, 2016, at 6:42 PM, dale wrote: > > > > I searched the talk archives, though I probably didn't use the = proper search terms. > > > > The system for work I will be building is kind of like a fleet = management system. It isn't tracking the vehicles, but a computer and = camera system we install and maintain on the vehicles. > > > > One of the things I wanted to do is to put the various problem codes = (e.g. C HD PCB SSD) in a single field separated by a comma. My thought = is that it would be easier to search for systems that had a specific = problem and/or combination of problems. > > > > As it has been a few years since coding in WebDNA, I'm not sure if = this is the best way or not. We do come up with new codes as time passes = based on new systems. > > > > Would you recommend using a single field for various codes as listed = above where I would only have to change the searches or using a hdr file = to make adding additional codes a bit easier? > > > > I really haven't searched for multiple bits of data in a single = field before. > > > > Ways in which this would be used: > > Someone checking the systems remotely would enter the code for that = system > > Techs fixing the system would need to remove the appropriate codes = for what they fixed > > Running reports to determine which systems have certain issues > > > > Additionally, each time the techs create a service ticket to make a = repair, I will save a copy of the the status of the system along with = their notes in a history database so we will have a life-cycle of the = system. Those records would only be editable by certain admin accounts. > > > > Thank you in advance for any recommendations as to the best way to = handle this. > > > > Dale --------------------------------------------------------- This message is sent to you because you are subscribed to the mailing list . To unsubscribe, E-mail to: archives: http://mail.webdna.us/list/talk@webdna.us Bug Reporting: support@webdna.us .
Associated Messages, from the most recent to the oldest:
614 I did something like that once. A database field had to store the type of invitation we had to send to = the customer it was something like an agenda: = cocktail-press-exhibition-embassy-catalog-museum-wife=E2=80=A6 Each customer could belong to several categories. In one field, I stored data like 00101100=E2=80=A6=20 [showif [GetChars start=3D2&end=3D2][agenda][/GetChars]=3D1] etc=E2=80=A6 you get the idea. - chris > On Sep 30, 2016, at 20:23, dale wrote: >=20 > Hello Patrick, >=20 > Interesting idea. I've not tried that in the past. Any possible = examples of how you would do that? It definitely sounds like a good way = to go. >=20 > Thank you, >=20 > Dale >=20 > On Fri, Sep 30, 2016 at 10:06 AM, Patrick McCormick = wrote: > I think you should store each alarm condition as one bit in a binary = number long enough to accommodate all alarm conditions. Then, each base = 10 value of that binary number represents a unique alarm or combination = of alarms. >=20 >=20 > > On Sep 29, 2016, at 6:42 PM, dale wrote: > > > > I searched the talk archives, though I probably didn't use the = proper search terms. > > > > The system for work I will be building is kind of like a fleet = management system. It isn't tracking the vehicles, but a computer and = camera system we install and maintain on the vehicles. > > > > One of the things I wanted to do is to put the various problem codes = (e.g. C HD PCB SSD) in a single field separated by a comma. My thought = is that it would be easier to search for systems that had a specific = problem and/or combination of problems. > > > > As it has been a few years since coding in WebDNA, I'm not sure if = this is the best way or not. We do come up with new codes as time passes = based on new systems. > > > > Would you recommend using a single field for various codes as listed = above where I would only have to change the searches or using a hdr file = to make adding additional codes a bit easier? > > > > I really haven't searched for multiple bits of data in a single = field before. > > > > Ways in which this would be used: > > Someone checking the systems remotely would enter the code for that = system > > Techs fixing the system would need to remove the appropriate codes = for what they fixed > > Running reports to determine which systems have certain issues > > > > Additionally, each time the techs create a service ticket to make a = repair, I will save a copy of the the status of the system along with = their notes in a history database so we will have a life-cycle of the = system. Those records would only be editable by certain admin accounts. > > > > Thank you in advance for any recommendations as to the best way to = handle this. > > > > Dale --------------------------------------------------------- This message is sent to you because you are subscribed to the mailing list . To unsubscribe, E-mail to: archives: http://mail.webdna.us/list/talk@webdna.us Bug Reporting: support@webdna.us .
christophe.billiottet@webdna.us
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:
CERT Advisory on malicious scripts (2000)
[protect] error page (1997)
problems with 2 tags (1997)
Updating checkboxes made easy !!! (1998)
Country & Ship-to address & other fields ? (1997)
Re2: frames & carts (1997)
Nav. 4 probs with cart (1997)
JavaScript form question (2001)
[OT] Am I an Idiot? (2004)
(2000)
Netscape 3.01 can't see db in form (1997)
Cart Question (1998)
syntax question, not in online refernce (1997)
can WC render sites out? (1997)
Date Formats (1997)
Some Questions (1997)
Bugs in IE 6.0 ? (2003)
WebCat2 beta 11 - new prefs ... (1997)
Emailer setup (1997)
OT: anyone know how to prevent image hijacking with Apache? (2002)