Samuel, On 15. 1. 2015, at 14:49, Samuel Pelletier <sam...@samkar.com> wrote:
> 1- Store additional attributes in a serialized map structure (json, > serialized php array, serialized java objects or property list). Precisely what I did. Works well, but is unacceptably slow (even if I cache unarchived dictionaries in EOs, fetching and unarchiving just the first time). > 2- Store the additional attributes in an dedicated entity with a commun > dictionary of attribute definitions. I use this approach in some specific cases (like e.g., file attachments), but to exploit it for all dynamic attributes I would fear all those joins would bring performance problems, too. Definitely I might be wrong, but I think a flat denormalized table would be consideraly faster. Thanks, OC _______________________________________________ Do not post admin requests to the list. They will be ignored. Webobjects-dev mailing list (Webobjects-dev@lists.apple.com) Help/Unsubscribe/Update your Subscription: https://lists.apple.com/mailman/options/webobjects-dev/archive%40mail-archive.com This email sent to arch...@mail-archive.com
