On Jul 21, 2012, at 1:30 PM, Kieran Kelleher kelleh...@gmail.com wrote:
On Jul 21, 2012, at 3:30 PM, Tim Worman li...@thetimmy.com wrote:
Thanks Ramsey.
Yeah. I would really need a many-to-many relationship - which I was hoping
to avoid. :-) I was wanting to just store and query keywords
WO'ers:
I have an Enitity that I would like to assign n categories to - essentially
descriptive strings. I have never used the javaEnum prototype and I was
wondering if it would be good for this task? On the UI side I would like to use
checkboxes to select which categories to apply to an EO.
For a 'to-one' type of arrangement, enums are perfect so long as your
categories don't change often.
For a 'to-many' you are describing, they are less so. You could serialize an
enum set, but then you can't query it. The only other solution I know of would
be to put them on a table and
And iirc avoid null values in enums or will throw exception on save. Set a
default value in the init() method of entity
Sent from my iPhone
On 21/lug/2012, at 18:24, Ramsey Gurley ramseygur...@gmail.com wrote:
For a 'to-one' type of arrangement, enums are perfect so long as your
categories
Thanks Ramsey.
Yeah. I would really need a many-to-many relationship - which I was hoping to
avoid. :-) I was wanting to just store and query keywords for my EO. A
flattened many-to-many seems heavy to just associate string values. A good
example would be a Contact entity where you maybe have
On Jul 21, 2012, at 3:30 PM, Tim Worman li...@thetimmy.com wrote:
Thanks Ramsey.
Yeah. I would really need a many-to-many relationship - which I was hoping to
avoid. :-) I was wanting to just store and query keywords for my EO. A
flattened many-to-many seems heavy to just associate
