RE: [Arsperl-users] question regarding the query() method

SourceForge Headquarters 1320 Columbia Street Suite 310 San Diego, CA 92101 +1 (858) 422-6466

Carey,
Here are the two ways with <s> meaning single quote (')and <d> meaning
double quote ("):

Using surrounding single quotes:
<s>(\<s>Login Name\<s> =3D <d>some user<d>)<s>

Using surrounding double quotes:
<d>(<s>Login Name<s> =3D \<d>some user\<d>)<d>

I hope this helps :)

Mark

Mark Vaughan

Programmer III

=20

Direct: +1 303 802 2426

Cell: +1 303 601 4434

Fax: +1 303 802 1420

mar...@ev...

Evolving Systems, Inc.=20

9777 Mt. Pyramid Court, Suite 100, Englewood, CO USA 80112

www.evolving.com

-----Original Message-----
From: ars...@ar...
[mailto:ars...@ar...] On Behalf Of Carey Matthew
Black
Sent: Wednesday, April 27, 2005 8:50 AM
To: ars...@ar...
Subject: Re: [Arsperl-users] question regarding the query() method

Mark,

That was my first thought too. But is it very hard to read the following
Perl:

-query =3D> '("Login Name" =3D "some_user")'

Is that:

<single>(<single><single>Login Name<single><single> =3D
<double>someuser<double>)<single>

or

<single>(<double>Login Name<double> =3D <double>someuser<double>)<single>=

or=20

<single>(<double>Login Name<double> =3D
<single><single>someuser<single><single>)<single>

or

etc...

All I can say is that my cursor appears to count the values as one
double quote around the Login Name field name. (not sure if that is a
function of the many layers of email processing or not.)

But it is hard to read it that way when you know what should be there
given ARS syntax and Perl syntax. Which is why I was trying to break
down the way it should be instead of just point fixing this query
condition.

It would actually be a nice add to the ARSPerl docs to include a
search example using:

Field labels (yea.. that takes some work)
Field DB names
Field ID values

And the host of "values" too. (Char, Integer, Data/Time, Real, etc..)

Would there be any interest in having a "ARSPerl sample form" with
some sample scripts that go with it?

--=20
Carey Matthew Black
Remedy Skilled Professional (RSP)
ARS =3D Action Request System(Remedy)

Solution =3D People + Process + Tools
Fast, Accurate, Cheap.... Pick two.
Never ascribe to malice, that which can be explained by incompetence.

http://www.fellowshipchurch.com

On 4/27/05, Mark Vaughan <mva...@ev...> wrote:
> I believe the "Login Name" should be surrounded by single quotes, not
> double quotes.
>=20
> Mark Vaughan
>=20
> Programmer III
>=20
> Direct: +1 303 802 2426
>=20
> Cell: +1 303 601 4434
>=20
> Fax: +1 303 802 1420
>=20
> mar...@ev...
>=20
> Evolving Systems, Inc.
>=20
> 9777 Mt. Pyramid Court, Suite 100, Englewood, CO USA 80112
>=20
> www.evolving.com
>=20
>=20
> -----Original Message-----
> From: ars...@ar...
> [mailto:ars...@ar...] On Behalf Of the sign will be
> that life is awesome
> Sent: Wednesday, April 27, 2005 4:16 AM
> To: ars...@ar...
> Subject: [Arsperl-users] question regarding the query() method
>=20
> I'm trying to figure out how to properly use qualifiers via the OO
> query()
> method on the SHR:People form.  my code is below :
>=20
>   my @entries =3D $remedy_form->query(
>      -query =3D> '("Login Name" =3D "some_user")'
>   );
>=20
> this returns an array of field headers but no entries.
>=20
> i've verified that the 'Login Name' field exists under that name in
the
> form
>=20
> 'Login Name' =3D> 240000005
>=20
> I suspect that I'm not understanding how to properly phrase a remedy
> query
> and apologize if that is the case here.  invoking query() with no
> arguments
> properly returns all entry IDs for the form and i can properly perform
a
> get() on the form handle to retrieve the entry - i just can't seem to
> properly
> format a filter on the query itself.
>=20
> does anyone see anything boneheaded i'm doing here?  i've tried
various
> quoting
> styles for the query, such as "(\"Login Name\" =3D \"some_user\")",
'Login
> name'
> and 'Login' instead of 'Login Name' and omitting the spaces between
the
> field
> name and the '=3D' in the query as well as removing the parentheses
around
> the
> query but none of those seem to work for me.  directly using
> ars_GetListEntry
> acts identically.
>=20
> one thing i've noted ( not sure if this is something the C API deals
> with or
> not ) is that you can specify any field name in the qualifier, whether
> it
> exists or not, and no error is thrown.
>=20
> the deconstructed qualifier as returned by ars_perl_qualifier() looks
> like
>=20
> $VAR1 =3D {
>          'oper' =3D> 'rel_op',
>          'rel_op' =3D> {
>                        'left' =3D> {
>                                    'value' =3D> 'Login Name'
>                                  },
>                        'right' =3D> {
>                                     'value' =3D> 'some_user'
>                                   },
>                        'oper' =3D> '=3D=3D'
>                      }
>        };
>=20
> using the standard $all qualifier of "1=3D1" returns
>=20
> $VAR1 =3D {
>          'oper' =3D> 'rel_op',
>          'rel_op' =3D> {
>                        'left' =3D> {
>                                    'value' =3D> 1
>                                  },
>                        'right' =3D> {
>                                     'value' =3D> 1
>                                   },
>                        'oper' =3D> '=3D=3D'
>                      }
>        };
>=20
> ( using "1=3D1" returns all entries properly, as does "1<2" and other
> queries
> of that nature, so i think i've at least got the basic syntax down.
> what i'm
> probably not understanding are what types of arguments i'm supposed to
> feed
> to the qualifier constructor, tho the examples i've seen in the
mailing
> list
> seem to match up with what i'm trying to do )
>=20
> a little stumped :) - thanks much for any help!
>=20
> - tom
>=20
> -------------------------------------------------------
> SF.Net email is sponsored by: Tell us your software development plans!
> Take this survey and enter to win a one-year sub to SourceForge.net
> Plus IDC's 2005 look-ahead and a copy of this survey
> Click here to start!  http://www.idcswdc.com/cgi-bin/survey?id=3D105hix=

> _______________________________________________
> Arsperl-users mailing list
> Ars...@ar...
> https://lists.sourceforge.net/lists/listinfo/arsperl-users
> This e-mail and any attachments may be confidential and/or legally
privileged. If you have received this e-mail and you are not a named
addressee, please inform Evolving Systems TIS at ti...@ev... and
then delete the e-mail from your system. If you are not a named
addressee you must not use, disclose, distribute, copy, print or rely on
this e-mail. To ensure regulatory compliance and for the protection of
our clients and business, Evolving Systems may monitor and read e-mails
sent to and from its servers. Although Evolving Systems routinely
screens for viruses, addressees should scan this e-mail and any
attachments for viruses. Evolving Systems makes no representation or
warranty as to the absence of viruses in this e-mail or any attachments.
>=20
> Registered Office: 9777 Mt. Pyramid Ct Suite 100, Englewood, CO 80112
>=20
>=20
> -------------------------------------------------------
> SF.Net email is sponsored by: Tell us your software development plans!
> Take this survey and enter to win a one-year sub to SourceForge.net
> Plus IDC's 2005 look-ahead and a copy of this survey
> Click here to start!  http://www.idcswdc.com/cgi-bin/survey?id=105hix
> _______________________________________________
> Arsperl-users mailing list
> Ars...@ar...
> https://lists.sourceforge.net/lists/listinfo/arsperl-users
>

-------------------------------------------------------
SF.Net email is sponsored by: Tell us your software development plans!
Take this survey and enter to win a one-year sub to SourceForge.net
Plus IDC's 2005 look-ahead and a copy of this survey
Click here to start!  http://www.idcswdc.com/cgi-bin/survey?id=105hix
_______________________________________________
Arsperl-users mailing list
Ars...@ar...
https://lists.sourceforge.net/lists/listinfo/arsperl-users
This e-mail and any attachments may be confidential and/or legally privil=
eged. If you have received this e-mail and you are not a named addressee,=
 please inform Evolving Systems TIS at ti...@ev... and then delete t=
he e-mail from your system. If you are not a named addressee you must not=
 use, disclose, distribute, copy, print or rely on this e-mail. To ensure=
 regulatory compliance and for the protection of our clients and business=
, Evolving Systems may monitor and read e-mails sent to and from its serv=
ers. Although Evolving Systems routinely screens for viruses, addressees =
should scan this e-mail and any attachments for viruses. Evolving Systems=
 makes no representation or warranty as to the absence of viruses in this=
 e-mail or any attachments.=20

Registered Office: 9777 Mt. Pyramid Ct Suite 100, Englewood, CO 80112