Smalltalk › Pharo › Pharo Smalltalk Users

Glorp on Pharo 4

_‹ Previous Topic Next Topic _›

Classic

List

Threaded

8 messages Options

Adventurer

Glorp on Pharo 4

Hi All,

I see that Sven is active on this list. I've tried to use his excellent
tutorial on his "concerning-pharo" blog to understand Glorp and to get my
own instance of the demo app running on Pharo 4 and Postgres.

I have not burnt a lot of time on this yet, but I would like to know if this
combination of technologies is known to work anywhere. I have not yet got
it working.

Craig

Sven Van Caekenberghe-2

Re: Glorp on Pharo 4

Hi Craig,

> On 19 Jan 2015, at 13:02, Craig <[hidden email]> wrote:
>
> Hi All,
>
> I see that Sven is active on this list. I've tried to use his excellent
> tutorial on his "concerning-pharo" blog to understand Glorp and to get my
> own instance of the demo app running on Pharo 4 and Postgres.
>
> I have not burnt a lot of time on this yet, but I would like to know if this
> combination of technologies is known to work anywhere. I have not yet got
> it working.
>
> Craig

Using Glorp on top of the PostgresV2 driver (which uses just a network connection and no native code nor plugin) should work on all platforms. Of course, you still have to install Postgres itself, but it can run on another machine too.

HTH,

Sven

Adventurer

Re: Glorp on Pharo 4

-----Original Message-----
From: Sven Van Caekenberghe
Sent: 20 January 2015 01:40 PM

Hi Sven,

> Using Glorp on top of the PostgresV2 driver (which uses just a network
connection
> and no native code nor plugin) should work on all platforms. Of course,
you still
> have to install Postgres itself, but it can run on another machine too.

Thanks for the pointer. It took quite a bit of scratching around, but I now
have a working
Postgres Glorp driver, so I can use either RDBMS.

Thank-you for taking the trouble to respond to my questions.

Craig

Adventurer

Re: Glorp on Pharo 4

In reply to this post by Sven Van Caekenberghe-2

From: Sven Van Caekenberghe
Sent: 20 January 2015 01:40 PM

> Using Glorp on top of the PostgresV2 driver (which uses just a network
connection and no native code nor plugin)
> should work on all platforms. Of course, you still have to install
Postgres itself, but it can run on another machine too.
>
> HTH,
>
> Sven
Sven,

I just ran into an issue in the Postgres V2 driver, which I guess is a
porting error. See below and note the commas ",".

PGConnection>>stSendingMD5Password: event
"MD5 authentication as explain in
http://archives.postgresql.org/pgsql-novice/2003-05/msg00305.php"
| hashedCredentials hashedMessage |

hashedCredentials := (MD5 hashMessage: (connectionArgs password,
connectionArgs userName)) hex asLowercase.
hashedMessage := 'md5', (MD5 hashMessage: (hashedCredentials, event
salt asString)) hex asLowercase.

self sendPacket: (PGPasswordPacket password: hashedMessage) on:
socket.

Sven Van Caekenberghe-2

Re: Glorp on Pharo 4

> On 22 Jan 2015, at 06:52, Craig <[hidden email]> wrote:
>
> From: Sven Van Caekenberghe
> Sent: 20 January 2015 01:40 PM
>
>> Using Glorp on top of the PostgresV2 driver (which uses just a network
> connection and no native code nor plugin)
>> should work on all platforms. Of course, you still have to install
> Postgres itself, but it can run on another machine too.
>>
>> HTH,
>>
>> Sven
> Sven,
>
> I just ran into an issue in the Postgres V2 driver, which I guess is a
> porting error. See below and note the commas ",".
>
> PGConnection>>stSendingMD5Password: event
> "MD5 authentication as explain in
> http://archives.postgresql.org/pgsql-novice/2003-05/msg00305.php"
> | hashedCredentials hashedMessage |
>
> hashedCredentials := (MD5 hashMessage: (connectionArgs password,
> connectionArgs userName)) hex asLowercase.
> hashedMessage := 'md5', (MD5 hashMessage: (hashedCredentials, event
> salt asString)) hex asLowercase.
>
> self sendPacket: (PGPasswordPacket password: hashedMessage) on:
> socket.

What exactly do you mean ?

Reading the link above that seems to be correct, at first glance, maybe I don't see it.

Sven

Adventurer

Re: Glorp on Pharo 4

From: Sven Van Caekenberghe
Sent: 22 January 2015 08:37 AM

> What exactly do you mean ?
>
> Reading the link above that seems to be correct, at first glance, maybe I
don't see it.

Sven,

Forgive me, I'm new to Pharo, but I'm sure that in Pharo you don't use
commas to separate parameters in a
message. I don't know of any syntactical significance of the comma.
I saw this after I got the ", does not understand connectionArgs" message
when trying to connect to my
Postgres database. I take this to mean that Pharo tried to send the
connectionArgs message to the
',' ByteString.

Craig

Sven Van Caekenberghe-2

Re: Glorp on Pharo 4

A comma is indeed a (binary) message. It concatenates two Collections, like Strings.

Please provide more details on how you try to connect and what error you get, exactly.

> On 22 Jan 2015, at 08:26, Craig <[hidden email]> wrote:
>
> From: Sven Van Caekenberghe
> Sent: 22 January 2015 08:37 AM
>
>> What exactly do you mean ?
>>
>> Reading the link above that seems to be correct, at first glance, maybe I
> don't see it.
>
> Sven,
>
> Forgive me, I'm new to Pharo, but I'm sure that in Pharo you don't use
> commas to separate parameters in a
> message. I don't know of any syntactical significance of the comma.
> I saw this after I got the ", does not understand connectionArgs" message
> when trying to connect to my
> Postgres database. I take this to mean that Pharo tried to send the
> connectionArgs message to the
> ',' ByteString.
>
> Craig
>
>

Adventurer

Re: Glorp on Pharo 4

Sven,

It took a bit, but I figured it out.

If you try to login with a login that has previously been used, then you get
this DNU message.

I was following your "reddit-st-in-10-cool-pharo-classes" and it happened
when I ran the first test.
This was the second time that the DefaultLogin was used (it was lazily
initialised by the create tables call).
When I nill-ed out the DefaultLogin the tests all passed.

Craig

-----Original Message-----
From: Pharo-users [mailto:[hidden email]] On Behalf Of
Sven Van Caekenberghe
Sent: 22 January 2015 10:19 AM
To: Any question about pharo is welcome
Subject: Re: [Pharo-users] Glorp on Pharo 4

A comma is indeed a (binary) message. It concatenates two Collections, like
Strings.

Please provide more details on how you try to connect and what error you
get, exactly.

> On 22 Jan 2015, at 08:26, Craig <[hidden email]> wrote:
>
> From: Sven Van Caekenberghe
> Sent: 22 January 2015 08:37 AM
>
>> What exactly do you mean ?
>>
>> Reading the link above that seems to be correct, at first glance,
>> maybe I
> don't see it.
>
> Sven,
>
> Forgive me, I'm new to Pharo, but I'm sure that in Pharo you don't use
> commas to separate parameters in a message. I don't know of any
> syntactical significance of the comma.
> I saw this after I got the ", does not understand connectionArgs"
> message when trying to connect to my Postgres database. I take this
> to mean that Pharo tried to send the connectionArgs message to the ','
> ByteString.
>
> Craig
>
>