yes,
I know that looks inconsistent, but it's a function of how metabase does its
schema detinition format.
I like to use only true/false. (thus the <required> value).
Metabase's field defs need
<notnull>1</notnull>
or
<notnull>0</notnull>
so I'm not being schitzo, I'm trying to satisfy metabase while maintaining
standard as best I can :)
btw: true/false is the gold standard everywhere for booleans.
_a
>
> A 'little' thing i noticed as i was looking at the entity definition
> again...
>
> I'm noticing a slight indifference to boolean values.
>
> Here we see true/false:
>
> <!-- must this field be valid to do a post of this entity? -->
> <required>true</required>
>
> Yet here we use 0/1:
>
> <!-- is this the default field in the db table? -->
> <default>0</default>
> <!-- can the field be null? -->
> <notnull>1</notnull>
>
>
> While the parser does not care, it sure would be nice to have a standard
> boolean value.
> The above example may be the only case, but I would imagine that there
> are other places where this is true. (no pun intended)
>
> jason
>
> _______________________________________________
> binarycloud-dev mailing list
> bin...@li...
> https://lists.sourceforge.net/lists/listinfo/binarycloud-dev
>
|
