OK, I checked to make sure the updates were being fired (and from the looks of the log, they are).
But I think I see that the lack of update executions hasn't been the problem all along, but rather that those updates are not finding their row... never checked that part. I'm offsite right now and can't look at the code, but I suspect that the milliseconds are the problem -- MSSQL rounds milliseconds to some multiple, so what you put in is not always what you get back. Since the program saves the initial date PK as the result of a datetime.now() call, I'll bet that it doesn't match the DB stored value. Here's a couple of things you can do to work around that: a) Truncate the milliseconds from the datetime.now() call before you write the initial job object b) Fetch the job object back after the first flush() to get the DB stored value. See if one of those fixes your issue. Rick --~--~---------~--~----~------------~-------~--~----~ You received this message because you are subscribed to the Google Groups "sqlalchemy" group. To post to this group, send email to [email protected] To unsubscribe from this group, send email to [EMAIL PROTECTED] For more options, visit this group at http://groups.google.com/group/sqlalchemy?hl=en -~----------~----~----~----~------~----~------~--~---
