Timo Sirainen wrote:
>> I added it to v1.1, but I don't know if I should add it to v1.0. At
>> least it shouldn't do it by default to make sure that no existing
>> installations break accidentally..
>
> Hmm. And I think I'll change the settings to option_file and
> option_group. They make more sen
On Tue, 2008-01-01 at 19:39 +0200, Timo Sirainen wrote:
> On Tue, 2008-01-01 at 18:23 +0100, Luca Longinotti wrote:
> > Timo Sirainen wrote:
> > > On 31.12.2007, at 15.23, Luca Longinotti wrote:
> > >
> > >> +mysql_options(conn->mysql, MYSQL_READ_DEFAULT_GROUP, "client");
> > >
> > > Is "clie
On Tue, 2008-01-01 at 18:23 +0100, Luca Longinotti wrote:
> Timo Sirainen wrote:
> > On 31.12.2007, at 15.23, Luca Longinotti wrote:
> >
> >> +mysql_options(conn->mysql, MYSQL_READ_DEFAULT_GROUP, "client");
> >
> > Is "client" always the correct group to read? Would there be any point
> > in
Timo Sirainen wrote:
> On 31.12.2007, at 15.23, Luca Longinotti wrote:
>
>> +mysql_options(conn->mysql, MYSQL_READ_DEFAULT_GROUP, "client");
>
> Is "client" always the correct group to read? Would there be any point
> in making this configurable?
>
Well, "client" is the default group. It can
On 31.12.2007, at 15.23, Luca Longinotti wrote:
+ mysql_options(conn->mysql, MYSQL_READ_DEFAULT_GROUP, "client");
Is "client" always the correct group to read? Would there be any
point in making this configurable?
PGP.sig
Description: This is a digitally signed message part
I hope this ml is the right place to send this...
Anyway, I'd very much like for the MySQL backend to call mysql_options,
so that it'll read the settings defined in MySQL's my.cnf under the
[client] section. This allows to set a whole slew of MySQL specific
settings for the MySQL connection, for ex
