Al:
YES. I'm starting off with the hypothesis that all database tables
should map to EJBs, because that is what all the hype is about.
Now, for real world, does it work well?
Is you answer that one should make create an EJB that
is not CMP, but rather one supplies a hand crafter SQL
command somewhere in its member functions?
STeve Punte
e-Business Software Architect
Technologent Inc
[EMAIL PROTECTED]
----- Original Message -----
From: Al Fogleson <[EMAIL PROTECTED]>
To: Steven Punte <[EMAIL PROTECTED]>; Orion-Interest
<[EMAIL PROTECTED]>
Sent: Tuesday, May 23, 2000 6:34 PM
Subject: Re: How are database JOINS achieved with EJBs?
> you can do it the same way using BMP.
>
> Although I would be careful, I think we, as programmers have convinced
> ourselves that if something is in a database it MUST be an entity bean.
This
> attitude seems to prevail all over, even at my work, where I am having a
> heck of a time convincing people it is just not so, or doesnt have to be
:)
>
> Al
>
> ----- Original Message -----
> From: "Steven Punte" <[EMAIL PROTECTED]>
> To: "Orion-Interest" <[EMAIL PROTECTED]>
> Sent: Thursday, May 25, 2000 8:52 PM
> Subject: How are database JOINS achieved with EJBs?
>
>
> > Dear EJB Community:
> >
> > Entity java beans pretty much represent a row of data
> > in a database table.
> >
> > If one has:
> >
> > Table X Table Y
> > -------------- --------------
> > A B C D D E F G
> >
> > One commonly executes a SQL command like:
> >
> > select A from X join Y on X.D=Y.D where Y.G ="Bill Clinton"
> >
> > How would one do the equivalent task in an elegant
> > "Enterprise Java Bean" like manner? That is, other
> > than simply writing some member function that performs
> > a JDBC select command like above.
> >
> > Inquiring Minds Want To Know
> >
> > --
> > STeve Punte
> > e-Business Software Architect
> > Technologent Inc
> > [EMAIL PROTECTED]
> >
> >
