Hi,
a new day, a new question. ;)
First of all: Should the data type "indicator" be interpreted as the
good old diode, glowing up to indicate s.o. s.th. special, or perhaps as
a kind of error level, like the DEFCONs with multiple meanings for each
level?
I for myself interpret it as a glowing diode and I'm wondering about the
SQL-type mapped to indicator: It's CHAR(1), but not BOOLEAN like (some)
databases would understand. Is there any background why CHAR(1) is used?
I know that MySQL didn't/doesn't(?) support BOOLEAN as type (for a long
time), but RDBMS like Postgres or Oracle support it and it's even
documented in the SQL-standard (Postgres docs say this.). Are there
perhaps any OFBiz-internal things which could cause serious problems
when using BOOLEAN?
Additionally I should say I'm developing on a Postgres-DB which will
changed to a Oracle-DB when the software will be productively used.
TIA
Best regards,
Fabian.
