Olivier Doucet was heard to say:
> Hello everyone,
>
> I'm following a quite old topic about libdbi speed issues.
> I was able to track the cause of these issues : The major problem is
> how libdbi goes from one row to another.
>
> RRDTool (the tool that used libdbi and that I was inspecting) is
Hi Markus,
2013/1/8 Markus Hoenicka :
> We could modify the driver function
> dbd_goto_row() by passing both the wanted row index rowidx and the
> current row index currowidx(which libdbi keeps track of anyway).
This is one way to fix the problem, I agree. Unfortunately my level in
C is too low t
Olivier Doucet was heard to say:
> Hi Markus,
>
> 2013/1/8 Markus Hoenicka :
>> We could modify the driver function
>> dbd_goto_row() by passing both the wanted row index rowidx and the
>> current row index currowidx(which libdbi keeps track of anyway).
>
> This is one way to fix the problem, I a
Markus,
Would it be worth the ugliness of a module-global variable to bury the
value of the row index used in the previous call to dbd_mysql.c::dbd_goto_row()
inside the MySQL driver itself, side-stepping the function signature change
for other drivers? The benefit of avoiding the API change may
Mike Rylander was heard to say:
> Markus,
>
> Would it be worth the ugliness of a module-global variable to bury the
> value of the row index used in the previous call to
> dbd_mysql.c::dbd_goto_row()
> inside the MySQL driver itself, side-stepping the function signature change
> for other dri
Markus Hoenicka writes:
> Hi,
>
> I'll have to read the code again a little more thoroughly, but to the
> best of my knowledge libdbi emulates MySQL's approach to retrieving
> rows from result sets. In order to walk through the rows of e.g. a
> PostgreSQL result set you have to retriev
