Re: Re: 2 csets were pushed to core/stable: [email protected]:/var/bk/xaraya...

Michael Cortez wrote:
> ...
> YES!!!!!!!
> 
> 
> 
> YES!!!!!!!!!!!!!!!!
> 
> 
> 
> Oh, did I mention, YES!!!!!!!!!!!!
> 
Hehe - guess that's clear :-)

> 
> Or at least some way of storing Configuration data -- don't know if just
> shoving more info into a TEXT field is the right way to do it though.
>
Well, you could have a table extension to store more configuration
options per property, but if you take the ever-growing list of
configuration options for articles pubtypes as an example, I found that
using a serialized text field for them was by far the easiest to handle.

Especially now that you have the ability to provide your own
configuration form for the validation field of each property type -
have a look at the new "subform" property type for instance... :-)

> Didn't even really notice it was 254, been storing all kinds of things
> in there -- just lucky to have not bumped up against the max I guess.
> 
Well, it's been an issue for e.g. the Select property type for a while
now - sometimes people had to create an API function and call it just
because they ran out of space in the validation field.

BTW, the xar_prop_validation field in the xar_dynamic_properties_def
table would also need to be increased accordingly. Care to help me
figure out how to change column types with xarDataDict ? :-)

Mike.