From: Matthew B. <mat...@co...> - 2005-04-29 17:39:48
|
Adam Marshall wrote: > We will fix this bug in the next week. We are going to release version > 2.4.3 probably around the end of next week and will include a shorter > name in response to your error report. I take it that this bug is from > version 2.4.2 of Bodington? 2.4.1 was the version he was using. This bug came in from version 1.3 of LogBookPage.sql (commited 12/08/2004). As the mapping between database columns and JavaBean properties is stored in the database we don't need to update current installations to fix this problem (unless there is hard coded SQL in LogBookFacility). All new installs should just have these trucated (remove the _id?). Leaving current installs along will probably come back to bite us if we don't alter the column names but it isn't essential for the bug fix. bodington=# select field, length(field) from fields where length(field )> 30; field | length -----------------------------------+-------- section_user_first_big_string_id | 32 section_user_last_big_string_id | 31 question_user_first_big_string_id | 33 question_user_last_big_string_id | 32 -- +--Matthew Buckett-----------------------------------------+ | VLE Developer, Learning Technologies Group | | Tel: +44 (0) 1865 283660 http://www.oucs.ox.ac.uk/ | +------------Computing Services, University of Oxford------+ |