Re: [WebDNA] Searching for multiple bits of data in one field or use
This WebDNA talk-list message is from 2016
It keeps the original formatting.
numero = 113027
interpreted = N
texte = 615It=E2=80=99s elegant, compact and intuitive. None of which is possible =with PHP!> On Sep 30, 2016, at 12:53 PM, christophe.billiottet@webdna.us wrote:>=20> I did something like that once.>=20> A database field had to store the type of invitation we had to send to =the customer>=20> it was something like an agenda: =cocktail-press-exhibition-embassy-catalog-museum-wife=E2=80=A6>=20> Each customer could belong to several categories.>=20>=20> In one field, I stored data like 00101100=E2=80=A6=20>=20> [showif [GetChars start=3D2&end=3D2][agenda][/GetChars]=3D1] etc=E2=80=A6=>=20> you get the idea.>=20> - chris>=20>=20>=20>> 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:>>>=20>>> I searched the talk archives, though I probably didn't use the =proper search terms.>>>=20>>> 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.>>>=20>>> 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.>>>=20>>> 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.>>>=20>>> 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?>>>=20>>> I really haven't searched for multiple bits of data in a single =field before.>>>=20>>> 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>>>=20>>> 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.>>>=20>>> Thank you in advance for any recommendations as to the best way to =handle this.>>>=20>>> Dale>=20>=20>=20>=20>=20>=20> ---------------------------------------------------------> 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---------------------------------------------------------This message is sent to you because you are subscribed tothe mailing list .To unsubscribe, E-mail to: archives: http://mail.webdna.us/list/talk@webdna.usBug Reporting: support@webdna.us.
Associated Messages, from the most recent to the oldest:
615It=E2=80=99s elegant, compact and intuitive. None of which is possible =with PHP!> On Sep 30, 2016, at 12:53 PM, christophe.billiottet@webdna.us wrote:>=20> I did something like that once.>=20> A database field had to store the type of invitation we had to send to =the customer>=20> it was something like an agenda: =cocktail-press-exhibition-embassy-catalog-museum-wife=E2=80=A6>=20> Each customer could belong to several categories.>=20>=20> In one field, I stored data like 00101100=E2=80=A6=20>=20> [showif [GetChars start=3D2&end=3D2][agenda][/GetChars]=3D1] etc=E2=80=A6=>=20> you get the idea.>=20> - chris>=20>=20>=20>> 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:>>>=20>>> I searched the talk archives, though I probably didn't use the =proper search terms.>>>=20>>> 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.>>>=20>>> 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.>>>=20>>> 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.>>>=20>>> 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?>>>=20>>> I really haven't searched for multiple bits of data in a single =field before.>>>=20>>> 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>>>=20>>> 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.>>>=20>>> Thank you in advance for any recommendations as to the best way to =handle this.>>>=20>>> Dale>=20>=20>=20>=20>=20>=20> ---------------------------------------------------------> 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---------------------------------------------------------This message is sent to you because you are subscribed tothe mailing list .To unsubscribe, E-mail to: archives: http://mail.webdna.us/list/talk@webdna.usBug Reporting: support@webdna.us.
Patrick McCormick
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:
[taxRate] [TaxTotal] ? (1997)
WebCatalog and WebMerchant reviewed by InfoWorld (1997)
Need help with emailer- 2 issues (1997)
HELP WITH DATES (1997)
WebCatalog and Webstar 3.02 (1998)
can we get string variables? (1998)
WebCatalog2 Feature Feedback (1996)
[BoldWords] WebCat.acgib15Mac (1997)
ListFiles Sorting (2000)
[BULK] [WebDNA] How to test email validity? (2011)
email database file (2005)
Show shoppingcart after remove last item (1997)
Search design (1997)
Multiple prices (1997)
SKU lookup (1997)
[protect admin] (1997)
emailer w/F2 (1997)
WebCatalog2 Feature Feedback (1996)
Signal Raised Error (1997)
RE: Problems with dbcatalog.exe (1997)