[SqueakDBX] OpenDBX: Another command is already in progress

[John Toohey]

The main one is the GlorpDatabaseReadError, and as its resumable, and a read
error, I just want to retry it, until it succeeds. This is a production
system, and having the debugger fire constantly, eventually messes up the
entire image.


On Tue, May 10, 2011 at 14:23, Mariano Martinez Peck
<marianopeck at gmail.com>wrote:

>
>
> On Tue, May 10, 2011 at 5:03 PM, John Toohey <jt at parspro.com> wrote:
>
>> But as these exceptions
>
>
> which ones? I guess you are talking about GlorpDatabaseReadError
>
>
>> are marked as Resumable, shouldn't it be enough for me to do :-
>
>
> I am not sure if I understood correctly. Can you explain a little more
> please?
>
>
>>  [
>>  ^aQuery executeWithParameters: #() in: self.
>> ]
>> on: GlorpDatabaseReadError
>>  do: [:ex | Transcript show: ex messageText;cr.  ex resume].
>>
>
>
>
> thanks
>
> Mariano
>
>
>
>>
>> On Tue, May 10, 2011 at 10:39, Mariano Martinez Peck <
>> marianopeck at gmail.com> wrote:
>>
>>>
>>>
>>> On Tue, May 10, 2011 at 4:31 PM, John Toohey <jt at parspro.com> wrote:
>>>
>>>> I get this error a lot when my system is under load. According to the
>>>> pgsql docs, I should do this, "PQgetResult must be called repeatedly
>>>> until it returns a null pointer,
>>>>
>>>
>>> *indicating* that the *command* *is* done."
>>>>
>>>>
>>> This is weird...it should not happen while using SqueakDBX.
>>> If you see DBXConnection >> execute:
>>>
>>> just at the beginning we do:
>>>
>>>     | aResult |
>>>     self isOpen ifFalse:
>>>         [ OpenDBXDriverError signal: 'You cannot execute a query if the
>>> connection is not open' ].
>>>     self releasePreviousResult.
>>>
>>>
>>> that method #releasePreviousResult  that exactly that. If you didn't
>>> finish iterating all returns in your last query, we do it for you in the
>>> next query. Of course, we also do that while closing the connection.
>>> So...I cannot image how you can get that :(
>>> Probably something with the pool and Glorp ?
>>>
>>>
>>>>  How do I handle this type of error in GlorpDBX? I'm using Pharo 1.2
>>>> and the Glorp/DBX build that was available when that was released.
>>>>
>>>> --
>>>> ~JT
>>>>
>>>>
>>>>
>>>> _______________________________________________
>>>> SqueakDBX mailing list
>>>> SqueakDBX at lists.squeakfoundation.org
>>>> http://lists.squeakfoundation.org/mailman/listinfo/squeakdbx
>>>>
>>>>
>>>
>>>
>>> --
>>> Mariano
>>> http://marianopeck.wordpress.com
>>>
>>>
>>> _______________________________________________
>>> SqueakDBX mailing list
>>> SqueakDBX at lists.squeakfoundation.org
>>> http://lists.squeakfoundation.org/mailman/listinfo/squeakdbx
>>>
>>>
>>
>>
>> --
>> ~JT
>>
>>
>>
>> _______________________________________________
>> SqueakDBX mailing list
>> SqueakDBX at lists.squeakfoundation.org
>> http://lists.squeakfoundation.org/mailman/listinfo/squeakdbx
>>
>>
>
>
> --
> Mariano
> http://marianopeck.wordpress.com
>
>
> _______________________________________________
> SqueakDBX mailing list
> SqueakDBX at lists.squeakfoundation.org
> http://lists.squeakfoundation.org/mailman/listinfo/squeakdbx
>
>


-- 
~JT
-------------- next part --------------
An HTML attachment was scrubbed...
URL: http://lists.squeakfoundation.org/pipermail/squeakdbx/attachments/20110510/1e192cef/attachment.htm