Re: Query Fails over ISTAR
Yep,
That's a problem.
Bug # for your reference : 19779, 31739
They are duplicate bugs.
Problem is
select (current year to second - cs.starttime) ..
"current" is refered to current of pca@hpvcp150:current_shift.
If you do
select current from pca@hpvcp150:current_shift cs;you will get -201.
Hopefully it will be fixed in upcoming 5.04 and 7.1
Darshan
In article <Ctx0HA.701@vcd.hp.com>, kenm@vcd.hp.com (Ken Miles) writes:
|> Why doesn't this work when issued across an Informix Star connection?
|> (I'm using two OnLine 5.02 servers).
|>
|> When I run this on the server with the actual table it works:
|>
|> select (current year to second - cs.starttime), shift
|> from
|> current_shift cs;
|>
|> (Column starttime is datetime year to second).
|>
|> I move to my second system which is attached to the first via ISTAR and
|> enter the query this way:
|>
|> select (current year to second - cs.starttime), shift
|> from
|> pca@hpvcp150:current_shift cs;
|>
|> It chokes on a "1260":
|>
|> # ^
|> # 1260: It is not possible to convert between the specified types.
|> #
|>
|> I put a set explain on and it shows this in a sqexplain file:
|>
|> QUERY:
|> ------
|> select (current year to second - cs.starttime), shift
|> from
|> pca@hpvcp150:current_shift cs
|>
|> Estimated Cost: 2
|> Estimated # of Rows Returned: 1
|>
|> 1) gap.cs: REMOTE PATH
|>
|> Remote SQL Request:
|> select (? - x0.starttime ) ,x0.shift from pca:"gap".current_shif
|> t x0
|>
|> I got past this once a few years ago but don't remember how I did it. Any
|> ideas out there?
|>
|> -Ken Miles
|> Hewlett-Packard
|> kenm@vcd.hp.com