Re: gda_server_error_*



> I mean the following: Some dbms-client apis support user defined callbacks.
> However, they missed a user-data parameter. Hence, you have no
> Gda_ServerConnection * pointer to use for gda_server_error_new,
> never getting a Gda_ServerError * pointer. So, you cannot send an error
> message to the server using these programming easing features of the
> dbms client api.
> However, i don't think the workaround keeping pointers of all
> Gda_ServerConnection *'s of the provider globaly would not be
> a good solution.
> 
> In conclusion, i'd greatly appreciate a function which can either return
> a GList of all Gda_ServerConnection s to the provider (and it can pick
> out the correct Connection by comparing the cnc user_data).
> or a functionset which can pass error messages as gchar * to the server
> library.
> 
The Gda_ServerImpl object holds a GList of all open connections for this
provider, so you can just have a global variable of type Gda_ServerImpl
and use this GList. I've added a gda_server_impl_get_connections #define
for that purpose, so use it if you like it.

But, we can also add the function you want, which returns a GList of all
open connections for all Gda_ServerImpl objects (usually there will be
only one per provider/process though). But as there should be only one
Gda_ServerImpl per process, I think the first solution is better.






[Date Prev][Date Next]   [Thread Prev][Thread Next]   [Thread Index] [Date Index] [Author Index]