oqgraph-dev team mailing list archive

[Arjen Lentz <arjen@xxxxxxxxxxxxx>]

I'd prefer a string, because we need to check the table structure, with enum there could be differences. Also messier over time.

Antony T Curtis <atcurtis@xxxxxxxxx> wrote:

>
>On 11 Feb, 2013, at 6:45 pm, Arjen Lentz wrote:
>
><snip>
>> 
>>> Arjen> We'll probably also change the latch column from an integer to
>>> a string. We can keep it backward compatible at least from the app
>>> perspective, allowing for "1" and the other values in the form of
>>> strings.
>> 
>
>If the latch column is defined as an ENUM(), they would have logical numeric identities in addition to the string label.
>
>(It would essentially be a very quick change to enable this in the code... little to no change is required in the storage engine other than to permit the declaration of the latch column as an enum,
>
>
>Antony T Curtis
>atcurtis@xxxxxxxxx
>
>0523 C487 9187 6972 6894
>AEC7 3087 F819 B477 B687
>