Mailing-List: contact dev-help@apr.apache.org; run by ezmlm
Precedence: bulk
Received-SPF: pass (nike.apache.org: local policy)
MIME-Version: 1.0
In-Reply-To: <1255145394.4698.44.camel@shrek.rexursive.com>
References: <e8349cf60910010320y59110ca8vd152d2318a8e6941@mail.gmail.com>
	<1255145394.4698.44.camel@shrek.rexursive.com>
From: Kevac Marko <marko@kevac.org>
Date: Sat, 10 Oct 2009 10:55:54 +0400
Message-ID: <e8349cf60910092355s3b4584c3r70a9b73f903ff579@mail.gmail.com>
Subject: Re: [PATCH] fix for max_length field to be populated for prepared
	statements
To: Bojan Smojver <bojan@rexursive.com>
Cc: dev@apr.apache.org
Content-Type: text/plain; charset=UTF-8

Well, yes. It is not used in apr_dbd_mysql.

For our project we are using apr_dbd, which don't have enough features
yet for our needs.

For example, we are using information from MYSQL_FIELD structure,
which, again, is not available from apr_dbd.h functions. Anyway, with
some dark "hack" magic one can access it (of course in non-portable
manner).

Variable max_length in MYSQL_FIELD is not populated for prepared
statements without flag in patch. This is why we need it.

Maybe this violates some kind of "not needed feature" rule. If so,
than what is your advice? Thanks.

On Sat, Oct 10, 2009 at 7:29 AM, Bojan Smojver <bojan@rexursive.com> wrote:
> On Thu, 2009-10-01 at 14:20 +0400, Kevac Marko wrote:
>> Without this attribute set, max_length field is not filled for
>> prepared statements.
>
> I'm not seeing use of max_length in the driver. Can you elaborate a bit
> more what this is for?
>
> >From what I can see we rely on buffer_length for prepared stuff, no?
>
> --
> Bojan
>
>


-- 
Marko Kevac
Sent from Moscow, Mow, Russia