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: Mark Wardle <email@hidden>
- Date: Wed, 19 Dec 2018 16:15:44 +0000
[forgot to include list in my reply]
Good questions!
The issue is that I want to build runtime forms that are automatically
rendered via D2W.
I currently build data collection forms using horizontal inheritance, so I
define the model and then D2W and everything else normally "just works". I
sometimes add some custom logic or properties.
But that doesn't scale. So firstly, I have to edit the model, rebuild the
application and install it. Doesn't take long, but... Secondly, horizontal
inheritance doesn't scale, so that to find a list of objects, EOF has to
perform multiple selects (therefore I guess O(n)), so as I add another
"form", I add another table and another SELECT.
I decided that worrying about this when I started out, many years ago, was
premature optimisation, and I haven't yet hit a real performance hurdle,
but it will happen. The idea of defining or supplementing an EOModel at
runtime is quite attractive, but feels like it might be a bit complex!
Mark
On Wed, 19 Dec 2018 at 15:49, Jesse Tayler <email@hidden> wrote:
> 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
>
>
--
Dr. Mark Wardle
Consultant Neurologist and Clinical informatician, University Hospital
Wales, Cardiff, UK
Chair, NHS Wales Technical Standards Board.
Email: email@hidden or email@hidden Twitter: @mwardle
Telephone: 02920745274 (secretary) or facsimile: 02920744166
_______________________________________________
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