On 3/19/20 10:25 AM, Simon Walter wrote:
...
Maybe it's gone after a year
or so of updates. I am not sure anything has changed though. Although,
as you explained about apr_dbd_get_row, maybe the apr_dbd_pselect was
written in a similar way.
Steven, I can report that I cannot replicate that pr
On 3/15/20 6:31 AM, Nick Kew wrote:
...
Is there guidance or a standard for driver writers
elsewhere?
No. Apart from our own needs, we just have occasional feedback
from users like yourself.
Just thinking aloud here, I wonder if an apr_dbd_row_alloc API
would meet your needs? I haven't th
On Sat, 14 Mar 2020 19:58:11 +
Steven Fosdick wrote:
> On Sat, 14 Mar 2020 at 02:34, Nick Kew wrote:
> > Isn't your most obvious fix simply to allocate your row
> > from your choice of pool before the first get_row?
>
> That wouldn't work. Here's the start of the dbd_oracle_get_row
> funct
On Sat, 14 Mar 2020 at 02:34, Nick Kew wrote:
> Isn't your most obvious fix simply to allocate your row
> from your choice of pool before the first get_row?
That wouldn't work. Here's the start of the dbd_oracle_get_row
function in the apr_dbd_oracle driver:
static int dbd_oracle_get_row(apr_po
> On 14 Mar 2020, at 02:23, Nick Kew wrote:
>
> [chop]
Damn, shouldn't be posting while down with a lurgy.
Isn't your most obvious fix simply to allocate your row
from your choice of pool before the first get_row?
Or am I still missing something?
--
Nick Kew
> On 14 Mar 2020, at 01:18, Steven Fosdick wrote:
>while (!apr_dbd_get_row(drv, rpool, res, &row, -1)) {
>for (int c = 0; c < cols; c++) {
>const char *name = apr_dbd_get_name(drv, res, c);
>const char *value = apr_dbd_get_en
