[ic] sql sessions - odd error
kevin at cursor.biz
Mon Mar 24 11:42:55 EST 2008
"Stefan Hornburg (Racke)" <racke at linuxia.de> wrote:
> Jon Jensen wrote:
> > Apparently MySQL on Windows isn't handling the Unix seconds-since-1970
> > epoch. You can disable time field updating altogether by changing this
> > line in catalog.cfg:
> > UserDB default time_field mod_time
> > to:
> > UserDB default time_field none
> > Then your userdb entries will not have a timestamp showing when they
> > were updated. You could change the mod_time field to be a "timestamp"
> > type, which I think MySQL automatically updates.
> The default behaviour of the first timestamp in a table is automatically
> update. As I learned from a problem in my synchronisation project you
> can instruct MySQL to not update it automatically. Duh.
> I think we should allow an option for UserDB to store as ISO date instead
> of a timestamp.
Perhaps the "iso_time" parameter will help there. :-)
_/ _/ _/_/_/_/ _/ _/ _/_/_/ _/ _/
_/_/_/ _/_/ _/ _/ _/ _/_/ _/ K e v i n W a l s h
_/ _/ _/ _/ _/ _/ _/ _/_/ kevin at cursor.biz
_/ _/ _/_/_/_/ _/ _/_/_/ _/ _/
More information about the interchange-users