> I've spent the last few hours tackling a confusing problem in > SQLObject, and thought I might post the experience to help other > TurboGear people.
Even better, post it on the wiki: http://trac.turbogears.org/turbogears/wiki/SqlObjectGotchas :) > As it turns out, one cannot use a field named 'dirty' in SQLObject > classes, as it is an internal attribute used by SQLObject. Everytime > SQLObject sets this attribute, (which was now a property) it triggered > a SQL update operation. > > I renamed the field, and the problem went away. That really IS dirty. :) -- mvh Björn --~--~---------~--~----~------------~-------~--~----~ You received this message because you are subscribed to the Google Groups "TurboGears" 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/turbogears -~----------~----~----~----~------~----~------~--~---
