This works for me. I'm gaiottino btw. The only reservation I have is that I found this issue when I realized that upgrading from 3.0.6 broke local infile sql and the option to activate this again is not valid for the [client] config as this prevents you from using for example mysqldump. That's why I proposed that [sequel] use it's own group.
Another solution may be to put the line conn.options(Mysql::OPT_LOCAL_INFILE, "client") back in so that local infile always works again but still allow other configuration to be read from the [client] group. So far it's only the option local-infile=1 that I've found causes an issue. On Apr 1, 6:00 pm, Jeremy Evans <[email protected]> wrote: > On Apr 1, 9:57 am, Michael Lang <[email protected]> wrote: > > > Seems to me the better approach is to keep the default "client" and pass in > > an option that can potentially override it and thus maintain backwards as > > well as widest compatibility. I personally rarely change the mysql config > > files unless its to move the socket file elsewhere and even then, that's a > > rarity these days and I have definitely never added a "sequel" group to any > > of mine. > > > How about simply changing line #97: > > > conn.options(Mysql::READ_DEFAULT_GROUP, opts[:config] || "client") > > > Then, if somebody needs to use a different group, they can override with > > :config => "sequel" or whatever suits their needs. > > That does seems like a better solution to me, though I'd probably > use :config_default_group as the option key. > > Jeremy -- You received this message because you are subscribed to the Google Groups "sequel-talk" group. To post to this group, send email to [email protected]. To unsubscribe from this group, send email to [email protected]. For more options, visit this group at http://groups.google.com/group/sequel-talk?hl=en.
