Actually, many good databases are not a collection of tables.  That is what
is new about SQL and its relation to the first order predicate calculus.
The new thing about SQL was that there were multiple files and the
normalization rules established via the rules of the first order predicate
calculus are there to make sure that each data entry is solitary, or else
you have to deal with multiple data entries or deletions, etc.  So, a person
who talks about Spring, Hibernate and Struts may claim they "know" that a
database is a collection of tables, but what they "know" would be false if
put as a general statement.  From the way you ask questions, tossing names
of applications around like famous people names at a cocktail party, it is
hard to tell what you are doing.  So, despite the fact that I don't have a
lot of good feelings about Larry, I support his attitude in this case.  Why
don't you forget the "smart talk" about applications and just tell us in
English what you need to do and what your situation is?  If you do that, I
would be glad to help.  If you don't, good luck.

On 4/7/06, olonga henry <[EMAIL PROTECTED]> wrote:
>
> Larry, person who talks about Spring, Hibernate and struts and know about
> JTA certainly knows that a database is a collection of tables.
>
> On 4/7/06, olonga henry <[EMAIL PROTECTED]> wrote:
> >
> >  No, I am using Hibernate 3 and there are a lot of advantages you get
> from
> > using a complete ORM solution like this compared to Ibatis.
> > No, I am forced to use two databases Ticket (MySql) and Employee(AS/400,
> > legacy info).  I have no choice here.
> >
> >
> >  On 4/7/06, Larry Meadors <[EMAIL PROTECTED]> wrote:
> > >
> > > All you want is a list of tickets by employeeId with the employee
> name?
> > >
> > > You confused us all with the database term, I guess - if I am reading
> > > your question correctly, you mean two tables, not two databases (a
> > > database is a collection of tables).
> > >
> > > Keep it simple - use iBATIS (or jdbc) and put the results into a map:
> > >
> > > <select id='getTicketsByEmployeeId' resultclass=" java.util.HashMap">
> > > select t.*, employee.name
> > > from ticket t
> > > join employee e on t.employeeId = e.employeeid
> > > where e.employeeid = #value#
> > > </select>
> > >
> > > Done. One (indexed and very fast) hit on the database and you are
> done.
> > >
> > > Larry
> > >
> > >
> > > On 4/7/06, olonga henry <[EMAIL PROTECTED]> wrote:
> > > > Neither. List of open tickets that can belong to any employee.
> > > > It's just happens that I want to display the name of the employee
> > > instead of
> > > > their Ids.  I have been telling this in every email.  But you people
> > > don't
> > > > seem to get this.
> > > >
> > > >
> > > >
> > > > On 4/7/06, Rick Reumann <[EMAIL PROTECTED] > wrote:
> > > > >
> > > > > olonga henry wrote the following on 4/7/2006 10:21 AM:
> > > > > > After getting the ticket list, I will have to read the
> employeeIds
> > > first
> > > > > in
> > > > > > memory then make those calls and put 'em in a hashmap so that I
> > > can
> > > > > disply
> > > > > > 'em properly in the hashmap.
> > > > >
> > > > > I've been following this thread, and it's amazing how
> > > overcomplicated
> > > > > people are making all of this. I'd love to know exactly from a
> > > "user's
> > > > > perspective" what you want to accomplish ologna. All of this
> "don't
> > > use
> > > > > a join" nonsense is just silly (to be polite:) Although, more than
> > > > > likely you don't need to get everything back on the initial
> display
> > > of
> > > > > your employees.
> > > > >
> > > > > Do you just want to display an Employee record and a list of
> tickets
> > > > > that belong to the employee????
> > > > >
> > > > > --
> > > > > Rick
> > > > > http://www.learntechnology.net
> > > > >
> > > > >
> > > ---------------------------------------------------------------------
> > > > > To unsubscribe, e-mail: [EMAIL PROTECTED]
> > > > > For additional commands, e-mail: [EMAIL PROTECTED]
> > > > >
> > > > >
> > > >
> > > >
> > >
> > > ---------------------------------------------------------------------
> > > To unsubscribe, e-mail: [EMAIL PROTECTED]
> > > For additional commands, e-mail: [EMAIL PROTECTED]
> > >
> > >
> >
>
>


--
"You can lead a horse to water but you cannot make it float on its back."
~Dakota Jack~

Reply via email to