On 2015-03-12 09:53 Michael Bayer <[email protected]> wrote: > which is why, “copy an object” is not an out of the box thing. Because > nobody really wants a full “copy”, it’s something custom.
As I described I don't want a "full copy". I only want to copy the "real data" handled by the user. All organizing/protocol data from SQLA or from me (e.g. the oid) as the developer shouldn't be copied. The use-case is simple: The user want to add new data which just differ a little from the last time data was added. So it is more ergonomic to offer a new-data-dialog with preset values from the last data-entry instead of an clean empty new-data-dialog. In the latter the user need to type in all data again but e.g. 80% of it is the same then yesterday. Understand? What do you think about this solution: <https://stackoverflow.com/questions/29039635/how-to-duplicate-an-sqlalchemy-mapped-object-the-correct-way> -- You received this message because you are subscribed to the Google Groups "sqlalchemy" group. To unsubscribe from this group and stop receiving emails from it, send an email to [email protected]. To post to this group, send email to [email protected]. Visit this group at http://groups.google.com/group/sqlalchemy. For more options, visit https://groups.google.com/d/optout.
