Subject | Re: [firebird-support] Re: Reboot to Restore |
---|---|
Author | Helen Borrie |
Post date | 2005-07-23T22:49Z |
At 08:51 AM 23/07/2005 -0700, you wrote:
API. Clients detach from the server by doing their own resources cleanup
and then calling the API function isc_detach_database(). Standard
interfaces like .NET, JDBC, ODBC each provide their own rules for how the
management of connections is to be surfaced to the programmer. I'm not a
.NET programmer, so I can't tell you anything about what that interface
does. You will find out all you need to know at the firebird-net-provider
list.
./heLen
>Ok, I'll have to go back to the code and make sure to explicity detach.One would suppose so, since each language interface layer wraps the same
>
>
>Meanwhile.....
>
>I have a simiar problem with a dotNet application using Firebird provider.
>I think I
>assumed that the Provider framework would keep connections managed well
>enough that I could drop a database and rerun a db creation script (which
>I can't do).
>Now I'm thinking I may have to explicitly detach the dotNet app in the
>same way as
>the ISAPI app?
API. Clients detach from the server by doing their own resources cleanup
and then calling the API function isc_detach_database(). Standard
interfaces like .NET, JDBC, ODBC each provide their own rules for how the
management of connections is to be surfaced to the programmer. I'm not a
.NET programmer, so I can't tell you anything about what that interface
does. You will find out all you need to know at the firebird-net-provider
list.
./heLen