Firebird SQL Development
 
Forums: » Register « |  User CP |  Games |  Calendar |  Members |  FAQs |  Sitemap |  Support | 
User Name:
Password:
Remember me
Go Back   Dev Shed ForumsDatabasesFirebird SQL Development

Reply
Add This Thread To:
  Del.icio.us   Digg   Google   Spurl   Blink   Furl   Simpy   Y! MyWeb 
Thread Tools Search this Thread Rate Thread Display Modes
 
Unread Dev Shed Forums Sponsor:
  #1  
Old October 3rd, 2006, 11:11 AM
DJAtwill DJAtwill is offline
Registered User
Dev Shed Newbie (0 - 499 posts)
 
Join Date: Feb 2004
Posts: 4 DJAtwill User rank is Just a Lowly Private (1 - 20 Reputation Level) 
Time spent in forums: 40 m 14 sec
Reputation Power: 0
Embedded .Net 2.0 connections

When using the .Net 2.0 client is it better to close the connection after each SQL command/process or cache the open connection? The reason I ask is because I know ADO.Net 2.0 has connection pooling and I wasn't sure if Firbird did something like this internally.

I also noticed that not calling Dispose() on the command object caused my application to eventually run out of memory. Is there a guide for faq relating to best way to use these libraries?

Reply With Quote
Reply

Viewing: Dev Shed ForumsDatabasesFirebird SQL Development > Embedded .Net 2.0 connections


Thread Tools  Search this Thread 
Search this Thread:

Advanced Search
Display Modes  Rate This Thread 
Rate This Thread:


Posting Rules
You may not post new threads
You may not post replies
You may not post attachments
You may not edit your posts

vB code is On
Smilies are On
[IMG] code is On
HTML code is Off
View Your Warnings | New Posts | Latest News | Latest Threads | Shoutbox
Forum Jump


Forums: » Register « |  User CP |  Games |  Calendar |  Members |  FAQs |  Sitemap |  Support | 
  
 





© 2003-2008 by Developer Shed. All rights reserved. DS Cluster 1 hosted by Hostway