My bad, it made wrong syntax
[/!]group1field=3Ddb_progress&group2field=3Ddb_progress&[!]
[/!]negroup1datarq=3D8&negroup2datarq=3D10&[!]
Fixed it.
Thanks a lot Terry
/Palle
> On 6. feb. 2016, at 18.56, Palle Bo Nielsen <powerpalle@powerpalle.dk> wrote:
>
> That=E2=80=99t new territory for me.
>
> So I tried like this but it did not work
>
> [/!]group1field=3Dprogressdata&group2field=3Dprogressdata&[!]<=br>> [/!]negroup1datarq=3D8&negroup2datarq=3D10&[!]
>
> Actually all 8 and 10 results where included.
>
> Is it supposed to be
>
> [/!]group1field=3Dprogressdata&group2field=3Dprogressdata&[!]<=br>> or
> [/!]group1=3Dprogressdata&group2=3Dprogressdata&[!]
>
>
> /Palle
>
>
>> On 6. feb. 2016, at 17.10, Terry Wilson <terry@terryfic.com> wrote:
>>
>> Use a group field to search two different ways on one field. There= are two ways to use group: to search multiple fields at once, and to searc=h one field in two different ways. Here's from the docs:
>>
>> "Searching the same field in two different ways
>>
>> Sometimes you need to compare a value two different ways, but the =search parameter will only accept a fieldname once. In this case, create tw=o group fields like this:
>>
>> group1field=3Dzipcode&group2field=3Dzipcode"
>>
>>
>> Another solution would be to use
>>
>> [founditems]
>> [hideif [db_progressdata]=3D8]
>>
>> ---results---
>>
>> [/hideif]
>> [/founditems]
>>
>> In the above, if you need to count them up, [numfound] won't w=ork, so add a counter to the results area
>>
>> Terry W
>>
>>
>> On Feb 6, 2016, at 7:12 AM, Palle Bo Nielsen <powerpalle@powerpalle.dk> wrote:
>>
>>> Hi all
>>>
>>> The code below works fine, but I need to set the <db_progre=ss> to filter two values. Right now it deselects any field with the valu=e 10. I need for it to deselect any field with the numbers 8 and 10.
>>>
>>> So I thought it could look like this example, but I won=E2=80==99t work - how is that?
>>>
>>> [/!]nedb_progressdatarq=3D8,10&[!]
>>>
>>>
>>>
>>> =E2=80=94 original code=C2=A0 which works with the value 10 --=
>>>
>>> [search db=3D/somepath/some.db&[!]
>>>
>>> [/!]eqdb_publishdatarq=3D1&[!]
>>> [/!]nedb_progressdatarq=3D10&[!]=C2=A0 =C2=A0 =C2=A0 =C2==A0 =C2=A0<<<<<< ISSUE
>>> [/!]max=3D[issue_search_length]&[!]
>>>
>>> [/!][showif [direction]^direction]dedb_indexSort=3D1&[/sho=wif][!]
>>> [/!][showif [direction]=3Dhead]asdb_headlinesort=3D1&[/sho=wif][!]
>>> [/!][showif [direction]=3Didid]dedb_indexsort=3D1&[/showif=][!]
>>> [/!][showif [direction]=3Dprog]dedb_progresssort=3D1&[/sho=wif][!]
>>> [/!][showif [direction]=3Dprio]asdb_prioritysort=3D1&[/sho=wif][!]
>>> [/!][showif [direction]=3Dtype]dedb_typesort=3D1&[/showif]=[!]
>>> [/!][showif [direction]=3Dcate]dedb_categorysort=3D1&[/sho=wif][!]
>>>
>>> [/!]db_indextype=3Dnum&[!]
>>> [/!]allreqd=3DT&[!]
>>> [/!]AllHit=3D1[!]
>>> [/!]startat=3D[start]]
>>>
>>> [founditems]--------------------------------------------------=-------
>>> This message is sent to you because you are subscribed to
>>> the mailing list <talk@we=bdna.us>.
>>> To unsubscribe, E-mail to: <talk-leave@webdna.us>
>>> archives: http://mail.webdna.us/list/talk@webd=na.us
>>> Bug Reporting: support@we=bdna.us
>>
>> ---------------------------------------------------------
>> This message is sent to you because you are subscribed to
>> the mailing list <talk@webdna=..us>.
>> To unsubscribe, E-mail to: <talk-leave@webdna.us>
>> archives: http://mail.webdna.us/list/talk@webdna.u=s
>> Bug Reporting: support@webdna=..us
>
> ---------------------------------------------------------
> This message is sent to you because you are subscribed to
> the mailing list <talk@webdna.us<=/a>>.
> To unsubscribe, E-mail to: <talk-leave@webdna.us>
> archives: http://mail.webdna.us/list/talk@webdna.us
> Bug Reporting: support@webdna.us<=/a>
---------------------------------------------------------
This message is sent to you because you are subscribed to
the mailing list <talk@webdna.us&g=t;.
To unsubscribe, E-mail to: <talk=-leave@webdna.us>
archives: http://mail.webdna.us/list/talk@webdna.us
Bug Reporting: support@webdna.us
|
My bad, it made wrong syntax
[/!]group1field=3Ddb_progress&group2field=3Ddb_progress&[!]
[/!]negroup1datarq=3D8&negroup2datarq=3D10&[!]
Fixed it.
Thanks a lot Terry
/Palle
> On 6. feb. 2016, at 18.56, Palle Bo Nielsen <powerpalle@powerpalle.dk> wrote:
>
> That=E2=80=99t new territory for me.
>
> So I tried like this but it did not work
>
> [/!]group1field=3Dprogressdata&group2field=3Dprogressdata&[!]<=br>> [/!]negroup1datarq=3D8&negroup2datarq=3D10&[!]
>
> Actually all 8 and 10 results where included.
>
> Is it supposed to be
>
> [/!]group1field=3Dprogressdata&group2field=3Dprogressdata&[!]<=br>> or
> [/!]group1=3Dprogressdata&group2=3Dprogressdata&[!]
>
>
> /Palle
>
>
>> On 6. feb. 2016, at 17.10, Terry Wilson <terry@terryfic.com> wrote:
>>
>> Use a group field to search two different ways on one field. There= are two ways to use group: to search multiple fields at once, and to searc=h one field in two different ways. Here's from the docs:
>>
>> "Searching the same field in two different ways
>>
>> Sometimes you need to compare a value two different ways, but the =search parameter will only accept a fieldname once. In this case, create tw=o group fields like this:
>>
>> group1field=3Dzipcode&group2field=3Dzipcode"
>>
>>
>> Another solution would be to use
>>
>> [founditems]
>> [hideif [db_progressdata]=3D8]
>>
>> ---results---
>>
>> [/hideif]
>> [/founditems]
>>
>> In the above, if you need to count them up, [numfound] won't w=ork, so add a counter to the results area
>>
>> Terry W
>>
>>
>> On Feb 6, 2016, at 7:12 AM, Palle Bo Nielsen <powerpalle@powerpalle.dk> wrote:
>>
>>> Hi all
>>>
>>> The code below works fine, but I need to set the <db_progre=ss> to filter two values. Right now it deselects any field with the valu=e 10. I need for it to deselect any field with the numbers 8 and 10.
>>>
>>> So I thought it could look like this example, but I won=E2=80==99t work - how is that?
>>>
>>> [/!]nedb_progressdatarq=3D8,10&[!]
>>>
>>>
>>>
>>> =E2=80=94 original code=C2=A0 which works with the value 10 --=
>>>
>>> [search db=3D/somepath/some.db&[!]
>>>
>>> [/!]eqdb_publishdatarq=3D1&[!]
>>> [/!]nedb_progressdatarq=3D10&[!]=C2=A0 =C2=A0 =C2=A0 =C2==A0 =C2=A0<<<<<< ISSUE
>>> [/!]max=3D[issue_search_length]&[!]
>>>
>>> [/!][showif [direction]^direction]dedb_indexSort=3D1&[/sho=wif][!]
>>> [/!][showif [direction]=3Dhead]asdb_headlinesort=3D1&[/sho=wif][!]
>>> [/!][showif [direction]=3Didid]dedb_indexsort=3D1&[/showif=][!]
>>> [/!][showif [direction]=3Dprog]dedb_progresssort=3D1&[/sho=wif][!]
>>> [/!][showif [direction]=3Dprio]asdb_prioritysort=3D1&[/sho=wif][!]
>>> [/!][showif [direction]=3Dtype]dedb_typesort=3D1&[/showif]=[!]
>>> [/!][showif [direction]=3Dcate]dedb_categorysort=3D1&[/sho=wif][!]
>>>
>>> [/!]db_indextype=3Dnum&[!]
>>> [/!]allreqd=3DT&[!]
>>> [/!]AllHit=3D1[!]
>>> [/!]startat=3D[start]]
>>>
>>> [founditems]--------------------------------------------------=-------
>>> This message is sent to you because you are subscribed to
>>> the mailing list <talk@we=bdna.us>.
>>> To unsubscribe, E-mail to: <talk-leave@webdna.us>
>>> archives: http://mail.webdna.us/list/talk@webd=na.us
>>> Bug Reporting: support@we=bdna.us
>>
>> ---------------------------------------------------------
>> This message is sent to you because you are subscribed to
>> the mailing list <talk@webdna=..us>.
>> To unsubscribe, E-mail to: <talk-leave@webdna.us>
>> archives: http://mail.webdna.us/list/talk@webdna.u=s
>> Bug Reporting: support@webdna=..us
>
> ---------------------------------------------------------
> This message is sent to you because you are subscribed to
> the mailing list <talk@webdna.us<=/a>>.
> To unsubscribe, E-mail to: <talk-leave@webdna.us>
> archives: http://mail.webdna.us/list/talk@webdna.us
> Bug Reporting: support@webdna.us<=/a>
---------------------------------------------------------
This message is sent to you because you are subscribed to
the mailing list <talk@webdna.us&g=t;.
To unsubscribe, E-mail to: <talk=-leave@webdna.us>
archives: http://mail.webdna.us/list/talk@webdna.us
Bug Reporting: support@webdna.us
DOWNLOAD WEBDNA NOW!
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...