Architecture :: Binding Of Gridview With Database Versus XML Layer / Database
Apr 13, 2010
I am having serious performances issues with gridview + tabs. Its very slow.. I was thinking to create a XML based logical layer between my database and UI.
1) Will it be useful if i use webservice to get data from database to poppulate gridview?
I have several web sequential pages which will modify a record and its child records in the database, called a "project". Such a project is currently passed between pages using its database ID in the URL parameters.
A project has some information specific to itself, and also consists of one or more Tasks, which each have information specific to itself.
Is it faster (alternatively, more maintainable or more easily understood) to hit the database each time I need to query the same project (and its tasks), or should I query the database once (either once for each page or once for all pages and save to Session) and check the saved object rather than the database?
I am new to this .NET what is the difference between N-Tier and 3- Tier Architecture. If they are same. How to pass the values from presentation layer to business logic layer.
For Example
I have 10 controls in presentation layer. I passing values to these controls. How the architecture works.
I am building a web site following the tutorials on asp.net. I am using dataset as data access lay, and writing classes to access the dataset. But the example is just basic ideas, how do I retrieve individual table column value in the business layer?For example, if I have a table called Product, I only want to find out what is the product name by product id. I did this in my ProductBLL:
public ProductBLL { public int GetProductName(string productId) { ProductDataSet.ProductDataTable prodData = Adapter.GetProductById(productId); [code]...
Is there a better way, or am I doing this correctly? Can anybody give me a reference to a more complicated business logic model?
After i retrieved a set of datatable from database, i need to edit the rows value before binding to the gridview. for example, a set of datatable is retrived from database.
i would like to change "james@hotmail.com" to "james" then bind it to gridview. Every rows of [userEmail] will be separated with the mail extension (@hotmail.com) ... how should i do..?
I'm trying to bind a nullable bit column, which at the moment is mostly null, but I need to somehow convert the null to a 'false' on runtime because it doesn't bind to a checkbox if it's null. But, I am currently unable to change the default value and update all records accordingly - is there a way to do this in runtime?
In this website article http://aspalliance.com/1943_ASPNET_40_and_the_Entity_Framework_4__Part_4__A_3_Layered_Approach_to_the_Entit_Framework
Vince Varallo says this in his opening paragraphs. "it will introduce a pattern for developing the application as a three layered application. Notice that I didn't say three tiered application. A tier really means a logical and physical separation of the layers. A layer implies just a logical separation. For many applications that's all you need. I'm not one to advocate over-engineering a system.
I always follow the simpler, better approach as long as the developers working with you understand the pattern."
Question 1. Can some explain to me what is difference between a 3 layer application and a 3 tiered application?
Question 2. Also, can some give me a link to a simple 3 tiered tutorial for entity framework?
It's a little bit late for me to be asking this, being already 7 months into development on a large MVC2 web application project for learning languages, but I wanted to get some opinion about what the recommended path for doing database stuff is.Having had no prior experience with commercial databases, I'm pretty confused with all the different options out there.
Because the ASP.NET MVC books use Linq to SQL in the examples, it looked pretty easy, so I just went ahead and used it.My first mistake was that for the models I created abstract interfaces, and then a stand-alone concrete implementation that I could load and save using XML, so I could develop the rest of the application while building up the data model, thinking I could easily provide an alternate implementation of the model classes using Linq to SQL to back it, not using the database design page, just letting the table objects and context do the work. Not being experienced with databases, however, my models were not so easy to reimplement for the database. I'm just about to the point where it is working, albeit there are a few performance problem areas.
So, is Linq to SQL generally the way to go for database stuff? Or is there a more recommended path? I love the simple mapping Linq to Sql provides, but discovered I had to spend a lot of time trying to work around some of its quirks and missing functionality. I found that SQL itself has it's own quirks too, such as problems mixing and matching different languages in strings.
Ideally, I would want something that lets me have a data model that's like an arbitrary heterogenious object tree, using normal collections, and still be able to deal with lots of items with good performance.
I have few textboxes and I want to search the text (partial search is also required) in the database and then show the result in a telerik grid. The grid has to be hidden initially and when I click the search button it should show up and display the results.
here i have in 3-tier architecture , how to pass the data between DAL and BAL. i am using grid view to edit the data,when ever i click on the edit button all the corresponding fields should come to textboxes. i tried for delete ,it works fine bt not working to EDIT.
I'm developing a n-tier architecture... I'm confused with handling exception in the layers... Is it a good practise to add a Exception Layer to the architecture.
I'm working with an asp.net application that stores most data in a database and not session. I'm wondering of the pros and cons of each and which is the better way to go. For example, you have a pretty busy site and instead of storing user specific variables in session, there is a DB table called user data and it can store all user specific data that can be accessed from any page by querying the database. Which is the better way to go, session or database?
As I began writing web applications with asp.net I started with small projects that used a Linq-To-SQL mapper for database access to a MSSQL Server. After gaining some expierence I switched into a classic 3 tier with Graphic Layer, Business Layer, Data Layer. The only function of the Data Layer was to provide methods insert/update/delete without any logic and logic the form of selection methods.
Over the time I realized that it would be better not to provide the database classes up to the GUI (took some time unfortunately). I switched into using Business classes in the BL that are used for all operations performed by the BL and display by the GUI in the form of getting List from the BL. A great advantage is that I can provide additional properties that are not represented by the database itself. However, I did that mapping inside the BL myself with methods that mapped the corresponding BL class to the database class.
I guess thats where O/R mapper come in handy? Until now I haven't realized their purpose, but I think I just found it. I've recently tried out using the new Entity Framework with .net framework 4, but I'm only using it like the Linq-To-SQL DataContext.
Is there a way to achieve the mapping automatically? If yes, is that something the new Entity Framework provides or do I need to look for a O/R Mapper like NHibernate?
I have an ASP.NET application with existing business classes and a database schema. (which I would like to keep) Currently I am using ADO.NET for the DAL, but I would like to switch to some advanced technology there for easier data retrieval.
Is EF applicable to my situation? Can I use it without splitting up my business classes and auto code generation? Can LINQ to SQL solve my problem better?
All I want to do is map my existing classes to the existing tables and dont have to handle details of the data retrieval myself.
1. I know about collections but I dont remember the precess. I know you drag a sqldatasource control on the form(Select everything in the database ie. selct *) and then delete it. But how do I use it i code.
Example. I need to select services where country=canada from the Agencies table.
2. I know how to manually pull data from an access database using the code below. I want to know how to pull data from a sql database just like the one below.
3. explain the difference between Collections and manually pulling it like the one bellow?
I have been learning C# for the last year or so and trying to incorporate best practices along the way. Between StackOverflow and other web resources, I thought I was on the right track to properly separating my concerns, but now I am having some doubts and want to make sure I am going down the right path before I convert my entire website over to this new architecture.
The current website is old ASP VBscript and has a existing database that is pretty ugly (no foreign keys and such) so at least for the first version in .NET I do not want to use and have to learn any ORM tools at this time.
I have the following items that are in separate namespaces and setup so that the UI layer can only see the DTOs and Business layers, and the Data layer can only be seen from the Business layer. Here is a simple example:
[Code]....
Am I completely off base? Should I also have the same properties in my BLL and not pass back DTOs to my UI? what is wrong and what is right. Keep in mind I am not a expert yet.
I would like to implement interfaces to my architecture, but I am still learning how to do that.
I am implementing 3-tier architecture. I just wanted to know the role of business layer in 3-tier architecture.
I am developing application in using entity framework. So I have entity object which is accessiable in PL,BL & DL. My question is whether input assignment to entity object should be in PL OR BL.(Consider there is save method)
i build online course selection for a university now i want to make it layering and i dont know to make it 2 layer or 3 layer i mean mix business layer and database layer because i use linq so it is not require to check request data that in sql from client in business layer because linq check it autimatically to preent injection and etc.is it right?can i put my class and DB class in same place or layer?if i make it 2 layer the performance becom better?