Thank you Daniel that was what I was thinking but not sure.
So that now leads me to my next issue which is in VC++.Net how would I call
connection Conn(Conninfo);
After a person puts in their userid and password and keep it open and
useable for all other functions in an application?
-----Original Message-----
From: [EMAIL PROTECTED]
[mailto:[EMAIL PROTECTED] On Behalf Of Daniel
Cristian Cruz
Sent: Thursday, January 04, 2007 12:36 PM
To: [email protected]
Subject: Re: [libpqxx-general] Persistent vs Non-Persistent Connections
Brian,
Try to always use a persistent connection. It improves performance,
since there is no need to create a new PostgreSQL server process for
each operation. It is even slower on some OS (guess what? :)).
There are some posts about it in PostgreSQL Performance List.
Kind Regards.
Daniel Cristian
Em Qui, 2007-01-04 às 11:45 -0500, DEV escreveu:
> Hello,
>
> I am working on an app in windows and things are going rather
> well, thanks to many on this list. I currently have it setup where
> any time you do anything with the database it makes a connection does
> what is needed then closes the connection. I am wondering if I should
> have the app coded to use a persistent connection where once you log
> into the app your are connected and it stays connected and uses that
> connection the whole time and closes it once you close the app or log
> out. Your opinions are greatly appreciated!
>
>
>
> Brian Doyle
>
>
>
>
> _______________________________________________
> Libpqxx-general mailing list
> [email protected]
> http://gborg.postgresql.org/mailman/listinfo/libpqxx-general
--
Daniel Cristian Cruz
クルズ クリスチアン ダニエル
Analista de Sistemas
Especialista Linux e PostgreSQL
_______________________________________________
Libpqxx-general mailing list
[email protected]
http://gborg.postgresql.org/mailman/listinfo/libpqxx-general
_______________________________________________
Libpqxx-general mailing list
[email protected]
http://gborg.postgresql.org/mailman/listinfo/libpqxx-general
