The initials "pf" aren't registered. :( I need to know if more maintenance is planned, or if I can just take over... I found a problem with the types returned in the current protocol. -- Randal L. Schwartz - Stonehenge Consulting Services, Inc. - +1 503 777 0095 <[hidden email]> <URL:http://www.stonehenge.com/merlyn/> Perl/Unix/security consulting, Technical writing, Comedy, etc. etc. See PerlTraining.Stonehenge.com for onsite and open-enrollment Perl training! |
Randal L. Schwartz wrote:
> I need to know if more maintenance is planned, or if I can just take over... I > found a problem with the types returned in the current protocol. A few people have submitted fixes & proposed enhancements. I had hoped to roll them together into a maintenance release, but that hasn't happened yet -- was hoping to get back to Squeaking come the new year, but my gig was extended. The project is public-writable, so I think those who are actively using PostgresV2 (not me at the moment) should just go ahead and maintain it. BTW, on map.squeak.org, it's clear that the PostgresV2 is under SqueakL+MIT license. Is it safe to assume that contributors have implicitly released their changes under the same license? -- Yanni Chiu |
On 5 janv. 08, at 07:22, Yanni Chiu wrote: > Randal L. Schwartz wrote: >> I need to know if more maintenance is planned, or if I can just >> take over... I >> found a problem with the types returned in the current protocol. > > A few people have submitted fixes & proposed enhancements. I had hoped > to roll them together into a maintenance release, but that hasn't > happened yet -- was hoping to get back to Squeaking come the new > year, but my gig was extended. > > The project is public-writable, so I think those who are actively > using PostgresV2 (not me at the moment) should just go ahead and > maintain it. > > BTW, on map.squeak.org, it's clear that the PostgresV2 is under > SqueakL+MIT license. Is it safe to assume that contributors have > implicitly released their changes under the same license? do not ask about that :) Just say if you publish on my repository it is assume that this is with the same license. Don't we like this polution of our life with all this great license % ^&.... wonderful lawer world. Stef > > -- > Yanni Chiu > > > |
In reply to this post by Randal L. Schwartz
"PostgresV2-pf.7" - it's my changes.
I added two methods: PGConnection#executeAndCheckResult: sqlString PGConnection#execute: sqlString withRowBlock: aRowBlock Without my changes, you cannot iterate big PostgreSQL table (with 5 000 000 rows for example). Default behaviour is: load whole resultset into memory - this is nice for small tables or applications like "sample blog". But for real use, you need to code with SQL CURSORs again and again... Look at "beginners" mailing list archive for messages with subject "PostgresV2 and bulk resultsets". http://lists.squeakfoundation.org/pipermail/beginners/2007-November/003374.html Petr Fischer On 3.1.2008, at 1:51, Randal L. Schwartz wrote: > > The initials "pf" aren't registered. :( > > I need to know if more maintenance is planned, or if I can just take > over... I > found a problem with the types returned in the current protocol. > > -- > Randal L. Schwartz - Stonehenge Consulting Services, Inc. - +1 503 > 777 0095 > <[hidden email]> <URL:http://www.stonehenge.com/merlyn/> > Perl/Unix/security consulting, Technical writing, Comedy, etc. etc. > See PerlTraining.Stonehenge.com for onsite and open-enrollment Perl > training! > > smime.p7s (3K) Download Attachment |
In reply to this post by Randal L. Schwartz
On Wed, 2008-01-02 at 16:51 -0800, Randal L. Schwartz wrote: > The initials "pf" aren't registered. :( > > I need to know if more maintenance is planned, or if I can just take over... I > found a problem with the types returned in the current protocol. > I changed the code to be able to configure the client encoding between squeak and postgres (side effects are in execute: and in the field converters). This has to be configured externally (external to PGConnection). But I don't like the approach like it is. In my working copy I defaulted the client encoding to utf-8 (in PGConnection>>startUp. The change is attached) to make my life easier. Having some negotation between the driver and the database, e.g. to set the client encoding would be useful. Norbert PGConnection-startup.st (606 bytes) Download Attachment |
Free forum by Nabble | Edit this page |