Hi!
My suggestion is to remove it, and put up a blueprint. Have folks fill
out the description on how it should be designed. We can then see if
anyone needs it. The work around for it is easy.
Cheers,
-Brian
On Apr 6, 2009, at 9:06 PM, Eric Day wrote:
Hello Drizzlers!
Does anyone see a reason to keep init_file or init_connect? As a
reminder, init_file is a local file that contains commands to run upon
server start up. It looks like this has mostly been removed already,
so this would be difficult to "keep". The init_command option is a
series of statement to execute on every connection. We're removing
multi-statement already, which means init_connect could only run a
single command unless we hacked something special back in.
Anyone feel strongly towards these things? Personally I feel this
is something best kept in the client or added back in through some
other plugin hook.
Thanks!
-Eric
_______________________________________________
Mailing list: https://launchpad.net/~drizzle-discuss
Post to : [email protected]
Unsubscribe : https://launchpad.net/~drizzle-discuss
More help : https://help.launchpad.net/ListHelp
--
_______________________________________________________
Brian "Krow" Aker, brian at tangent.org
Seattle, Washington
http://krow.net/ <-- Me
http://tangent.org/ <-- Software
_______________________________________________________
You can't grep a dead tree.
_______________________________________________
Mailing list: https://launchpad.net/~drizzle-discuss
Post to : [email protected]
Unsubscribe : https://launchpad.net/~drizzle-discuss
More help : https://help.launchpad.net/ListHelp
