Really? When I made a test on 7.6.04 and 8.1 the stored procedure returned a
value, though you needed to cast it on some occasions.
https://bmccommunities.jive-mobile.com/#jive-discussion?content=%2Fapi%2Fcore%2Fv2%2Fdiscussions%2F93451
Mobilis in Mobile.
> Le 20 févr. 2014 à 21:42, Charlie Lotr
e Lotridge
Sent: Thursday, February 20, 2014 6:29 PM
To: arslist@ARSLIST.ORG<mailto:arslist@ARSLIST.ORG>
Subject: Re: FYI...SQL in Set Fields MUST begin with "SELECT"
**
Yeah, things start to get funny when you surpass the varchar limit (typically
4000 chars) and head into LOB terri
st@ARSLIST.ORG] On Behalf Of Charlie Lotridge
Sent: Thursday, February 20, 2014 3:25 PM
To: arslist@ARSLIST.ORG
Subject: Re: FYI...SQL in Set Fields MUST begin with "SELECT"
**
Interesting, thanks for this info.
I suppose this could be what's going on, but I'd think it wo
; *From:* Action Request System discussion list(ARSList) [mailto:
> arslist@ARSLIST.ORG] *On Behalf Of *Charlie Lotridge
> *Sent:* Thursday, February 20, 2014 3:25 PM
>
> *To:* arslist@ARSLIST.ORG
> *Subject:* Re: FYI...SQL in Set Fields MUST begin with "SELECT"
&g
RG
Subject: Re: FYI...SQL in Set Fields MUST begin with "SELECT"
**
Interesting, thanks for this info.
I suppose this could be what's going on, but I'd think it would be more
appropriate for ARS to error if the SQL violates some rules, rather than
operate as if the qu
LJ, the doc indeed does say that there's no syntax checking, and I did
chase it down the rabbit hole insofar as to do a SQL log to confirm that
ARS thinks it's submitting the SQL to the DB. Just to make sure, I then
cut & pasted that same SQL from the SQL log and into a query window and
executed i
the interesting thing is that what I remember of the docs state that Remedy
does no syntax checking of your SQL to determine if it's accurate, it
trusts you to do that. And because of that, I must wonder if you traced
the SQL all the way to the DB and determine what it's doing with thatto
see
ubject: Re: FYI...SQL in Set Fields MUST begin with "SELECT"
**
Interesting, thanks for this info.
I suppose this could be what's going on, but I'd think it would be more
appropriate for ARS to error if the SQL violates some rules, rather than
operate as if the query returne
Interesting, thanks for this info.
I suppose this could be what's going on, but I'd think it would be more
appropriate for ARS to error if the SQL violates some rules, rather than
operate as if the query returned no results. It's misleading. Also, the
documentation mentions nothing about any suc
I think there are security requirements for web applications and one of the
requirements is to prevent SQL injection. Not sure, but perhaps Remedy is
using something of this sort with the midtier.
I ran into something similar with iReports and Jaspersoft when I was
writing an SQL query only mine
I use quite a lot of SQL in my workflow, yet somehow never discovered this
one before. It turns out that if you're using SQL to pull data back for a
Set Fields action, it must begin with the SELECT keyword, or it won't
return any results.
For example, if you have a Set Fields with this SQL:
*SEL
11 matches
Mail list logo
