On 11/01/2013 20:01, Michael Bayer wrote:
On Jan 11, 2013, at 1:37 PM, Chris Withers wrote:
On 11/01/2013 15:26, Michael Bayer wrote:
what is it looking up ? what's a "myobj" ?
An unmapped instance of the mapped class.
yeah you don't want to have unmapped instances of mapped classes lying around.
Why? They're just objects.
It's really handy having domain objects that can exist without potentially ever
having to know about a database...
What's the downside of having unmapped objects around?
Beginning to suspect we have a terminology mismatch, an "unmapped" object of a
"mapped class" implies you are creating objects from a class before you've mapped the
class
Yep, terminology mismatch, that's why I gave the unit test example.
What's the correct way to refer to an instance of a mapped class but
that has never been anywhere near a session?
It's one of those I want to call the lookup method on with a session...
cheers,
Chris
--
Simplistix - Content Management, Batch Processing & Python Consulting
- http://www.simplistix.co.uk
--
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.
