<html> <head> <base href="https://bugs.documentfoundation.org/"> </head> <body> <div> <a class="bz_bug_link bz_status_NEW " title="NEW - Data Records Not Saved to External Firebird Database File" href="https://bugs.documentfoundation.org/show_bug.cgi?id=106463#c16">Comment # 16</a> on <a class="bz_bug_link bz_status_NEW " title="NEW - Data Records Not Saved to External Firebird Database File" href="https://bugs.documentfoundation.org/show_bug.cgi?id=106463">bug 106463</a> from <a class="email" href="mailto:drewjensen.inbox@gmail.com" title="Drew Jensen <drewjensen.inbox@gmail.com>"> Drew Jensen</a> <pre>(In reply to Robert Großkopf from <a href="show_bug.cgi?id=106463#c15">comment #15</a>) > *** <a class="bz_bug_link bz_status_RESOLVED bz_closed" title="RESOLVED DUPLICATE - EDITING: Saving data into FB3.0 file impossible when only writing data into a table" href="show_bug.cgi?id=122967">Bug 122967</a> has been marked as a duplicate of this bug. *** So - as a work around (scripting vs core code fix) for this there are three approaches that I see as fairly straightforward. 1 - catch the close file event and check if it is an ODB with firebird_file sdbc and issue a commit against the connection prior to releasing it. (though I have not tested if that even is called before the connection is closed I believe it is) or 2 - catch the sub_component close event inside the ODB and issue a commit. (I prefer this one) or 3 - catch the file save event for individual ODB files by updating the properties of the physical files and issue the commit. (easiest script to write and it works) Maybe this merits a post on the ask.lo service with example script for those.</pre> </div> <hr> You are receiving this mail because: <ul> <li>You are the assignee for the bug.</li> </ul> </body> </html>