Hi,
On Sep 3, 2010, at 4:03 PM, Chris Hobbs wrote:
The obvious fix would be to simply set branchcode to LOWER(branchcode) in the back end, but the foreign key constraint prevents me from doing so through mysql. A longer-term fix would be to figure out why it's not setting the branchcode correctly, but as far as cascading the update of branchcode is concerned, you could either alter the constraints to cascade updates or take advantage of MySQL's ability to disable foreign key checks temporarily:
SET FOREIGN_KEY_CHECKS = 0; Galen's direction on removing the foreign key checks temporarily got me
On 9/15/10 9:01 AM, Galen Charlton wrote: the ability to update branchcodes across all of my db tables, but I seem to have a problem with my zebra indexes - most of my items (those that have not been circulated since the conversion) do not have branch information visible information - here's a screen shot: http://www.nhusd.k12.ca.us/it/files/images/Screen%20shot%202010-09-23%20at%2... I have tried re-indexing in the hopes that it would work itself out (rebuild_zebra.pl -b -a -r) but no luck. Any idea how to get the correct (lowercase) branch info into the zebra indexes? Thanks, -- Chris Hobbs Director, Technology New Haven Unified School District -- This message was scanned by ESVA and is believed to be clean.