Hi,
On 3 Jul 2009, at 18:44, Sheeri K. Cabral wrote:
On Fri, Jul 3, 2009 at 12:45 PM, Mark Leith<mark.le...@sun.com> wrote:
Hey Sheeri,
Re: Jeremy's comment - did you guys rip out the !include's that
MySQL
has?
AFAIK those aren't MySQL's includes, they are part of the Debian
and/or Ubuntu (I forget which) package(s).
I'd beg to differ... :)
http://dev.mysql.com/doc/refman/5.1/en/option-files.html
"It is possible to use !include directives in option files to
include other
option files and !includedir to search specific directories for
option
files. For example, to include the /home/mydir/myopt.cnf file, use
the
following directive:
!include /home/mydir/myopt.cnf
To search the /home/mydir directory and read option files found
there, use
this directive:
!includedir /home/mydir
There is no guarantee about the order in which the option files in
the
directory will be read.
Note
Currently, any files to be found and included using the !includedir
directive on Unix operating systems musthave file names ending
in .cnf. On
Windows, this directive checks for files with the .ini or .cnf
extension.
Write the contents of an included option file like any other option
file.
That is, it should contain groups of options, each preceded by a
[group]
line that indicates the program to which the options apply.
While an included file is being processed, only those options in
groups that
the current program is looking for are used. Other groups are
ignored.
Suppose that a my.cnf file contains this line:
!include /home/mydir/myopt.cnf
And suppose that /home/mydir/myopt.cnf looks like this:
[mysqladmin] force [mysqld] key_buffer_size=16M
If my.cnf is processed by mysqld, only the [mysqld] group in
/home/mydir/myopt.cnf is used. If the file is processed by
mysqladmin, only
the [mysqldamin] group is used. If the file is processed by any other
program, no options in /home/mydir/myopt.cnf are used.
The !includedir directive is processed similarly except that all
option
files in the named directory are read."
Cheers,
Mark
That's awful....particularly the "we have no idea in which order those
files are read". I thought that's what --defaults-file-extra was for.
+100 to rip it out.
I'm not sure I would consider it *that* bad. :)
What problems do you think there would be, that would rely on the
order of options files read in a whole directory? Speaking of MySQL
here, not Drizzle though.. :)
Best regards
Mark
--
Mark Leith
MySQL Regional Support Manager, Americas
Sun Microsystems, Inc., http://www.sun.com/mysql/
_______________________________________________
Mailing list: https://launchpad.net/~drizzle-discuss
Post to : drizzle-discuss@lists.launchpad.net
Unsubscribe : https://launchpad.net/~drizzle-discuss
More help : https://help.launchpad.net/ListHelp
