Re: Enterprise objects stored in JSON or byte
Re: Enterprise objects stored in JSON or byte
- Subject: Re: Enterprise objects stored in JSON or byte
- From: Jesse Tayler <email@hidden>
- Date: Wed, 19 Dec 2018 10:49:17 -0500
Hi Mark
Sounds interesting, I was wondering a while back if an eomodel could work on
top of a database like Mongo and store anything without need for migration or
table setup - but it sounds like you want the reverse?
You sort of want to have arbitrary attributes? Even arbitrary relationships?
What’s the relation to EOF? These then must be made persistent regardless of
structure?
I’m trying to imagine what you’re after a bit but modeler could be thought of
as an editor for EOEntities which are meant to be structured and could just as
easily be created in memory vs. loaded from a model file but I’d wonder why
> On Dec 19, 2018, at 10:39 AM, Mark Wardle <email@hidden> wrote:
>
> I want to define a group enterprise objects at runtime and yet use them in a
> fairly similar way to "normal" enterprise objects.
>
> Essentially, I want a generic object that is backed by a NSDictionary (or
> other persistence mechanism like bytes/protobuf) and has a defined behaviour
> class. I would like to define the model at runtime rather than using
> EOModeler. The definition of the object (list of properties and for each
> property: name, dataType, class, prototype etc.) defined itself at runtime in
> the backing database.
>
> Anyone done something similar, and if so, what is the best approach? I have
> contemplated building a generic EO that delegates its behaviour and data to
> the behaviour class and the backing NSDictionary respectively, and alters the
> implementation of KVC to make it fairly transparent. I'm aware that some of
> the hidden "magic" that comes from defining an object in EOModeler might be
> lost.
>
> Any hints/tips gratefully received!
>
> Best wishes,
>
> Mark
>
>
>
> _______________________________________________
> 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
_______________________________________________
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