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 relate to that… which sorta defeats the purpose of using an enum. Ramsey On Jul 21, 2012, at 8:25 AM, Tim Worman wrote: > 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. Then, in the > database have only those selections saved to the database. > > Tim > UCLA GSE&IS > > _______________________________________________ > Do not post admin requests to the list. They will be ignored. > Webobjects-dev mailing list ([email protected]) > Help/Unsubscribe/Update your Subscription: > https://lists.apple.com/mailman/options/webobjects-dev/ramseygurley%40gmail.com > > This email sent to [email protected] _______________________________________________ Do not post admin requests to the list. They will be ignored. Webobjects-dev mailing list ([email protected]) Help/Unsubscribe/Update your Subscription: https://lists.apple.com/mailman/options/webobjects-dev/archive%40mail-archive.com This email sent to [email protected]
