Paul,<br><div class="gmail_extra"><br><div class="gmail_quote"><blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex"><div class="im">
&gt; I just pushed bug 7167, which changes the way database updates work. I<br>
&gt; wrote up instructions for database updates<br>
&gt; at <a href="http://wiki.koha-community.org/wiki/Database_updates#Using_the_new_update_procedure" target="_blank">http://wiki.koha-community.org/wiki/Database_updates#Using_the_new_update_procedure</a><br>
&gt;<br>
&gt; Please be sure to read those instructions and follow them in the future.<br>
</div>Hi Jared, (and happy new year everyone !)<br>
<br>
How should be handle pending patches with a DB update ? (question asked<br>
for each role : submitter, signer, QAer)<br>
<br>
Should someone update the patch to use the new DB update schema ? if no,<br>
how should/can we test patches with the old schema ?<br>
<br>
( Thanks for pushing this patch though ! )<br></blockquote><div><br></div><div>Once the needed follow-ups are signed off and the feature is re-pushed, it will be the responsibility of the QAer to copy the database update from <a href="http://updatedatabase.pl">updatedatabase.pl</a> to a new-style update for SQL-only updates (for complex updates that are not simply copy-paste, we will probably have to send the patch back to the author for revision). For bugs that are not signed off, the author will need to move the database update, unless someone else volunteers to do it for them.</div>
<div><br></div><div>Also, I have a correction to Chris&#39;s response: we will not need two separate sets of DB changes because I will be copying every non-linear update into <a href="http://updatedatabase.pl">updatedatabase.pl</a>. That was the reason for the CheckVersion() routine.</div>
<div><br></div><div>Regards,</div><div>Jared</div><div><br></div></div>-- <br>Jared Camins-Esakov<div>Bibliographer, C &amp; P Bibliography Services, LLC</div><div>(phone) +1 (917) 727-3445</div><div>(e-mail) <a href="mailto:jcamins@cpbibliography.com" target="_blank">jcamins@cpbibliography.com</a></div>
<div>(web) <a href="http://www.cpbibliography.com/" target="_blank">http://www.cpbibliography.com/</a></div>
</div>