Thank you Serge, you are always alert. It's very nice and clear the
theory, but below is the result of empirical research :)
- Using READ ONLY in the cursor declaration did not solve the problem
(try it).
- Using the "for myrow as select..." syntax you proposed solved the
problem, both with **AND WITHOUT** read-only declaration.
PD: I'm not using MTK, I'm using a home-made translator (using C, Lex,
Yacc, etc.). I've already programmed one for Informix->SQL Server and
one for Informix->Oracle, with full stored-procedure translation and
mimic of Informix behaviours. We code everything in Informix and use it
to port our projects automatically (tons of code).
> Thank you Serge, you are always alert. It's very nice and clear the
> theory, but below is the result of empirical research :)
>
> - Using READ ONLY in the cursor declaration did not solve the problem
> (try it).
Hmm, der may be more variables involved here.
> - Using the "for myrow as select..." syntax you proposed solved the
> problem, both with **AND WITHOUT** read-only declaration.
Even if you extend your example to more rows? If yes I really want to
try it because that would be AI.
> PD: I'm not using MTK, I'm using a home-made translator (using C, Lex,
> Yacc, etc.). I've already programmed one for Informix->SQL Server and
> one for Informix->Oracle, with full stored-procedure translation and
> mimic of Informix behaviours. We code everything in Informix and use it
> to port our projects automatically (tons of code).
.. presumably not cheap. If you have improvement proposals for the MTK
feel free to send a note to mtk@us.ibm.com
The goal is not to burden customers with this.
Cheers
Serge

Signature
Serge Rielau
DB2 SQL Compiler Development
IBM Toronto Lab
Gustavo Randich - 25 Feb 2005 19:54 GMT
>> - Using the "for myrow as select..." syntax you proposed solved the
>> problem, both with **AND WITHOUT** read-only declaration.
>
> Even if you extend your example to more rows? If yes I really want to
> try it because that would be AI.
>From over 4000 rows it begins to "lose" rows even with READ ONLY. To
try it I simply copy-paste the INSERTs to produce 4700+ rows of data.
In the meantime I'm not so worried because Informix 7.x loses rows at a
much greater rate! It seems like static cursors are an impossible
thing.