[squeak-dev] Re: Problem with TimeStamp class and ODBC package

Andreas Raab andreas.raab at gmx.de
Tue Apr 28 08:01:49 UTC 2009


Giuseppe Luigi Punzi wrote:
> ........?
> 
> I installed latest version from Universes. I tried to reproduce the 
> problem, and I can't. And the only change between this images was ODBC 
> installed, for this I thought was ODBC causing the problem.
> 
> Could be the universes version outdated?

Yes, that is very likely. Unfortunately, only the so-called "maintainer" 
can update an entry in Universes and I have more than once seen that 
"maintainer" have absolutely no relationship to the real people 
maintaining a package. I don't know who is the listed maintainer for the 
ODBC package in Universes (and I can't be bothered to check since 
Universes cannot be searched and I'm not going to click through every 
frigging entry) but more likely than not you won't find any of the 
actual contributors listed there. So I guess you'll have to ask that 
"maintainer" to do his job of actually maintaining the package they've 
volunteered to maintain ;-)

Cheers,
   - Andreas

> Andreas Raab escribió:
>> Giuseppe Luigi Punzi wrote:
>>> Trying some things with Aida/Web, I got an error with TimeStamp class 
>>> in one image with a MNU #day.
>>>
>>> The problem, seems, thath ODBC Package, reimplement TimeStamp class, 
>>> changing his parent to Magnitude, and changing some selectors.
>>
>> You may be using an outdated version of ODBC. There is no 
>> reimplementation of TimeStamp in http://squeaksource.com/ODBC.html
>>
>> Cheers,
>>   - Andreas
>>
>>> Initially, TimeStamp (is in Kernel-Chronology category) and is 
>>> subclass of DateAndTime thath is subclass of Magnitude.
>>>
>>> DateAndTime is who has #day
>>>
>>> In my image with the problems, I have installed ODBC, and TimeStamp, 
>>> is subclass of Magnitude, and is in Kernel-Magnitude category.
>>>
>>> Changing
>>> Magnitude subclass: #TimeStamp
>>>
>>> by
>>> DateAndTime subclass: #TimeStamp
>>>
>>> I can access to Aida Interface on localhost:8888 and the problem 
>>> seems solved, but, I don't know if could be colateral damage for this 
>>> change, because ODBC change more things on this class.
>>>
>>> I tried to contact with Diego Gómez Deck, but I didn't get any response.
>>>
>>> Somebody can solve this?
>>>
>>> Cheers.
>>>
>>>
>>
>>
> 
> 
> 




More information about the Squeak-dev mailing list