| Groups | Blog | Home |
dotnet ado.net : Strongly Typed Dataset should be in DataAccess Layer or Business Layer
strongly typed dataset we can generate all of the fields from tables in database and also has tableadapter that allow us to write down sql command in or directly link to table. We still can write the code in dataset partial class for validating data as well. As far as I understand strongly typed dataset is in both of Business layer and data access layer, isn't it? Because validation rules code and all datatable's fields should be in business layer and tableadapter which is tied to sql command and connection string should be in data access layer. Is this right or wrong? Any suggestion or does it have any best way if I want to use strongly typed dataset in my project.
Kittipong,
It depends on the project, however I do it for larger project as you told. However it is even possible to set your simple checkings in the field descriptors in the SQL server, that is then exposed in the strongly typed dataset which makes then an easy early check even automatically in the UI possible, as it is about binded controls. The cavatat of that is that it needs forever maintenance at the SQL server side. I agree with you that this all does not make everything clear. Cor <kittipong.kiatcheeranun@gmail.com> schreef in bericht news:1188349576.118470.74270@x35g2000prf.googlegroups.com... [quoted text, click to view] >I am not exactly sure that my understanding is right or wrong. In
> strongly typed dataset we can generate all of the fields from tables > in database and also has tableadapter that allow us to write down sql > command in or directly link to table. We still can write the code in > dataset partial class for validating data as well. > As far as I understand strongly typed dataset is in both of Business > layer and data access layer, isn't it? Because validation rules code > and all datatable's fields should be in business layer and > tableadapter which is tied to sql command and connection string should > be in data access layer. Is this right or wrong? Any suggestion or > does it have any best way if I want to use strongly typed dataset in > my project. >
On Aug 29, 1:30 pm, "Cor Ligthert[MVP]" <notmyfirstn...@planet.nl>
[quoted text, click to view] wrote: > Kittipong, > > It depends on the project, however I do it for larger project as you told. > However it is even possible to set your simple checkings in the field > descriptors in the SQL server, that is then exposed in the strongly typed > dataset which makes then an easy early check even automatically in the UI > possible, as it is about binded controls. > > The cavatat of that is that it needs forever maintenance at the SQL server > side. I agree with you that this all does not make everything clear. > > Cor > > <kittipong.kiatcheera...@gmail.com> schreef in berichtnews:1188349576.118470.74270@x35g2000prf.googlegroups.com... > > >I am not exactly sure that my understanding is right or wrong. In > > strongly typed dataset we can generate all of the fields from tables > > in database and also has tableadapter that allow us to write down sql > > command in or directly link to table. We still can write the code in > > dataset partial class for validating data as well. > > As far as I understand strongly typed dataset is in both of Business > > layer and data access layer, isn't it? Because validation rules code > > and all datatable's fields should be in business layer and > > tableadapter which is tied to sql command and connection string should > > be in data access layer. Is this right or wrong? Any suggestion or > > does it have any best way if I want to use strongly typed dataset in > > my project. Thanks for the answer Cor. I still have a thing that confusing me. For DataAccess Layer should it know about StronglyTyped dataset? For example, I have a insert product method in my Data Access Layer as the first method below: 1. First Method: public static int Insert(string productName, int categoryID, decimal unitPrice) { Database myDatabase = DatabaseFactory.CreateDatabase(); DBCommandWrapper myCommand = myDatabase.GetStoredProcCommandWrapper("entlibProductsInsert"); myCommand.AddInParameter("@ProductName", DbType.String, productName); myCommand.AddInParameter("@CategoryID", DbType.Int32, categoryID); myCommand.AddInParameter("@UnitPrice", DbType.Currency, unitPrice); // Execute the query and return the new identity value return Convert.ToInt32(myDatabase.ExecuteScalar(myCommand)); } 2. Second Method: public static int Insert(ProductDataSet productDataSet) { Database myDatabase = DatabaseFactory.CreateDatabase(); DBCommandWrapper myCommand = myDatabase.GetStoredProcCommandWrapper("entlibProductsInsert"); myCommand.AddInParameter("@ProductName", DbType.String, productName); myCommand.AddInParameter("@CategoryID", DbType.Int32, categoryID); myCommand.AddInParameter("@UnitPrice", DbType.Currency, unitPrice); // Execute the query and return the new identity value return Convert.ToInt32(myDatabase.ExecuteScalar(myCommand)); } In my case If I want to change parameter to be strongly typed dataset as shown in my second method, do I need to move my strongly typed dataset to DataAccess Layer or it should be separated in another layer? What I am thinking I may put my strongly typed dataset in another layer called Business Entity because the strongly typed needs to share with DataAccess, Business and UI (binding control) as well. I am not sure it's right or wrong and I don't really know how other people do it, any suggestion will be really appreciated. Regards, Kittipong
On Aug 30, 3:23 am, "Cor Ligthert[MVP]" <notmyfirstn...@planet.nl>
[quoted text, click to view] wrote: > kittipong, > > Be aware that you never move an object between layers, you only give the > reference by value, therefore I like it very much to give the object that it > is about. In your case the strongly typed dataset. > > Cor > > <kittipong.kiatcheera...@gmail.com> schreef in berichtnews:1188373595.643692.58390@x35g2000prf.googlegroups.com... > > > On Aug 29, 1:30 pm, "Cor Ligthert[MVP]" <notmyfirstn...@planet.nl> > > wrote: > >> Kittipong, > > >> It depends on the project, however I do it for larger project as you > >> told. > >> However it is even possible to set your simple checkings in the field > >> descriptors in the SQL server, that is then exposed in the strongly typed > >> dataset which makes then an easy early check even automatically in the UI > >> possible, as it is about binded controls. > > >> The cavatat of that is that it needs forever maintenance at the SQL > >> server > >> side. I agree with you that this all does not make everything clear. > > >> Cor > > >> <kittipong.kiatcheera...@gmail.com> schreef in > >> berichtnews:1188349576.118470.74270@x35g2000prf.googlegroups.com... > > >> >I am not exactly sure that my understanding is right or wrong. In > >> > strongly typed dataset we can generate all of the fields from tables > >> > in database and also has tableadapter that allow us to write down sql > >> > command in or directly link to table. We still can write the code in > >> > dataset partial class for validating data as well. > >> > As far as I understand strongly typed dataset is in both of Business > >> > layer and data access layer, isn't it? Because validation rules code > >> > and all datatable's fields should be in business layer and > >> > tableadapter which is tied to sql command and connection string should > >> > be in data access layer. Is this right or wrong? Any suggestion or > >> > does it have any best way if I want to use strongly typed dataset in > >> > my project. > > > Thanks for the answer Cor. I still have a thing that confusing me. For > > DataAccess Layer should it know about StronglyTyped dataset? For > > example, I have a insert product method in my Data Access Layer as the > > first method below: > > > 1. First Method: > > public static int Insert(string productName, int categoryID, decimal > > unitPrice) > > { > > Database myDatabase = DatabaseFactory.CreateDatabase(); > > DBCommandWrapper myCommand = > > myDatabase.GetStoredProcCommandWrapper("entlibProductsInsert"); > > > myCommand.AddInParameter("@ProductName", DbType.String, > > productName); > > myCommand.AddInParameter("@CategoryID", DbType.Int32, categoryID); > > myCommand.AddInParameter("@UnitPrice", DbType.Currency, unitPrice); > > > // Execute the query and return the new identity value > > return Convert.ToInt32(myDatabase.ExecuteScalar(myCommand)); > > } > > > 2. Second Method: > > public static int Insert(ProductDataSet productDataSet) > > { > > Database myDatabase = DatabaseFactory.CreateDatabase(); > > DBCommandWrapper myCommand = > > myDatabase.GetStoredProcCommandWrapper("entlibProductsInsert"); > > > myCommand.AddInParameter("@ProductName", DbType.String, > > productName); > > myCommand.AddInParameter("@CategoryID", DbType.Int32, categoryID); > > myCommand.AddInParameter("@UnitPrice", DbType.Currency, unitPrice); > > > // Execute the query and return the new identity value > > return Convert.ToInt32(myDatabase.ExecuteScalar(myCommand)); > > } > > > In my case If I want to change parameter to be strongly typed dataset > > as shown in my second method, do I need to move my strongly typed > > dataset to DataAccess Layer or it should be separated in another > > layer? What I am thinking I may put my strongly typed dataset in > > another layer called Business Entity because the strongly typed needs > > to share with DataAccess, Business and UI (binding control) as well. > > > I am not sure it's right or wrong and I don't really know how other > > people do it, any suggestion will be really appreciated. > > > Regards, > > Kittipong Thank for your answer cor. It helped me out a lot :). And I also skim read through Patterns of Enterprise Applicaiton Architecture (Martin Fowler) and MS Designing Data Tier Components and Passing Data Through Tiers. These two books are great and answer a heap of my questions as well. Regards, Kittipong
kittipong,
Be aware that you never move an object between layers, you only give the reference by value, therefore I like it very much to give the object that it is about. In your case the strongly typed dataset. Cor <kittipong.kiatcheeranun@gmail.com> schreef in bericht news:1188373595.643692.58390@x35g2000prf.googlegroups.com... [quoted text, click to view] > On Aug 29, 1:30 pm, "Cor Ligthert[MVP]" <notmyfirstn...@planet.nl>
> wrote: >> Kittipong, >> >> It depends on the project, however I do it for larger project as you >> told. >> However it is even possible to set your simple checkings in the field >> descriptors in the SQL server, that is then exposed in the strongly typed >> dataset which makes then an easy early check even automatically in the UI >> possible, as it is about binded controls. >> >> The cavatat of that is that it needs forever maintenance at the SQL >> server >> side. I agree with you that this all does not make everything clear. >> >> Cor >> >> <kittipong.kiatcheera...@gmail.com> schreef in >> berichtnews:1188349576.118470.74270@x35g2000prf.googlegroups.com... >> >> >I am not exactly sure that my understanding is right or wrong. In >> > strongly typed dataset we can generate all of the fields from tables >> > in database and also has tableadapter that allow us to write down sql >> > command in or directly link to table. We still can write the code in >> > dataset partial class for validating data as well. >> > As far as I understand strongly typed dataset is in both of Business >> > layer and data access layer, isn't it? Because validation rules code >> > and all datatable's fields should be in business layer and >> > tableadapter which is tied to sql command and connection string should >> > be in data access layer. Is this right or wrong? Any suggestion or >> > does it have any best way if I want to use strongly typed dataset in >> > my project. > > Thanks for the answer Cor. I still have a thing that confusing me. For > DataAccess Layer should it know about StronglyTyped dataset? For > example, I have a insert product method in my Data Access Layer as the > first method below: > > 1. First Method: > public static int Insert(string productName, int categoryID, decimal > unitPrice) > { > Database myDatabase = DatabaseFactory.CreateDatabase(); > DBCommandWrapper myCommand = > myDatabase.GetStoredProcCommandWrapper("entlibProductsInsert"); > > myCommand.AddInParameter("@ProductName", DbType.String, > productName); > myCommand.AddInParameter("@CategoryID", DbType.Int32, categoryID); > myCommand.AddInParameter("@UnitPrice", DbType.Currency, unitPrice); > > // Execute the query and return the new identity value > return Convert.ToInt32(myDatabase.ExecuteScalar(myCommand)); > } > > 2. Second Method: > public static int Insert(ProductDataSet productDataSet) > { > Database myDatabase = DatabaseFactory.CreateDatabase(); > DBCommandWrapper myCommand = > myDatabase.GetStoredProcCommandWrapper("entlibProductsInsert"); > > myCommand.AddInParameter("@ProductName", DbType.String, > productName); > myCommand.AddInParameter("@CategoryID", DbType.Int32, categoryID); > myCommand.AddInParameter("@UnitPrice", DbType.Currency, unitPrice); > > // Execute the query and return the new identity value > return Convert.ToInt32(myDatabase.ExecuteScalar(myCommand)); > } > > In my case If I want to change parameter to be strongly typed dataset > as shown in my second method, do I need to move my strongly typed > dataset to DataAccess Layer or it should be separated in another > layer? What I am thinking I may put my strongly typed dataset in > another layer called Business Entity because the strongly typed needs > to share with DataAccess, Business and UI (binding control) as well. > > I am not sure it's right or wrong and I don't really know how other > people do it, any suggestion will be really appreciated. > > Regards, > Kittipong > >
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 |