Return-Path: Delivered-To: apmail-apr-dev-archive@www.apache.org Received: (qmail 33463 invoked from network); 22 May 2006 10:12:08 -0000 Received: from hermes.apache.org (HELO mail.apache.org) (209.237.227.199) by minotaur.apache.org with SMTP; 22 May 2006 10:12:08 -0000 Received: (qmail 32096 invoked by uid 500); 22 May 2006 10:12:07 -0000 Delivered-To: apmail-apr-dev-archive@apr.apache.org Received: (qmail 32042 invoked by uid 500); 22 May 2006 10:12:06 -0000 Mailing-List: contact dev-help@apr.apache.org; run by ezmlm Precedence: bulk List-Post: List-Help: List-Unsubscribe: List-Id: Delivered-To: mailing list dev@apr.apache.org Received: (qmail 32031 invoked by uid 99); 22 May 2006 10:12:06 -0000 Received: from asf.osuosl.org (HELO asf.osuosl.org) (140.211.166.49) by apache.org (qpsmtpd/0.29) with ESMTP; Mon, 22 May 2006 03:12:06 -0700 X-ASF-Spam-Status: No, hits=-0.0 required=10.0 tests=SPF_HELO_PASS,SPF_PASS X-Spam-Check-By: apache.org Received-SPF: pass (asf.osuosl.org: domain of bojan@rexursive.com designates 203.171.74.242 as permitted sender) Received: from [203.171.74.242] (HELO beauty.rexursive.com) (203.171.74.242) by apache.org (qpsmtpd/0.29) with ESMTP; Mon, 22 May 2006 03:12:04 -0700 Received: from coyote.rexursive.com (coyote.rexursive.com [172.27.0.22]) by beauty.rexursive.com (Postfix) with ESMTP id C8BBD253BB2 for ; Mon, 22 May 2006 20:11:42 +1000 (EST) Subject: Re: [PATCH]: improved error reporting for apr_dbd_mysql.c - correct version From: Bojan Smojver To: dev@apr.apache.org In-Reply-To: <20060522064925.13980.qmail@web36710.mail.mud.yahoo.com> References: <20060522064925.13980.qmail@web36710.mail.mud.yahoo.com> Content-Type: text/plain Date: Mon, 22 May 2006 20:11:42 +1000 Message-Id: <1148292703.2146.9.camel@coyote.rexursive.com> Mime-Version: 1.0 X-Mailer: Evolution 2.6.1 (2.6.1-1.fc5.2) Content-Transfer-Encoding: 7bit X-Virus-Checked: Checked by ClamAV on apache.org X-Spam-Rating: minotaur.apache.org 1.6.2 0/1000/N On Sun, 2006-05-21 at 23:49 -0700, Alex Dubov wrote: > won't it be better to add "max_field_size=" key to the > dbd parameter string (with some sane default and 0 > defined as unlimited)? Yep, we can do that. -- Bojan