Re: EOModeler
Re: EOModeler
- Subject: Re: EOModeler
- From: Arturo Pérez <email@hidden>
- Date: Mon, 12 Jan 2004 00:05:35 -0500
On Jan 11, 2004, at 11:54 PM, james cicenia wrote:
On Jan 11, 2004, at 10:27 PM, Arturo Pirez wrote:
On Jan 11, 2004, at 10:24 PM, james cicenia wrote:
Arturo,
I do understand what you are suggesting. But wouldn't it just be
quicker
and easier to use the database for this? In other words, my graph
object
would just issues a simple, for example:
Select count(department) from project_request
where status=open group by department.
And then just turn this simple result into a list which would be part
of my graph object?
-James
I seem incapable of crafting a response that won't seem condescending
or
that won't irritate you further. So just let me leave it at.
Sure. You can do that. The database IS good at that sort of thing.
But it's
the wrong approach.
LOL - You are such the purist!
It's funny. Everyone thinks I'm a purist. But I don't.
My approach is to write everything at a high level of abstraction. Use
your
toolset to the fullest. With WO as the toolset that means everything
is an
object. The benefit there is that your productivity is very high
because you're
not spending any time fighting against your toolset.
Then I benchmark. Then, if necessary, I recode in C that would make
you throw up.
My funnest moment ever came when I wrote some Java that looked like
assembler. It crashed
the IBM JVM but ran fine on Sun's. And was FAST! (task went from
300ms to 40ms).
So, purist, umm no :-) But I am lazy. Using the object features of WO
keeps me from
having to sweat over the SQL :-)
----
WO in philadelphia - wanna cheesesteak with that?
Please visit webobjects.meetup.com.
_______________________________________________
webobjects-dev mailing list | email@hidden
Help/Unsubscribe/Archives: http://www.lists.apple.com/mailman/listinfo/webobjects-dev
Do not post admin requests to the list. They will be ignored.