On Wed, Jan 21, 2009 at 08:33:03AM -0800, Jan Koprowski wrote: > IMHO this could be standard for all classes (why not). I understood > this SQLAlchemy forces you to write your own class methods wrap > meta.Session - but this isn't cool :P because i waste my time :P
Don't wrap meta.Session. That's a silly thing to do. The semantics of the session and the sematics of your object are *completely* seperate things. In SQLAlchemy, your model objects don't save themselves - the session commits their data. It seems like you're putting a square peg in a round hole. -- Ross Vandegrift [email protected] "If the fight gets hot, the songs get hotter. If the going gets tough, the songs get tougher." --Woody Guthrie --~--~---------~--~----~------------~-------~--~----~ You received this message because you are subscribed to the Google Groups "pylons-discuss" 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/pylons-discuss?hl=en -~----------~----~----~----~------~----~------~--~---
