Jiri Cincura wrote: > > Read tracker: http://tracker.firebirdsql.org/browse/DNET-156 or use > stable version of provider. > In addition to workaround, mentioned in tracker, i propose calling FbConnection.ClearAllPools() on application exit, it has the benefit of still using connection pooling and preventing application from freezing till final version of provider arrives :drunk: -- View this message in context: http://www.nabble.com/NET-Provider-2.5-alfa-and-fb-embedded-Firebird-2.0-ERROR%21%21%21-tp16451201p16547981.html Sent from the firebird-net-provider mailing list archive at Nabble.com.
------------------------------------------------------------------------- This SF.net email is sponsored by the 2008 JavaOne(SM) Conference Register now and save $200. Hurry, offer ends at 11:59 p.m., Monday, April 7! Use priority code J8TLD2. http://ad.doubleclick.net/clk;198757673;13503038;p?http://java.sun.com/javaone _______________________________________________ Firebird-net-provider mailing list Firebird-net-provider@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/firebird-net-provider
