Pete,<div><br></div><div><br></div><div>You can report this issue to <a href="http://bugs.koha-community.org">http://bugs.koha-community.org</a>. I've checked, and there doesn't seem to be an existing report.</div>
<div><br></div><div><br></div><div>-Ian<br><br><div class="gmail_quote">On Tue, Nov 30, 2010 at 11:47 AM, Peter Huerter <span dir="ltr"><<a href="mailto:pete.huerter@gmail.com">pete.huerter@gmail.com</a>></span> wrote:<br>
<blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex;"><br>
Perhaps this is a bug, or at least an inconsistency between the items, and<br>
authorised_values SQL table schema.<br>
<br>
Koha allows you to define an authorised value having length 80, but then you<br>
can't use it.<br>
<br>
Here is why:<br>
<br>
The SQL field items.ccode is a varchar(10).<br>
<br>
The SQL field authorised_values.authorised_value is a varchar(80).<br>
<br>
If this is a bug, how can I go about opening a defect?<br>
<br>
Thanks,<br>
<br>
Pete.<br>
<font color="#888888">--<br>
View this message in context: <a href="http://koha.1045719.n5.nabble.com/SQL-field-lengths-tp3285076p3286344.html" target="_blank">http://koha.1045719.n5.nabble.com/SQL-field-lengths-tp3285076p3286344.html</a><br>
Sent from the Koha - Discuss mailing list archive at Nabble.com.<br>
</font><div><div></div><div class="h5">_______________________________________________<br>
Koha mailing list <a href="http://koha-community.org" target="_blank">http://koha-community.org</a><br>
<a href="mailto:Koha@lists.katipo.co.nz">Koha@lists.katipo.co.nz</a><br>
<a href="http://lists.katipo.co.nz/mailman/listinfo/koha" target="_blank">http://lists.katipo.co.nz/mailman/listinfo/koha</a><br>
</div></div></blockquote></div><br><br clear="all"><br>-- <br>Ian Walls<br>Lead Development Specialist<br>ByWater Solutions<br>Phone # (888) 900-8944<br><a href="http://bywatersolutions.com">http://bywatersolutions.com</a><br>
<a href="mailto:ian.walls@bywatersolutions.com">ian.walls@bywatersolutions.com</a><br>Twitter: @sekjal<br>
</div>