Re: Model/DB synchronization (was: Migrations (was: ERXSQLHelper))
Re: Model/DB synchronization (was: Migrations (was: ERXSQLHelper))
- Subject: Re: Model/DB synchronization (was: Migrations (was: ERXSQLHelper))
- From: OC <email@hidden>
- Date: Tue, 20 Jan 2015 13:50:51 +0100
Samuel,
On 15. 1. 2015, at 14:49, Samuel Pelletier <email@hidden> 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 (email@hidden)
Help/Unsubscribe/Update your Subscription:
This email sent to email@hidden