Learn how easy it is to sync an existing GitHub or Google Code repo to a SourceForge project! See Demo

Close

#11 Defined values not always working as expected

open
nobody
None
5
2012-06-13
2012-06-13
Anonymous
No

Maybe it's a subtle "bug" that comes from nowhere, but in my installations the Table settings -> Field setting of a Defined choice does not work as expected.
Both the suggested rules:
VALUE_A
VALUE_B
VALUE_C
or
A=Label A
B=Label B
C=Label C

do not work. Another option is a better substitute for this one, the Values defined by table, which works very well.
As a workaround (or a better solution) for multiple choices which do not deserve a table by themselves, a table like the following could be used.
CREATE TABLE common_options (
cod varchar(10) primary key,
label varchar(60) unique,
usage varchar(10)
);
where usage contains the categories or domains of the choices.

Discussion