Re: Creating a EOModel in code
Re: Creating a EOModel in code
- Subject: Re: Creating a EOModel in code
- From: Hugi Thordarson via Webobjects-dev <email@hidden>
- Date: Fri, 26 Jun 2020 19:27:59 +0000
> Ok, so are all the cool guys using Cayenne now then?
I've seen some pretty cool guys use it but I also use it.
> I'm sure I should read some page about it rather than waste everyone’s time
> reiterating why it’s better and why we should be moving to that sort of thing
> etc.
It's awesome in so many ways. But for people that already know EOF, it's
probably best described as "EOF without that darned locking thing". And there's
seriously exciting stuff happening in the most recent releases (subqueries,
SQL-functions and more, all type safe using "Properties", the Cayenne version
of ERXKey.
API-wise it can pretty much be a drop-in replacement for EOF and from
experience I can say there's nothing to lose and much to gain. (assuming you're
using an SQL db. Cayenne is explicitly an SQL DB framework, not a "generic
everything framework" like EOF wants to be).
- hugi
>> On Jun 26, 2020, at 3:10 PM, Hugi Thordarson via Webobjects-dev
>> <email@hidden> wrote:
>>
>> You might also want to take a look at Cayenne. It's well documented and
>> we're eager to help where the docs fall short. And most importantly; it's an
>> active and maintained project that didn't die over a decade ago :)
>>
>> - hugi
>>
>>
>>
>>> On 26 Jun 2020, at 19:04, Aaron Rosenzweig via Webobjects-dev
>>> <email@hidden> wrote:
>>>
>>> Hi Don,
>>>
>>> Have a look at EOEntity and friends: EOAttribute, EORelationship.
>>>
>>> You can build them out and setup the “external” name for the column, etc. I
>>> did it once as an exercise many moons ago. The only practical use I got out
>>> of it was sometimes sanity checking keyPaths to see if they hit things “in
>>> memory” or if they were completely traversable through EOEntity
>>> relationships. Something that trips an in-memory method call is not
>>> something you can use to build a complex SQL query.
>>>
>>> Like other people have said, the “reverse engineering” of the original WO
>>> tools is more likely what you want to use instead. You point Entity Modeler
>>> at a database and it can make a surprisingly good model file from it.
>>> Depending on how big the database is… it might be worth your trouble of
>>> firing up MacOS Tiger and installing the NeXTStep GUI tools to do the
>>> reverse engineering. I don’t think that the Eclipse java based
>>> EntityModeler can reverse engineer. I don’t know if Cayenne can reverse
>>> engineer.
>>> AARON ROSENZWEIG / Chat 'n Bike
>>> e: email@hidden t: (301) 956-2319
>>>
>>>
>>>> On Jun 25, 2020, at 8:53 PM, Don Lindsay via Webobjects-dev
>>>> <email@hidden> wrote:
>>>>
>>>> Hello;
>>>>
>>>> The Documentation for EOModel states that you can build one in code, but
>>>> there are no examples or further information that I can find. Does anyone
>>>> have any documentation or samples that they can direct me to so I can
>>>> create EOModels while the application is running:
>>>>
>>>> What I want to do is connect to a database that my app does not know
>>>> about, someone provides connection parameters and I create an EOModel and
>>>> connect to that database or rest and access it using the EOModel created
>>>> using new EOModel().
>>>>
>>>> Thanks
>>>>
>>>> Don
>>>> _______________________________________________
>>>> 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
>>
>> _______________________________________________
>> 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