|
From: Roger H. <cro...@ya...> - 2005-12-30 17:50:03
|
--- Chuck Esterbrook <chu...@gm...> wrote: > On 12/29/05, Roger Haase <cro...@ya...> wrote: > > ... > > > > If I understand this correctly, a User record is in the process of > > being moved into the Middlekit store, and it is expecting the old > > mx.DateTime type of <type 'DateTime'>, but the MySQL-python module > is > > passing the Python 2.3/2.4 <type 'datetime.datetime'>. > > > > An idea was to uninstall mx and see what happened next, but yum > > reported that MySQL-python 1.2 was dependent upon mx and would be > > uninstalled along with it. > > > > Anyone have an idea of what to do to fix this? > > I maintain MiddleKit and I'll help you work through this. Did you > regen your MK source code? If so and you still have the problem, can > you send me your GenUser.py so I can look at it? I have worked around the problem by uninstalling MySQL-python 1.2 and installed the older MySQL-python 0.9.2. Everything seems to work OK with the older module. I think the problem is incompatible defauts between MiddleKit and MySQL-python 1.2. Given the presence of both mx and Python 2.3+, MySQL-python 1.2 is choosing to use the Python datetime module and MiddleKit is using the mx DateTime. I had regened the MK source code and I have attached the module. The relevant part is the setUpdateTime method at line 936 and the failure is the type check at line 941. Roger Haase __________________________________ Yahoo! for Good - Make a difference this year. http://brand.yahoo.com/cybergivingweek2005/ |