--- Chuck Esterbrook <chuck.esterbrook@...> wrote:
> On 12/29/05, Roger Haase <crosseyedpenguin@...> 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
> > 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.
Yahoo! for Good - Make a difference this year.