Doru, Note that there is also the newer
http://www.squeaksource.com/PostgresV3.html which implements a more recent, incompatible version of the wire protocol between the client and server. I haven't tested it though, and I don't know if it is compatible at the higher level. Sven On 02 Mar 2014, at 17:34, Tudor Girba <[email protected]> wrote: > Hi, > > I am trying to understand how PostgresV2 is implemented because I would like > to build some inspector support for it, and I encounter a couple of issues. > In case anyone knows the answer, it would speed up my effort: > > - Why is result an instance variable in PGConnection? Making it a variable > always returns the same object when executing a query and that is a bit of a > pain. > > - Why does the PGResult have the possibility of holding multiple > PGResultSets? When is it possible to have multiple at the same time? (when > you execute a query, the result is being initialized) > > - When running something like > connection execute: 'select * from ...' > the PGResultSet already includes all rows of the query. Is it not possible to > have a stream-like functionality in which the actual rows are retrieved only > on demand? (a similar functionality exists in DBXTalk) > > - What is the difference between PGAsciiRow and PGDataRow? > > Doru > > -- > www.tudorgirba.com > > "Every thing has its own flow"
