| Groups | Blog | Home |
dotnet ado.net : Named Recordsets from SProcs?
etc. to their correct names. The rowsets being returned from the SP don't have names so ADO has no way of knowing what to call them. Not all rowsets are simply SELECT * FROM myTable queries. -- ____________________________________ William (Bill) Vaughn Author, Mentor, Consultant Microsoft MVP www.betav.com Please reply only to the newsgroup so that others can benefit. This posting is provided "AS IS" with no warranties, and confers no rights. __________________________________ [quoted text, click to view] "A Traveler" <hitchhikersguideto-news@yahoo.com> wrote in message news:OhaMTW3jEHA.3968@TK2MSFTNGP11.phx.gbl... > Hello, > > I have a SQL Server stored procedure which will return several recordsets > back to the caller (multiple SELECT statements). > By default when you call this stored proc from ADO.NET, you get back the > tables in the DataSet as Table, Table1, Table2, etc.... > Is there anyway in the sproc that i can name them so that when they come > back to ADO, the DataSet contains them with friendly names, like > TBL_HEADER, TBL_DETAILS, TBL_LOCATIONS, etc.... ?? > > Thanks in advance, > > - Hitchhiker. >
Hello,
I have a SQL Server stored procedure which will return several recordsets back to the caller (multiple SELECT statements). By default when you call this stored proc from ADO.NET, you get back the tables in the DataSet as Table, Table1, Table2, etc.... Is there anyway in the sproc that i can name them so that when they come back to ADO, the DataSet contains them with friendly names, like TBL_HEADER, TBL_DETAILS, TBL_LOCATIONS, etc.... ?? Thanks in advance, - Hitchhiker.
Yah, i know they could get more complex, i just thought maybe there was some
way to do something like SELECT * FROM (SELECT whatever whatever) AS MYTableName Oh well... thanks anyway for ALL your help on my questions thus far. [quoted text, click to view] "William (Bill) Vaughn" <billvaRemoveThis@nwlink.com> wrote in message news:%23TIlkr3jEHA.3724@TK2MSFTNGP11.phx.gbl... > Nope, but you can change the TableMappings collection to map Table, Table1 > etc. to their correct names. The rowsets being returned from the SP don't > have names so ADO has no way of knowing what to call them. Not all rowsets > are simply SELECT * FROM myTable queries. > > -- > ____________________________________ > William (Bill) Vaughn > Author, Mentor, Consultant > Microsoft MVP > www.betav.com > Please reply only to the newsgroup so that others can benefit. > This posting is provided "AS IS" with no warranties, and confers no > rights. > __________________________________ > > "A Traveler" <hitchhikersguideto-news@yahoo.com> wrote in message > news:OhaMTW3jEHA.3968@TK2MSFTNGP11.phx.gbl... >> Hello, >> >> I have a SQL Server stored procedure which will return several recordsets >> back to the caller (multiple SELECT statements). >> By default when you call this stored proc from ADO.NET, you get back the >> tables in the DataSet as Table, Table1, Table2, etc.... >> Is there anyway in the sproc that i can name them so that when they come >> back to ADO, the DataSet contains them with friendly names, like >> TBL_HEADER, TBL_DETAILS, TBL_LOCATIONS, etc.... ?? >> >> Thanks in advance, >> >> - Hitchhiker. >> > >
No problem. Just consider that it's bad form to do a SELECT * and especially
without a WHERE clause. IMHO the "DataTable" should have been called the "DataRowset" object. This way developers would know it's designed for rowsets, not entire tables. Sure, there are cases when the database is simple that fetching the whole table makes sense. It doesn't in production systems that you expect to scale. -- ____________________________________ William (Bill) Vaughn Author, Mentor, Consultant Microsoft MVP www.betav.com Please reply only to the newsgroup so that others can benefit. This posting is provided "AS IS" with no warranties, and confers no rights. __________________________________ [quoted text, click to view] "A Traveler" <hitchhikersguideto-news@yahoo.com> wrote in message news:%23ya28%233jEHA.4092@TK2MSFTNGP10.phx.gbl... > Yah, i know they could get more complex, i just thought maybe there was > some way to do something like > > SELECT * FROM (SELECT whatever whatever) AS MYTableName > > Oh well... thanks anyway for ALL your help on my questions thus far. > > > "William (Bill) Vaughn" <billvaRemoveThis@nwlink.com> wrote in message > news:%23TIlkr3jEHA.3724@TK2MSFTNGP11.phx.gbl... >> Nope, but you can change the TableMappings collection to map Table, >> Table1 etc. to their correct names. The rowsets being returned from the >> SP don't have names so ADO has no way of knowing what to call them. Not >> all rowsets are simply SELECT * FROM myTable queries. >> >> -- >> ____________________________________ >> William (Bill) Vaughn >> Author, Mentor, Consultant >> Microsoft MVP >> www.betav.com >> Please reply only to the newsgroup so that others can benefit. >> This posting is provided "AS IS" with no warranties, and confers no >> rights. >> __________________________________ >> >> "A Traveler" <hitchhikersguideto-news@yahoo.com> wrote in message >> news:OhaMTW3jEHA.3968@TK2MSFTNGP11.phx.gbl... >>> Hello, >>> >>> I have a SQL Server stored procedure which will return several >>> recordsets back to the caller (multiple SELECT statements). >>> By default when you call this stored proc from ADO.NET, you get back the >>> tables in the DataSet as Table, Table1, Table2, etc.... >>> Is there anyway in the sproc that i can name them so that when they come >>> back to ADO, the DataSet contains them with friendly names, like >>> TBL_HEADER, TBL_DETAILS, TBL_LOCATIONS, etc.... ?? >>> >>> Thanks in advance, >>> >>> - Hitchhiker. >>> >> >> > >
Yeah. i dont generally do unfiltered SELECT *'s except on things like lookup tables where its just a small set of ID/TEXT combinations. [quoted text, click to view] "William (Bill) Vaughn" <billvaRemoveThis@nwlink.com> wrote in message news:OfkkON6jEHA.2652@TK2MSFTNGP15.phx.gbl... > No problem. Just consider that it's bad form to do a SELECT * and > especially without a WHERE clause. IMHO the "DataTable" should have been > called the "DataRowset" object. This way developers would know it's > designed for rowsets, not entire tables. Sure, there are cases when the > database is simple that fetching the whole table makes sense. It doesn't > in production systems that you expect to scale. > > -- > ____________________________________ > William (Bill) Vaughn > Author, Mentor, Consultant > Microsoft MVP > www.betav.com > Please reply only to the newsgroup so that others can benefit. > This posting is provided "AS IS" with no warranties, and confers no > rights. > __________________________________ > > "A Traveler" <hitchhikersguideto-news@yahoo.com> wrote in message > news:%23ya28%233jEHA.4092@TK2MSFTNGP10.phx.gbl... >> Yah, i know they could get more complex, i just thought maybe there was >> some way to do something like >> >> SELECT * FROM (SELECT whatever whatever) AS MYTableName >> >> Oh well... thanks anyway for ALL your help on my questions thus far. >> >> >> "William (Bill) Vaughn" <billvaRemoveThis@nwlink.com> wrote in message >> news:%23TIlkr3jEHA.3724@TK2MSFTNGP11.phx.gbl... >>> Nope, but you can change the TableMappings collection to map Table, >>> Table1 etc. to their correct names. The rowsets being returned from the >>> SP don't have names so ADO has no way of knowing what to call them. Not >>> all rowsets are simply SELECT * FROM myTable queries. >>> >>> -- >>> ____________________________________ >>> William (Bill) Vaughn >>> Author, Mentor, Consultant >>> Microsoft MVP >>> www.betav.com >>> Please reply only to the newsgroup so that others can benefit. >>> This posting is provided "AS IS" with no warranties, and confers no >>> rights. >>> __________________________________ >>> >>> "A Traveler" <hitchhikersguideto-news@yahoo.com> wrote in message >>> news:OhaMTW3jEHA.3968@TK2MSFTNGP11.phx.gbl... >>>> Hello, >>>> >>>> I have a SQL Server stored procedure which will return several >>>> recordsets back to the caller (multiple SELECT statements). >>>> By default when you call this stored proc from ADO.NET, you get back >>>> the tables in the DataSet as Table, Table1, Table2, etc.... >>>> Is there anyway in the sproc that i can name them so that when they >>>> come back to ADO, the DataSet contains them with friendly names, like >>>> TBL_HEADER, TBL_DETAILS, TBL_LOCATIONS, etc.... ?? >>>> >>>> Thanks in advance, >>>> >>>> - Hitchhiker. >>>> >>> >>> >> >> > >
Don't see what you're looking for? Try a search.
|
June 2003
July 2003
August 2003
September 2003
October 2003
November 2003
December 2003
January 2004
February 2004
March 2004
April 2004
May 2004
June 2004
July 2004
August 2004
September 2004
October 2004
November 2004
December 2004
January 2005
February 2005
March 2005
April 2005
May 2005
June 2005
July 2005
August 2005
September 2005
October 2005
November 2005
December 2005
January 2006
February 2006
March 2006
April 2006
May 2006
June 2006
July 2006
August 2006
September 2006
October 2006
November 2006
December 2006
January 2007
February 2007
March 2007
April 2007
May 2007
June 2007
July 2007
August 2007
September 2007
October 2007
November 2007
December 2007
January 2008
February 2008
March 2008
April 2008
| home · blog · groups | Questions? Comments? Contact the dn |