Login ProductsSalesSupportDownloadsAbout |
Home » Technical Support » DBISAM Technical Support » Support Forums » DBISAM Third Party Announcements » View Thread |
Messages 1 to 6 of 6 total |
Context ADO.Net Provider and Sessions |
Fri, Jul 21 2006 9:29 PM | Permanent Link |
"Alan Questell" | In trying out the ADO.Net data provider, closing a DBISAM connection leaves
the session, though disconnected, on the server. Is there another method to dispose of the session? Shouldn't it end the session? |
Sat, Jul 22 2006 5:56 AM | Permanent Link |
Michael Baytalsky | Hi Alan,
Which version of the provider and which version of DBISAM are you testing? Michael Alan Questell wrote: > In trying out the ADO.Net data provider, closing a DBISAM connection leaves > the session, though disconnected, on the server. Is there another method to > dispose of the session? Shouldn't it end the session? > > |
Sat, Jul 22 2006 1:53 PM | Permanent Link |
"Alan Questell" | VS 2005, DBISAM 3.30 (registered version), ADO.Net Provider 2.0 (trial
version - just downloaded a couple of days ago). I was just trying out the provider with a small program against the DBISAM server on localhost: open a connection, fill a grid with data, and close the connection - but that leaves the session in place and creates another one on each subsequent run. I end with dbConnection.Close() - dbConnection being a DbisamConnection object created in code. "Michael Baytalsky" <mike@contextsoft.com> wrote in message news:E96618D7-9F01-4D89-861C-8D7DF3F469AF@news.elevatesoft.com... > Hi Alan, > > Which version of the provider and which version of DBISAM are > you testing? > > Michael > > Alan Questell wrote: >> In trying out the ADO.Net data provider, closing a DBISAM connection >> leaves the session, though disconnected, on the server. Is there another >> method to dispose of the session? Shouldn't it end the session? |
Sat, Jul 22 2006 11:36 PM | Permanent Link |
"Alan Questell" | Playing with it further, I found that if I use Alt-F4 to close my small test
application, the session at the server is disposed of properly. But if you use the red Close button in the upper right corner (Windows XP Pro), the session is disconnected, but not disposed of. In any case, the Close() method of the connection object has been called already. "Michael Baytalsky" <mike@contextsoft.com> wrote in message news:E96618D7-9F01-4D89-861C-8D7DF3F469AF@news.elevatesoft.com... > Hi Alan, > > Which version of the provider and which version of DBISAM are > you testing? > > Michael > > Alan Questell wrote: >> In trying out the ADO.Net data provider, closing a DBISAM connection >> leaves the session, though disconnected, on the server. Is there another >> method to dispose of the session? Shouldn't it end the session? |
Sun, Jul 23 2006 2:47 PM | Permanent Link |
Michael Baytalsky | Hi Alan,
You need to switch connection Pooling off (by adding Pooling=False to your connection string). This will make it use disconnected model. Otherwise, there's currently no control over how the objects are disposed, because they're disposed by .Net - undeterministic garbage collector. I think what you're seeing with Alt-F4 is one of the side-effects of it. Michael Alan Questell wrote: > Playing with it further, I found that if I use Alt-F4 to close my small test > application, the session at the server is disposed of properly. But if you > use the red Close button in the upper right corner (Windows XP Pro), the > session is disconnected, but not disposed of. In any case, the Close() > method of the connection object has been called already. > > > "Michael Baytalsky" <mike@contextsoft.com> wrote in message > news:E96618D7-9F01-4D89-861C-8D7DF3F469AF@news.elevatesoft.com... >> Hi Alan, >> >> Which version of the provider and which version of DBISAM are >> you testing? >> >> Michael >> >> Alan Questell wrote: >>> In trying out the ADO.Net data provider, closing a DBISAM connection >>> leaves the session, though disconnected, on the server. Is there another >>> method to dispose of the session? Shouldn't it end the session? > > |
Mon, Jul 24 2006 7:32 PM | Permanent Link |
"Alan Questell" | Okay, thanks.
"Michael Baytalsky" <mike@contextsoft.com> wrote in message news:98BBD86E-3338-41DE-9E1A-6D33E9CCD02B@news.elevatesoft.com... > Hi Alan, > > You need to switch connection Pooling off (by adding Pooling=False to your > connection string). This will make it use disconnected model. Otherwise, > there's currently no control over how the objects are disposed, because > they're disposed by .Net - undeterministic garbage collector. I think > what you're seeing with Alt-F4 is one of the side-effects of it. > > > Michael > > Alan Questell wrote: >> Playing with it further, I found that if I use Alt-F4 to close my small >> test application, the session at the server is disposed of properly. But >> if you use the red Close button in the upper right corner (Windows XP >> Pro), the session is disconnected, but not disposed of. In any case, the >> Close() method of the connection object has been called already. >> >> >> "Michael Baytalsky" <mike@contextsoft.com> wrote in message >> news:E96618D7-9F01-4D89-861C-8D7DF3F469AF@news.elevatesoft.com... >>> Hi Alan, >>> >>> Which version of the provider and which version of DBISAM are >>> you testing? >>> >>> Michael >>> >>> Alan Questell wrote: >>>> In trying out the ADO.Net data provider, closing a DBISAM connection >>>> leaves the session, though disconnected, on the server. Is there >>>> another method to dispose of the session? Shouldn't it end the session? >> |
This web page was last updated on Wednesday, April 24, 2024 at 11:07 AM | Privacy PolicySite Map © 2024 Elevate Software, Inc. All Rights Reserved Questions or comments ? E-mail us at info@elevatesoft.com |