I agree that this is a bug in JasperReports. I've been stepping throgh
their code to determine where the paramter type is set to
'java.lang.String', but have not yet figured out how their Java API will
allow me to override that with 'java.lang.Integer' or something more
appropriate.
If I figu
"Jason L. Buberel" <[EMAIL PROTECTED]> writes:
> For reference, when using JasperReports .jrxml files as the basis for
> the query, I only had to do to the following to 'force' postgres to
> treat the jasper report parameter as a number and not text, thereby
> allowing the correct index to be us
Tom-right-as-usual:
Yep - you were right about the query plan for the prepared statement (a
sequential scan of the table) differed a bit from the directly-executed
version :)
For reference, when using JasperReports .jrxml files as the basis for
the query, I only had to do to the following to
"Jason L. Buberel" <[EMAIL PROTECTED]> writes:
> In my syslog output, I see entries indicating that the
> JDBC-driver-originated query on a table named 'city_summary' are taking
> upwards of 300 seconds:
> Oct 1 18:27:47 srv3 postgres-8.2[1625]: [12-1]
> LOG: duration: 307077.037 ms execute S
I'm hoping that someone on the list can help me understand an apparent
discrepancy in the performance information that I'm collecting on a
particularly troublesome query.
The configuration: pg-8.2.4 on RHEL4. log_min_duration_statement = 1m.
In my syslog output, I see entries indicating that t
