J
Jarod
Hey
Will be in .net 2.0 any nice way to use stored procedures and get typed
dataset ?
Jarod
Will be in .net 2.0 any nice way to use stored procedures and get typed
dataset ?
Jarod
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.
C
Cor Ligthert [MVP]
Jarod,
Click on the generated dataset in the dataadapter part.
I hope this helps,
Cor
Click on the generated dataset in the dataadapter part.
I hope this helps,
Cor
G
Geoffrey Samper
Check out this link http://msdn2.microsoft.com/en-us/library/04y282hb
N
Nicholas Paldino [.NET/C# MVP]
Jarod,
In .NET 2.0 (or rather, Visual Studio .NET 2.0), you will be able to
drag your stored procedures into your design surface, and it will create
managed wrappers for them. It's definitely a nice feature.
Hope this helps.
In .NET 2.0 (or rather, Visual Studio .NET 2.0), you will be able to
drag your stored procedures into your design surface, and it will create
managed wrappers for them. It's definitely a nice feature.
Hope this helps.
T
The Crow
ok, we can do this by drag and drop a "select" stored procedure. how about
if we want to use stored procedures for insert and update as well? how about
our "select" stored procedure includes some logic (case when or if
statements based on some parameter etc.) ? how about if we dont want always
get same column set? do we have to generate, for each set of columns,
another dataset? i think VS.NET is not powerful enough when it cames to
dataset - dataadapter stuff. more generally .NET platform is not powerfull
enough to build an "true domain model" (kinda Business Object Layer). im
waiting for object spaces untill 2007 :/ BTW ive heard Anders Hejlsberg is
working on Object Spaces? is it true?
if we want to use stored procedures for insert and update as well? how about
our "select" stored procedure includes some logic (case when or if
statements based on some parameter etc.) ? how about if we dont want always
get same column set? do we have to generate, for each set of columns,
another dataset? i think VS.NET is not powerful enough when it cames to
dataset - dataadapter stuff. more generally .NET platform is not powerfull
enough to build an "true domain model" (kinda Business Object Layer). im
waiting for object spaces untill 2007 :/ BTW ive heard Anders Hejlsberg is
working on Object Spaces? is it true?
N
Nicholas Paldino [.NET/C# MVP]
See inline:
how about if we want to use stored procedures for insert and update as well?
It will support that as well. VS.NET doesn't care what you want to do
with your stored procedure, they are all accessed the same way (pass
parameters, execute, get results). They are all treated the same way.
how about our "select" stored procedure includes some logic (case when or if
statements based on some pparameter etc.)?
See above. VS.NET 2005 will generate the wrapper, along with methods to
call the procedure (it will create a parameter list which mimics the stored
procedure parameter list).
how about if we dont want always get same column set? do we have to
generate, for each set of columns, another dataset?
You would have to tweak the code for this. However, this is a result of
bad design on the part of the stored procedure, not a limitation in VS.NET
2005. It's like returning object from a method, you could do it, and return
any type you like, but what use is it? It's better to have well-defined
result sets.
i think VS.NET is not powerful enough when it cames to dataset - dataadapter
stuff. more generally .NET platform is not powerfull enough to build an
"true domain model" (kinda Business Object Layer). im waiting for object
spaces untill 2007 :/
I think this is debatable. Needless to say, I strongly disagree with
business objects in a sense (espectially when there is a need for
transactions, given their nature).
BTW ive heard Anders Hejlsberg is working on Object Spaces? is it true?
No, he is not. For all intents and purposes, ObjectSpaces is dead.
Now, it is going to be LINQ, or more specifcally, DLINQ, for working with
database servers. It's in the preliminary stages, so it's hard to say how
it will work, and won't be out for a while.
how about if we want to use stored procedures for insert and update as well?
It will support that as well. VS.NET doesn't care what you want to do
with your stored procedure, they are all accessed the same way (pass
parameters, execute, get results). They are all treated the same way.
how about our "select" stored procedure includes some logic (case when or if
statements based on some pparameter etc.)?
See above. VS.NET 2005 will generate the wrapper, along with methods to
call the procedure (it will create a parameter list which mimics the stored
procedure parameter list).
how about if we dont want always get same column set? do we have to
generate, for each set of columns, another dataset?
You would have to tweak the code for this. However, this is a result of
bad design on the part of the stored procedure, not a limitation in VS.NET
2005. It's like returning object from a method, you could do it, and return
any type you like, but what use is it? It's better to have well-defined
result sets.
i think VS.NET is not powerful enough when it cames to dataset - dataadapter
stuff. more generally .NET platform is not powerfull enough to build an
"true domain model" (kinda Business Object Layer). im waiting for object
spaces untill 2007 :/
I think this is debatable. Needless to say, I strongly disagree with
business objects in a sense (espectially when there is a need for
transactions, given their nature).
BTW ive heard Anders Hejlsberg is working on Object Spaces? is it true?
No, he is not. For all intents and purposes, ObjectSpaces is dead.
Now, it is going to be LINQ, or more specifcally, DLINQ, for working with
database servers. It's in the preliminary stages, so it's hard to say how
it will work, and won't be out for a while.
T
The Crow
sorry i was talking about typed dataset's that is generated by visual
studio, when you drag and drop stored procedure.
studio, when you drag and drop stored procedure.
N
Nicholas Paldino [.NET/C# MVP]
As was I.
T
The Crow
i think u r talking about stored procedure wrapper comimg with vs2005.
It will support that as well. VS.NET doesn't care what you want to do
with your stored procedure, they are all accessed the same way (pass
parameters, execute, get results). They are all treated the same way.
please tell me the answers applied to VS2003. how to specify typed dataset
to use custom stored procedures and take a custom action(espesially based on
return value)?on custom situations how to call paramtered version of stored
procedure and send parameter ? i wish data manuplation and business logic
were just as easy as VS thinks. its not just filling and updating
datasource. and one more question, how about retrieving particular record(s)
with only particular detail records, and travelling between records? dataset
tastes me as an huge datasource, database's on memory implementation, so i
dont like to use dataset when working with particular records. for example,
when i fill a customer and only orders of customer given in a particular
date, having 1 dataset, 2 datatables in it and using customer.Orders[0]
notation is awfull i think. but in case of datasource is completely in
memory, its perfect to be able write something like order.Parent.. hopefully
i told my thoughts clearly.
It will support that as well. VS.NET doesn't care what you want to do
with your stored procedure, they are all accessed the same way (pass
parameters, execute, get results). They are all treated the same way.
please tell me the answers applied to VS2003. how to specify typed dataset
to use custom stored procedures and take a custom action(espesially based on
return value)?on custom situations how to call paramtered version of stored
procedure and send parameter ? i wish data manuplation and business logic
were just as easy as VS thinks. its not just filling and updating
datasource. and one more question, how about retrieving particular record(s)
with only particular detail records, and travelling between records? dataset
tastes me as an huge datasource, database's on memory implementation, so i
dont like to use dataset when working with particular records. for example,
when i fill a customer and only orders of customer given in a particular
date, having 1 dataset, 2 datatables in it and using customer.Orders[0]
notation is awfull i think. but in case of datasource is completely in
memory, its perfect to be able write something like order.Parent.. hopefully
i told my thoughts clearly.
T
The Crow
i meant "in an object oriented fashion" in my questions.
Ask a Question
Want to reply to this thread or ask your own question?
You'll need to choose a username for the site, which only take a couple of moments. After that, you can post your question and our members will help you out.