c# - Good approach to interface with database through gridview -



c# - Good approach to interface with database through gridview -

what doing create stored procedures each table select/insert/update, (if select) fill datatable rows , pass objectdatasource bound gridview. or bad technique? techniques (using bo, bl, dal) update/remove/insert records in database through gridviews?

thanks!

i info model layer encapsulates info want exposed main application. have buisiness logic layer connects model layer info access layer. info access layer of magic happens. in here, utilize system.data, system.data.sqlclient or mysql.data.mysqlclient (or whatever use--it has .net connector) namespaces phone call stored procedures , set info data model or vice versa.

here illustration of 1 have done explained, mine little different. info model expose access methods, helps organization of data. also, utilize system.data.datatable binding info gridview. works wonderfully , allows store primary key , foreign key information. manage passing schema info gridview you.

public class imagelistmodel { private imagelistbll objimagelistbll; public imagelistmodel(string connectionstring, string databaseengine, int groupid) { if(databaseengine.tolower() == "mysql") objimagelistbll = new imagelistbll(databaseengine.mysql, connectionstring); groupid = groupid; } public int groupid { get; set; } public datatable getimagelist() { homecoming objimagelistbll.getimagelist(groupid); } public bool insertimage(imagemodel objimage) { objimage.groupid = groupid; homecoming objimage.insert(); } public bool deleteimage(imagemodel objimage) { homecoming objimage.delete(); } public bool editimage(imagemodel objimage) { homecoming objimage.edit(); } } public class imagemodel { private imagebll objimagebll; public imagemodel(string connectionstring, string databaseengine) { if (databaseengine.tolower() == "mysql") objimagebll = new imagebll(databaseengine.mysql, connectionstring); } public long id { get; set; } public string titletop { get; set; } public string titlebottom { get; set; } public string imageurl { get; set; } public string extramarkup { get; set; } public string descriptionurl { get; set; } public int order { get; set; } public int userid { get; set; } public int groupid { get; set; } public bool insert() { homecoming objimagebll.insertimage(this); } public bool edit() { homecoming objimagebll.editimage(this); } public bool delete() { homecoming objimagebll.deleteimage(this); } public void changeposition() { objimagebll.changeimageposition(this); } }

as see, dal hidden. bll manages calling appropriate info access layer methods. models generic list of images appropriate info state manipulation, retrieving, , saving methods. modeling should mean in opinion.

i assume know nuts , bolts of how utilize db connector. allow me know if don't , post more code.

my model works follows:

datamodel -- exposed main application | | \/ business logic layer | pass datamodel | \/ info access layer

c# asp.net

Comments

Popular posts from this blog

iphone - Dismissing a UIAlertView -

intellij idea - Update external libraries with intelij and java -

javascript - send data from a new window to previous window in php -