Hi, On Thu, Nov 20, 2008 at 3:20 AM, Paul POULAIN <paul.poulain@free.fr> wrote:
Mason James a écrit :
Hi folks
Any objections to bumping the authorised_values.category column to say.. 20 chars??
I'm having to make my new auth categories a little terse/cryptic because of the current 10 char limit
No objection, but note that borrower_attribute_types.authorised_value_category would also have to be expanded. To modify the suggestion slightly, how about keeping the current length of authorised_value.category and creating a new authorised_value_categories table: CREATE table authorised_value_categories ( category varchar(10) NOT NULL, description varchar(80), module varchar(10), PRIMARY KEY (category), KEY module_idx (module) ); This gives us a longer description, and we can make authorised_value.category a foreign key. The module column would be used to implement Paul's idea.
I think it's a good idea. Another idea I have would be to add a "module" field, to separate the different uses of auth values : - cataloguing - acquisitions - members [snip]
-- Galen Charlton VP, Research & Development, LibLime galen.charlton@liblime.com p: 1-888-564-2457 x709 skype: gmcharlt