This weekend I'm using the import_cvs functionality I've created in a real
life situation (so far I had only tested it) to import a CoA setup.
What happened is that the csv file has encoding issues (not UTF-8). When I
tried uploading again, I found that half the CoA was already in the system,
while I had hoped that the failure would have caused the entire transaction
be be aborted.
Turns out the save() method of the DBObject::Account class commits after
inserting every account.
In my view, it's impractical to have library code issue commits. So, with
this mail I'm soliciting feedback how people think about it. In my view,
only the request handlers (ie 'top level code') should be issuing
$dbh->commit()s.
Let's set a policy here which we can apply throughout "new code".
Bye,
Erik.
------------------------------------------------------------------------------
This SF email is sponsosred by:
Try Windows Azure free for 90 days Click Here
http://p.sf.net/sfu/sfd2d-msazure
_______________________________________________
Ledger-smb-devel mailing list
[email protected]
https://lists.sourceforge.net/lists/listinfo/ledger-smb-devel
