On 2/1/06, Wade Leftwich <[EMAIL PROTECTED]> wrote: > I think your questions are actually about SQL in general, not SqlAlchemy > in particular.
I'll freely admit that my knowledge of SQL and of relational theory in general is quite ad hoc. > The definition of a primary key is "a column or set of columns that > uniquely specifies a row". So if you update or delete based on a primary > key, you will affect zero or one rows, never more. This is the theory and in normal database operation it's the case. I was wondering about the edge case where there are identical rows in the database (though it may not have come out that way in the question) and Michael answered that by saying they'd get aggregated into the same object instance. This makes sense, I had one or two ideas on how it would work if this weren't the case, but happily it's not. Thanks for taking the time to answer my questions Michael. ------------------------------------------------------- This SF.net email is sponsored by: Splunk Inc. Do you grep through log files for problems? Stop! Download the new AJAX search engine that makes searching your log files as easy as surfing the web. DOWNLOAD SPLUNK! http://sel.as-us.falkag.net/sel?cmd=lnk&kid3432&bid#0486&dat1642 _______________________________________________ Sqlalchemy-users mailing list [email protected] https://lists.sourceforge.net/lists/listinfo/sqlalchemy-users
