Subject Re: [firebird-support] Re: Unsupported Column Type: 0
Author Helen Borrie
At 05:33 PM 9/05/2005 +0000, you wrote:
>Hi Helen,
>
><snip>
>
> > Well, you do have some ambiguities between the main query and the
>subquery,
> > but I suspect the cause of the error you are seeing is that you are
>using
> > IB_SQL's DSQL interface to submit this request and you have
>forgotten to
> > uncheck the Params checkbox.
> >
>
>Could you point out the ambiguities?

> for
> select memberid, <---------
> memberwantsjot
> from organizationmember
> where organizationid = new.organizationid and
> memberwantsemails = 1 and
> memberstatus >= 1 and
> memberid not in (select memberid <-------
> from emailjobstats
> where emailjobid = new.emailjobid)
> into :memid, :wwantsjot
> do

for
select om.memberid,
om.memberwantsjot
from organizationmember om
where om.organizationid = new.organizationid and
om.memberwantsemails = 1 and
om.memberstatus >= 1 and
om.memberid not in (select ejs.memberid
from emailjobstats ejs
where ejs.emailjobid = new.emailjobid)
into :memid, :wwantsjot
do

>I'm currently using Marathon
>v3.0.0.50 RC1 (Using IBObjects v4.5x) as such I'm not using IB_SQL.

Ah, but it's the same data access interface. So look for a checkbox
somewhere in the DSQL tool that you are using, where you can turn parameter
detection off and on. The error message is thrown when the editor tries to
treat :variable as if it is a parameter.

>If it's something I've got wrong in my trigger code I can fix that
>straight away.

The ambiguity should throw its own exception in Fb 1.5. In Fb 1.0, it only
throws a warning, so you don't see an exception.

>But if it's not I need to track it down and fix it in
>the Marathon code. So knowing what I've done wrong in the trigger
>code would be a very good place for me to start.

Sure: But this is an IBO exception, being thrown from the editor. It's
not an engine exception.

./heLen