Re: Why NOT use fetchReturnsList?
Gerhard Häring <[email protected]> Thu, 17 Jun 2004 17:37:25 +0200
| Newsgroups | gmane.comp.python.db.pypgsql.user |
|---|---|
| Message-ID | <[email protected]> |
Leo Leo wrote: > Hello! > > I have still a question about this parameter "fetchReturnsList". > > As far as I have understood it, the pgResultSet contains a lot more > information about the retrieved data, than the result by Lists. That's correct. PgResultSet had a lot more overhead in the past, but we implemented an optimization once that dynamically creates classes. Now the classes contain the additional information of the PgResultSet, not each object instance any more. PgResultSets are still slower than fetchReturnsList=True, but not so significantly any longer. > [...] So, shouldn't it be better (Performance, less traffic etc.) to gather this > additional information in an other way (just once per select) and get the > data by lists? (I made something like this for PHP some months ago) There's hardly any space overhead of PgResultSets any more :-) -- Gerhard ------------------------------------------------------- This SF.Net email is sponsored by The 2004 JavaOne(SM) Conference Learn from the experts at JavaOne(SM), Sun's Worldwide Java Developer Conference, June 28 - July 1 at the Moscone Center in San Francisco, CA REGISTER AND SAVE! http://java.sun.com/javaone/sf Priority Code NWMGYKND