apr-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Garrett Rooney" <roo...@electricjellyfish.net>
Subject Re: [PATCH]: DBD prepared statement arguments rework for 1.2.x
Date Mon, 25 Sep 2006 01:16:22 GMT
On 9/24/06, Bojan Smojver <bojan@rexursive.com> wrote:
> Quoting Garrett Rooney <rooneg@electricjellyfish.net>:
> > I guess I'm not seeing how adding a bunch of new format strings isn't
> > changing anything...  Am I just misunderstanding how the patch works?
> > It looks like it replaces the existing format string parsing with all
> > new parsing.  Is it just that the new parsing is a superset of the
> > existing stuff?
> Yes, that's how it should work - as a superset. There are new format
> strings that we would support, apart from already supported ones,
> which were %s and %d (only in PostgreSQL ATM). The %s and %d would
> remain with the same meaning and anything that isn't specifically
> defined would still be interpreted as %s (i.e. VARCHAR), just like it
> is now (although, I find that to be a bad idea - we should stick to
> explicit meanings).
> The parsing would get moved out of the drivers, so that we can rely on
> it being identical for all drivers. Which would make things a bit more
> consistent.

Ok, in that case it sounds good to me.


View raw message