I will add some comments and will create some tool support as well. For
now, I updated the copyright notice:

Name: PostgresV2-TudorGirba.30
Author: TudorGirba
Time: 3 March 2014, 7:46:26.827104 am
UUID: 7efdf379-1733-470b-a84e-29ed8f79dd6e
Ancestors: PostgresV2-EdwinDH.29

updated the copyright notice based on a mail from the author Yanni Chiu:

<quote>
I've lost track of where it's being actively maintained, but please go
ahead and remove or update the copyright text in the comment to MIT.
</quote>


It is already in StHub in PharoExtras :).

Cheers,
Doru




On Mon, Mar 3, 2014 at 7:37 AM, Pharo4Stef <[email protected]> wrote:

> Doru
>
> Will you add comments in the classes?
> Where the code located?
> Would be good to migrate it to SmalltalkHub.
>
> Stef
>
> On 03 Mar 2014, at 07:27, Tudor Girba <[email protected]> wrote:
>
> Thank you, Yanni!
>
> Doru
>
>
> On Mon, Mar 3, 2014 at 12:11 AM, Yanni Chiu <[email protected]> wrote:
>
>> Hmmm. Didn't remember that was there. IIRC, it was released under Squeak
>> Licence, via SqueakMap. Then when migrated to squeaksource.com, I
>> believe it was marked as MIT. I've lost track of where it's being actively
>> maintained, but please go ahead and remove or update the copyright text in
>> the comment to MIT.
>> --
>> Yanni
>>
>>
>> On 02/03/2014 11:36 AM, Tudor Girba wrote:
>>
>>> Another thing I see in the comment of PGConnection is this:
>>> Copyright (c) 2001-2003 by Yanni Chiu. All Rights Reserved.
>>>
>>> Does anyone know the actual license?
>>>
>>> Doru
>>>
>>>
>>> On Sun, Mar 2, 2014 at 5:34 PM, Tudor Girba <[email protected]
>>> <mailto:[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 <http://www.tudorgirba.com>
>>>
>>>
>>>     "Every thing has its own flow"
>>>
>>>
>>>
>>>
>>> --
>>> www.tudorgirba.com <http://www.tudorgirba.com>
>>>
>>>
>>> "Every thing has its own flow"
>>>
>>
>>
>
>
> --
> www.tudorgirba.com
>
> "Every thing has its own flow"
>
>
>


-- 
www.tudorgirba.com

"Every thing has its own flow"

Reply via email to