Thanks for the information.
May be Olivier could help us there.
On 3/10/14 12:59, Pierce Ng wrote:
On Thu, Oct 02, 2014 at 03:43:05PM -0300, Esteban A. Maringolo wrote:
Is the V2/V3 spec a PostgreSQL protocol spec or something made up in
the Squeak community?
V2/V3 are PostgreSQL wire protoco
Do you really mean that the board is a kind of jerks and idiots that are
lazy bastards?
Please slow down, I never, ever, suggested even remotely that.
I know but do not say that the board is not interested. We just issue
today a roadmap to inria and database is one of the items.
If people
On 3/10/14 14:32, Stephan Eggermont wrote:
PostgresV3-Core/Pool looks perfectly usable.
There is
PG3Connection>>md5HashMessage: aString
^Smalltalk globals
at: #MD5
ifPresent: [ :md5 | (md5 hashMessage: aString) hex asLowercase ]
ifAbsent:
PostgresV3-CodeMirror is very interesting.
7 classes and less than 1K lines of code.
In the base class PG3SchemaMirror, the
compilerClass, parserClass, sourceCodeTemplate
and shoutParserClass are overridden to return
PG3-specific classes. That allows simple
integration with other languages, in th
2014-10-02 17:26 GMT-03:00 Sven Van Caekenberghe :
> Esteban,
>
> On 02 Oct 2014, at 20:43, Esteban A. Maringolo wrote:
>
>> 2014-10-02 15:19 GMT-03:00 Stephan Eggermont :
>>> Esteban wrote:
Are you using/planning to use PostgresV3?
>>>
What are its advantages over current driver (Postgr
2014-10-03 2:47 GMT-03:00 stepharo :
> On 2/10/14 20:43, Esteban A. Maringolo wrote:
>> I don't want to sound harsh, but there is no VISIBLE interest from the
>> Pharo board/committee regarding ORM and/or RDBMS support other than a
>> CI task.
> Do you really mean that the board is a kind of jerks
PostgresV3-Core/Pool looks perfectly usable.
There is
PG3Connection>>md5HashMessage: aString
^Smalltalk globals
at: #MD5
ifPresent: [ :md5 | (md5 hashMessage: aString) hex asLowercase ]
ifAbsent: [ WebUtils md5Digest: aString ]
Which work
On Thu, Oct 02, 2014 at 03:43:05PM -0300, Esteban A. Maringolo wrote:
> Is the V2/V3 spec a PostgreSQL protocol spec or something made up in
> the Squeak community?
V2/V3 are PostgreSQL wire protocol versions. V3 supports parameter binding
and bulk copying, whereas V2 does not.
There is some add
On 2/10/14 23:37, Esteban Lorenzano wrote:
HI,
Well, what you say sounds harsh... but is not too far from truth,
sadly. What happens is that current manpower for every task is very
limited (it's me)... and well, urgent stuff is always hunting us.
But esteban this is not true.
Pharo is not y
On 2/10/14 20:43, Esteban A. Maringolo wrote:
I don't want to sound harsh, but there is no VISIBLE interest from the
Pharo board/committee regarding ORM and/or RDBMS support other than a
CI task.
Do you really mean that the board is a kind of jerks and idiots that are
lazy bastards?
If people
HI,
Well, what you say sounds harsh... but is not too far from truth, sadly.
What happens is that current manpower for every task is very limited (it's
me)... and well, urgent stuff is always hunting us.
We have the willing, and we have spent some time on it, but it will be a
lot easier if there i
Esteban,
On 02 Oct 2014, at 20:43, Esteban A. Maringolo wrote:
> 2014-10-02 15:19 GMT-03:00 Stephan Eggermont :
>> Esteban wrote:
>>> Are you using/planning to use PostgresV3?
>>
>>> What are its advantages over current driver (PostgresV2)?
>>
>> I was puzzled that a smart developer like Leven
2014-10-02 15:19 GMT-03:00 Stephan Eggermont :
> Esteban wrote:
>>Are you using/planning to use PostgresV3?
>
>>What are its advantages over current driver (PostgresV2)?
>
> I was puzzled that a smart developer like Levente
> decides not to use Glorp.
I don't want to sound harsh, but there is no V
Esteban wrote:
>Are you using/planning to use PostgresV3?
>What are its advantages over current driver (PostgresV2)?
I was puzzled that a smart developer like Levente
decides not to use Glorp. And I wondered why
SqueakDBX decided to use V2 instead of V3,
a protocol introduced in 2003 or so.
2014-10-01 9:30 GMT-03:00 Stephan Eggermont :
> The PostgresV3 code in squeak uses subclasses of Compiler and Parser to make
> sure that
> PG3SchemaMirror subclasses can parse plsql code. That looks like a nice way
> to work.
Are you using/planning to use PostgresV3?
What are its advantages ove
On 01 Oct 2014, at 14:30, Stephan Eggermont wrote:
> The PostgresV3 code in squeak uses subclasses of Compiler and Parser to make
> sure that
> PG3SchemaMirror subclasses can parse plsql code. That looks like a nice way
> to work.
>
> What do we need to do to do something similar with the Opa
16 matches
Mail list logo
