[Top][All Lists]

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

Re: [Help-smalltalk] DBI.Connection call yields "Object: nil error: did

From: Holger Freyther
Subject: Re: [Help-smalltalk] DBI.Connection call yields "Object: nil error: did not understand #atEnd" in ST 3.2.91-b98173d
Date: Mon, 31 Aug 2015 08:09:25 +0200

> On 31 Aug 2015, at 04:51, Mark Bratcher <address@hidden> wrote:
> Holger


> I believe I found the problem.


> The socket is connecting fine. But digging into the connection code, I found 
> that a `class new` operation now automatically calls the `initialize` method 
> in 3.2.91-b98173d, but it does not do so in 3.2.5. This causes a problem in 
> the MySQLPacket and MySQLInputPacket connection code and results in 
> `MySQLInputPacket >> initialize` being called too early in `^(self new) 
> stream: aStream ; initialize` inside of ` MySQLPacket class >> on: aStream`. 
> It's called automatically on `self new` before the stream is set.

I tried to align this semantic to Pharo (as porting from/to Pharo gets easier). 
you for your analysis! The question is why does the CI pass? Did I by accident 
go through authentication?

I will try to reproduce and integrate a fix this week.


reply via email to

[Prev in Thread] Current Thread [Next in Thread]