Jeroen T. Vermeulen wrote:
>On Fri, January 6, 2006 16:44, Luis Silva wrote: > > >>The problem is that if you do this you'll access the database twice. I'm >>trying to do what you told me but only with one access. tks a lot >> >> > >You could use a pipeline to reduce that effect. Pump in queries on one >end, and read results out the other. One extreme case is to make the >pipeline retain as many queries as you have, insert all queries, and then >start reading results until you encouter an empty one; the other extreme >is just to insert the next query before reading the result of the last >one. The optimal may lie somewhere in between, and depend on the queries, >whether the database is local or remote, system configuration, etc. > > >Jeroen > > >_______________________________________________ >Libpqxx-general mailing list >[email protected] >http://gborg.postgresql.org/mailman/listinfo/libpqxx-general > > >__________ NOD32 1.1354 (20060105) Information __________ > >This message was checked by NOD32 antivirus system. >http://www.eset.com > > > > > Alternatively you could create a function in the DB in PL/SQL or SQL. If you return NULL from a PLSQL function no further processing is done. This allows you to do everything with one client-server interaction. You can call such a function using within an SQL select statement. Quite easy really. _______________________________________________ Libpqxx-general mailing list [email protected] http://gborg.postgresql.org/mailman/listinfo/libpqxx-general
