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:pharo-users-boun...@lists.pharo.org] 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 <cr...@hivemind.net> 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 > >
