Quoting Bojan Smojver <[EMAIL PROTECTED]>:

What should happen instead for SQLite3 is
apr_pstrdup of column names inside dbd_sqlite3_select (i.e. at present,
this part of the code in the driver is buggy, but since it doesn't get
used, nobody noticed yet).

More on this point - the new code should introduce column names (probably char **) in the result set, so that memory for column names gets allocated only once (no need to burden each row with copies of columns names). Then the columns' name members can just point to that.

--
Bojan

Reply via email to