Re: Geting data from joined tables

Bill

I want to be able to do exactly what you recommend to avoid.

1) I don't want to be forced to hand-code field lists in select
statements.

2) I don't want that the code breaks if someone adds a column.

If I could do this within the JDBC API such as
Resultset.getString("t1.col1") than everything would be 100%.

In fact there is a database that just works like this. Look at
quadcap.com.

Regards

Bernard





"Bill" <wfs4@xxxxxxxxxxxxx> wrote:

Hi,

you normally never do a SELECT * - 'cos if someone adds a new column /
or rearranges the columns - you'd have problems.

How about

select t1.col1 as t1_col1,
t2.col2 as t2_coll1
from table_1 as t1
table_2 as t2
where t1.key = t2.key etc

Bill


"Bernd Treine" <bht@xxxxxxxxxxxxx> wrote in message
news:8qcmj2t30t4q1gcf5cg39fqbvmcvfju95t@xxxxxxxxxx
Hi all,

What would be the best method of getting data from a Resultset that
has multiple joined tables?

Example

select
t1.*,
t2.*
from
table1 t1,
table1 t2
where ....

The issue is that in SQL, I can distinguish between fields of t1 and
t2 although they have the same name. In JDBC I get an error.

I can't write:

Resultset.getString("t1.field1")
and
Resultset.getString("t2.field1")
Resultset just cannot distinguish the 2 fields by the "t1." qualifier.

I know I can work around with
Resultset.getString(columnIndex).

But that does not answer my question.

Many thanks

Bernard


.

Relevant Pages

  • Re: Testing for empty columns in resultset
    ... After populating a resultset with a query, what is the best way to test ... if a column is null to avoid the dreaded null pointer exception when ...
    (comp.lang.java.databases)
  • Testing for empty columns in resultset
    ... After populating a resultset with a query, what is the best way to test ... if a column is null to avoid the dreaded null pointer exception when ...
    (comp.lang.java.databases)
  • Re: Testing for empty columns in resultset
    ... After populating a resultset with a query, what is the best way to test ... if a column is null to avoid the dreaded null pointer exception when ...
    (comp.lang.java.databases)
  • Re: SET NOCOUNT ON OPTION
    ... It avoid that a procedure return more than one resultset, ... execute quickly. ... Your sp don't return any resultset than you shoul use it. ... > So is it good or bad to use SET NOCOUNT ON? ...
    (microsoft.public.dotnet.framework.aspnet)
  • Re: SET NOCOUNT ON OPTION
    ... >I tink that is better using it. ... > It avoid that a procedure return more than one resultset, ... > execute quickly. ... > Your sp don't return any resultset than you shoul use it. ...
    (microsoft.public.dotnet.framework.aspnet)