R
Rob Morris
Does anyone have a decent resolution to data layer
handling of stored procedures with inner and outer joins?
handling of stored procedures with inner and outer joins?
You are using an out of date browser. It may not display this or other websites correctly.
You should upgrade or use an alternative browser.
You should upgrade or use an alternative browser.
S
Steve S
retrieving the data shouldn't be an issue........
Inserts, updates and deletes...... are a different story....... the SP
almost needs to be a program within itself...... to deal with FIELDS......
and it combines them up into the appropriate SQL statements..... for the
various tables
If you provided just a little more info on what your doing with the join....
it would be easier to assist.........
Inserts, updates and deletes...... are a different story....... the SP
almost needs to be a program within itself...... to deal with FIELDS......
and it combines them up into the appropriate SQL statements..... for the
various tables
If you provided just a little more info on what your doing with the join....
it would be easier to assist.........
R
Robert Morris
I agree it shouldn't be an issue ... and thanks for your
response.
Here is the problem, I have several middle-tiers and none
that required so much compatibility with existing "stuff"
as this one. I am dealing with stored procedures that may
have multiple table aliases to the same table. When I
return the data to the object layer I need to identify
fields with the same name uniquely, preferably by the
table alias. There was a way, I think, in ADODB to get
the table aliases. I can not seem to find a way to do
this in ADO.NET.
Any help is appreciated greatly,
- Rob
response.
Here is the problem, I have several middle-tiers and none
that required so much compatibility with existing "stuff"
as this one. I am dealing with stored procedures that may
have multiple table aliases to the same table. When I
return the data to the object layer I need to identify
fields with the same name uniquely, preferably by the
table alias. There was a way, I think, in ADODB to get
the table aliases. I can not seem to find a way to do
this in ADO.NET.
Any help is appreciated greatly,
- Rob
S
Steve S
Within the four different DBs that I have played with, when there is naming
issues of the columns, the DBs have resolved it typically with a "1" or
"A/B" attached to the end of the column name......
(Select * from Customer, Orders)... would result in the customerID to be
recalled twice..... hence two columns, different names..... a 1 & 2
....... or an A & B versions..... one from each table
As far as I'm aware, the DB table names are not available as part of the
dataset/datatable structure....
The DB table used to be available through VB6 and ADODB recordsets.... as
long as it was still connected to the database... but lost that as soon as
the recordset crossed over a process boundry (or so that was our
experience).
HTH....... aloha
issues of the columns, the DBs have resolved it typically with a "1" or
"A/B" attached to the end of the column name......
(Select * from Customer, Orders)... would result in the customerID to be
recalled twice..... hence two columns, different names..... a 1 & 2
....... or an A & B versions..... one from each table
As far as I'm aware, the DB table names are not available as part of the
dataset/datatable structure....
The DB table used to be available through VB6 and ADODB recordsets.... as
long as it was still connected to the database... but lost that as soon as
the recordset crossed over a process boundry (or so that was our
experience).
HTH....... aloha
R
Robert Morris
Steve, Thank you very much, I got the 1,2 thing but I
have a feeling that I am going to have to make an ADODB
call till they can get their act straight, thanks!
have a feeling that I am going to have to make an ADODB
call till they can get their act straight, thanks!