[Mono-bugs] [Bug 78281][Maj] Changed - timeout and expire fields in SessionSQLServerHandler

[bugzilla-daemon at bugzilla.ximian.com]

Please do not reply to this email- if you want to comment on the bug, go to the
URL shown below and enter your comments there.

Changed by babal at via.ecp.fr.

http://bugzilla.ximian.com/show_bug.cgi?id=78281

--- shadow/78281	2006-05-15 19:27:33.000000000 -0400
+++ shadow/78281.tmp.2458	2006-05-16 01:49:06.000000000 -0400
@@ -62,6 +62,24 @@
    offline, for example with Mono's dbsessmgr tool.
 
 2. NOW() doesn't work with all databases supported by
    SessionSQLServerHandler.
 
 
+
+------- Additional Comments From babal at via.ecp.fr  2006-05-16 01:49 -------
+1. I was'nt too sure about this either, but I chose this solution
+   rather than simply selecting valid sessions because the infinite
+   growth of the table could lead to a potential denial of service,
+   unless the administrator is aware he/she must do some cleanup.
+
+   (Maybe some documentation would do the trick, but it bothers me
+   to require the administrator to take some action to keep the
+   system secure, even if I know that there are other ways to
+   exploit that breach anyway)
+
+   Anyway, the next patch corrects this.
+
+2. Is there an explicit list of supported databases ? If so, do they
+   support an other keyword (CURRENT_TIMESTAMP ?) ? I could modify my
+   patch to revert to a client side computation, but if there is a
+   way to avoid it...