Opps... <br><br>Let's keep this on the list.<br>
<br><div class="gmail_quote">On Fri, Apr 1, 2011 at 9:06 AM, Chris Nighswonger <span dir="ltr"><<a href="mailto:cnighswonger@foundations.edu">cnighswonger@foundations.edu</a>></span> wrote:<br><blockquote class="gmail_quote" style="margin: 0pt 0pt 0pt 0.8ex; border-left: 1px solid rgb(204, 204, 204); padding-left: 1ex;">
<div class="gmail_quote"><div class="im">On Fri, Apr 1, 2011 at 8:37 AM, Archives and Collections Society <span dir="ltr"><<a href="mailto:paul.a@aandc.org" target="_blank">paul.a@aandc.org</a>></span> wrote:<br></div>
<blockquote class="gmail_quote" style="margin: 0pt 0pt 0pt 0.8ex; border-left: 1px solid rgb(204, 204, 204); padding-left: 1ex;"><div class="im">
<div>At 11:41 AM 4/1/2011 +0700, <a href="mailto:hansbkk@gmail.com" target="_blank">hansbkk@gmail.com</a> wrote:<br></div></div><div class="im"><div><blockquote class="gmail_quote" style="margin: 0pt 0pt 0pt 0.8ex; border-left: 1px solid rgb(204, 204, 204); padding-left: 1ex;">
Or is there some Koha-specific way of handling this?<br>
</blockquote>
<br></div>
Not to my knowledge (Chris?) - but in general for other mysql usage (e.g. our accounting system) there has been no problem for the 12 years I've been running the system. Philosophically, most Koha writes as far as I can see will be from Java scripts processed by perl, and my experience tells me that these are "near instantaneous" so while your example of table A and table B is a possibility, pure corruption is unlikely. And ... any backup is better than none.<br>
</div></blockquote></div><br>If you're really concerned in this regard you could implement some sort of WAL archiving which should allow you to roll back incomplete transactions if I understand it correctly.<br><br>
Kind Regards,<br><font color="#888888">
Chris<br>
</font></blockquote></div><br>