Thanks for swift response and ticket creation. Something like:
rec.store(Condition condition); would be very appreciated, though I see possible problems you already mentioned (update or insert, affect multiple rows?). Still, can there be either more control over record class (not necessarily in interface, let a programmer take the risk of throwing SQL exception when trying rec.update/rec.insert over a casted type not originally returned by Factory.fetch()) or provide more clever function like updateNew(condition)doing first select for condition and then update or insert. At least storing field array of a record is still useful, but you must identify/match the record in DB anyway, right?
