Subject | Re: FB2.0 - Baffled by strange SQL Parse Error: Parameter name expected |
---|---|
Author | mlq97 |
Post date | 2008-01-04T18:41:37Z |
--- In firebird-support@yahoogroups.com, Svein Erling Tysvaer
<svein.erling.tysvaer@...> wrote:
I don't think this is the problem because I have just discovered that
this procedure runs OK when it is called by a certain other procedure,
but not by another.
So the problem seems to relate to the context in which it is called.
But if so, what could be causing this error message? Why would the
same update query sometimes work and other times show this parse error
when in both cases the variables seem correctly set and the
procedure's single input parameter is clearly OK?
Might this error be generated by some downstream trigger or procedure?
If so, would it show more information in the error message about what
is causing it it. Also I am not getting an exception in my
application. The procedure just seems to fail without making a fuss.
Mitch
<svein.erling.tysvaer@...> wrote:
>:V_DOCLINE_SHOWS_SUPPL_INV_COMPLETE
> Hi Mitch!
>
> I'm just guessing, but I notice that
> contains 34 characters and :V_ITEM_SUPPL_INV_COMPLETE_PCNT_2 containsThank you very much Set.
> 32. May the limit for such names be 31 characters?
>
> HTH,
> Set
>
I don't think this is the problem because I have just discovered that
this procedure runs OK when it is called by a certain other procedure,
but not by another.
So the problem seems to relate to the context in which it is called.
But if so, what could be causing this error message? Why would the
same update query sometimes work and other times show this parse error
when in both cases the variables seem correctly set and the
procedure's single input parameter is clearly OK?
Might this error be generated by some downstream trigger or procedure?
If so, would it show more information in the error message about what
is causing it it. Also I am not getting an exception in my
application. The procedure just seems to fail without making a fuss.
Mitch