I am having problems with the db_fetch_next routine and Postgres.
I can’t see any problem with my code that calls it, and as far as I can tell the problem appears to be in the db_postgres_fetch_result routine. On the first invocation of db_postgres_fetch_result it allocates a result structure and gives me the first 5 rows of the 198 that match my query after calling db_postgres_convert_rows. On the 2nd invocation it fails to retrieve the next 5 rows because CON_RESULT(_con) is NULL ! Anyone got any suggestions?
Paul Pankhurst Engineering Director Crocodile RCS Ltd
Tel: 01489 668620 DDI: 01489 668622 www.crocodile-rcs.com
Hello,
On 12/13/11 11:40 AM, Paul Pankhurst wrote:
I am having problems with the db_fetch_next routine and Postgres. I can't see any problem with my code that calls it, and as far as I can tell the problem appears to be in the db_postgres_fetch_result routine. On the first invocation of db_postgres_fetch_result it allocates a result structure and gives me the first 5 rows of the 198 that match my query after calling db_postgres_convert_rows. On the 2nd invocation it fails to retrieve the next 5 rows because CON_RESULT(_con) is NULL ! Anyone got any suggestions?
can you doublecheck and see if you don't call free_result() before fetching the next rows? If you run with debug=3, if there is a free_result, you should see the log message from:
LM_DBG("PQclear(%p) result set\n", CON_RESULT(_con))
Cheers, Daniel