I am using InnoDB for transactional support. I also have a timeLifeCycleInitialized field for each life cycle record and a timeLifeCycleTransitioned for the parent record. I have verified that the child records have existed for minutes to hours and have shown up in previous queries, so it's not the case that they don't exist yet.
I'll look at the MySQL issues and post in their forum next. Thanks for your reply. Daniel On Sep 3, 9:43 am, "Michael Bayer" <mike...@zzzcomputing.com> wrote: > Daniel wrote: > > > So if there were five child_life_cycle records in the database and > > three had values for doneProcessing and the other two didn't then I > > would expect to get a "2" back from my query and not transition. > > However, I'm finding that in some cases (when I look in my logs) the > > query will return zero (0) and then a few seconds later it will return > > the correct number of "2". Somehow those two records didn't show up > > in the query. They were masked. > > it could that those zeros are occurring before the child records actually > exist in the DB, which may or may not be possible. If for some reason > your query for "null" is in a transaction that is more stale than the one > that added the child records, that would cause it as well. I'm assuming > you're all on InnoDB tables otherwise you're not getting any kind of > transactional consistency. > > It also may be a known MySQL bug. Search around on their tracker as I > have seen some bugs related to incorrect data being returned for InnoDB. --~--~---------~--~----~------------~-------~--~----~ You received this message because you are subscribed to the Google Groups "sqlalchemy" group. To post to this group, send email to sqlalchemy@googlegroups.com To unsubscribe from this group, send email to sqlalchemy+unsubscr...@googlegroups.com For more options, visit this group at http://groups.google.com/group/sqlalchemy?hl=en -~----------~----~----~----~------~----~------~--~---
