don't enlist sql command cache dependencies"

Hi,

We're having some trouble with SysCache2's sql command cache dependencies when not using MSSQL. We are aware of the fact that any other db drivers are incompatible with this but our NHibernate configuration is setup up dynamically - some clients use MySQL, some clients use MSSQL. Since it's one deployed webapp, we do not wish to alter the web.config to remove  the configured <cacheRegion/> tags for clients who happen to not use MSSQL. 

This patch simply does not enlist dependency objects if it sees that your connection string is "incompatible" with the existing SqlCommandCacheDependencyEnlister. ATM it simply checks if a substring is present in the connection string, but it could be made more robust.


Please take a quick look and see if this is interesting for you. 
Thanks in advance!


Regards,
-- Wouter Groeneveld. 

---- original commit msg: ----

don't enlist sql command cache dependencies

if not compatible (no
mssql), simply don't enlist the cache dependencies
and issue a warning
instead of crashing. If you have a <region/> in your
Web.config but your
connection string is resolved dynamically (for one
client using mssql
and for one client for instance mysql) - you'd have
to alter the web
config everytime, which is not good...