On Sat, Jan 31, 2009 at 8:23 PM, Martin Kersten
On 30-01-2009 21:59:15 -0600, Ross Bates wrote:
As to the possibility to kill a client, perhaps we can just create a hook at the MAL level. It is worth to open up a feature request for this, I think. The hooks are available in the kernel to stop a client between individual MAL statements. It requires protocol extensions for out of bound messages, or a secure scheme to open a second connection using the same user credentials to shoot off another. Then a SQL command like "call resetClient()" could be made to do
Fabian Groffen wrote: the trick.
This does not solve the point raised, i.e. to stop instructions in the middle of their processing. This is one of the design issues why MonetDB can be fast, i.e. in the inner loop of bulk operations avoid time checking environment status.
Please don't compromise on speed. Please. I can architect and write my apps to ensure they are 'well behaved', whatever that means from MonetDB's perspective - I can't make MonetDB faster than it is :) Mark
------------------------------------------------------------------------------ This SF.net email is sponsored by: SourcForge Community SourceForge wants to tell your story. http://p.sf.net/sfu/sf-spreadtheword _______________________________________________ MonetDB-users mailing list MonetDB-users@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/monetdb-users