apr-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Garrett Rooney" <roo...@electricjellyfish.net>
Subject Re: LONGs and LOBs [Was: improved error reporting for apr_dbd_mysql.c]
Date Fri, 02 Jun 2006 17:18:30 GMT
On 6/2/06, Chris Darroch <chrisd@pearsoncmg.com> wrote:
> Bojan Smojver wrote:
>
> > length:column:table:payload
> > ------ ------ ----- -------
> > ^      ^      ^     ^
> > |      |      |     +-----------> binary data, length in size
> > +------+------+-----------------> ascii
>
>    That could work for me, but if others feel it's too much of a hack,
> fair enough.
>
> > - %O - unsigned long (big L has been taken by Oracle driver already!)
>
>    A question re APR policy, really -- do we need to care about this,
> since the Oracle driver only exists in trunk, IIRC?  I'm all for
> backwards compatibility, but thought I should clarify if it's required
> in this case.

If it has never been present on a release branch we have zero need to
worry about backwards compatibility.  If someone is depending on the
code in trunk clearly they have enough clue to deal with the breakages
that can result.

-garrett

Mime
View raw message