On Tue, Apr 07, 2009 at 11:03:40AM -0400, Ronald Bradford wrote: > I have seen this in use with clients. > People sometimes use MEMORY tables for caching, and have init_file in place > for loading on a server restart.
I'm aware of this too. However... would this purpose be better served by being able to have auth only let one connection in to begin with? i.e. your init_file becomes a sep program that does what it needs to. It could then make the decision based on a number of things if the server can continue to start (i.e. accept other connections). You could then do all sorts of funky things like load the MEMORY tables from another host. > Re init_connect, what is really lacking is ability for auditing of > successful and unsuccessful connections. You can log just success with > this, and I agree with Roland, some hook for disconnect is valuable for > this purpose of auditing. Sounds like a plugin that executes SQL in these cases... but the hooks are there for other plugins to do whatever. -- Stewart Smith _______________________________________________ Mailing list: https://launchpad.net/~drizzle-discuss Post to : [email protected] Unsubscribe : https://launchpad.net/~drizzle-discuss More help : https://help.launchpad.net/ListHelp
