report writer

Hello,
I'm testing Ingres 2006 r2 sp1 (9.1.1 (a64.lnx/103)NPTL) and I have a
problem with report writer. In ABF application I call report and in
param section I have a variable a_zarizeni:

call report(name=:report_name, param='a_zarizeni="T"')

In report I have NOT this variable declared (declare section of this
report is empty). And report writer returns error:

Reading report specifications and preparing query . . .

E_FM2001 Expected a number starting at '-1'.

E_RW140E Incompatible value 'T' cannot be assigned to variable
'a_zarizeni'.
Previous value of variable will be
retained.

Retrieving data . . .

If output of ReportWriter goes to file, I can only see these messages.
If the output goes on screen, I have to press ENTER key.

This is new behaviour of report writer and I don't know
- it's a bug and I should report it to Ingres corp.
- it was a bug and I have to find a workaround for my applications
(but we use it since ingres 6.x)

That looks like the known bug 119729. It is fixed in the catch-up patch
on top of Ingres 2006r2 SP1. Patch 13017, which is the most recent on
that platform, contains the fix.


On Fri, 2008-08-22 at 03:29 -0700, Vaclav Dohnal wrote:
> Hello,
> I'm testing Ingres 2006 r2 sp1 (9.1.1 (a64.lnx/103)NPTL) and I have a
> problem with report writer. In ABF application I call report and in
> param section I have a variable a_zarizeni:
>
> call report(name=:report_name, param='a_zarizeni="T"')
>
> In report I have NOT this variable declared (declare section of this
> report is empty). And report writer returns error:
>
> Reading report specifications and preparing query . . .
>
> E_FM2001 Expected a number starting at '-1'.
>
> E_RW140E Incompatible value 'T' cannot be assigned to variable
> 'a_zarizeni'.
> Previous value of variable will be
> retained.
>
> Retrieving data . . .
>
> If output of ReportWriter goes to file, I can only see these messages.
> If the output goes on screen, I have to press ENTER key.
>
> This is new behaviour of report writer and I don't know
> - it's a bug and I should report it to Ingres corp.
> - it was a bug and I have to find a workaround for my applications
> (but we use it since ingres 6.x)
> _______________________________________________
> Info-Ingres mailing list
> Info-Ingres-at-kettleriverconsulting.com
> http://www.kettleriverconsulting.com...fo/info-ingres