Databases
StackOverflow2013
Postsdbo
PO
 

Note that there are some explanatory texts on larger screens.

plurals
  1. PO
    primarykey
    data
    text
    <p>You could have a repository:</p> <pre><code>public interface IUsersRepository { public User GetUser(int id); } </code></pre> <p>then implement it:</p> <pre><code>public class UsersRepository: IUsersRepository { private readonly string _connectionString; public UsersRepository(string connectionString) { _connectionString = connectionString; } public User GetUser(int id) { // Here you are free to do whatever data access code you like // You can invoke direct SQL queries, stored procedures, whatever using (var conn = new SqlConnection(_connectionString)) using (var cmd = conn.CreateCommand()) { conn.Open(); cmd.CommandText = "SELECT id, name FROM users WHERE id = @id"; cmd.Parameters.AddWithValue("@id", id); using (var reader = cmd.ExecuteReader()) { if (!reader.Read()) { return null; } return new User { Id = reader.GetInt32(reader.GetOrdinal("id")), Name = reader.GetString(reader.GetOrdinal("name")), } } } } } </code></pre> <p>and then your controller could use this repository:</p> <pre><code>public class UsersController: Controller { private readonly IUsersRepository _repository; public UsersController(IUsersRepository repository) { _repository = repository; } public ActionResult Index(int id) { var model = _repository.GetUser(id); return View(model); } } </code></pre> <p>This way the controller is no longer depend on the implementation of your data access layer: whether you are using plain ADO.NET, NHibernate, EF, some other ORM, calling an external web service, XML, you name it. </p> <p>Now all that's left is to configure your favorite DI framework to inject the proper implementation of the repository into the controller. If tomorrow you decide to change your data access technology, no problem, simply write a different implementation of the <code>IUsersRepository</code> interface and reconfigure your DI framework to use it. No need to touch your controller logic.</p> <p>Your MVC application is no longer tied to the way data is stored. This makes it also easier to unit test your controllers in isolation as they are no longer tightly coupled to a particular data source.</p>
    singulars
    1. This table or related slice is empty.
    1. POUsing ASP.Net MVC with Classic ADO.Net
      singulars
      1. PTQuestion
    1. PTAnswer
    1. USDarin Dimitrov
    1. USDarin Dimitrov
    plurals
    1. This table or related slice is empty.
    1. This table or related slice is empty.
    1. POUsing ASP.Net MVC with Classic ADO.Net
      singulars
      1. PTQuestion
    1. This table or related slice is empty.
    1. VO
      singulars
      1. PO
      1. This table or related slice is empty.
      1. VTUpMod
    2. VO
      singulars
      1. PO
      1. This table or related slice is empty.
      1. VTUpMod
    3. VO
      singulars
      1. PO
      1. This table or related slice is empty.
      1. VTUpMod
    1. COExcellent approach - combine that with Dapper and you can save yourself another boatload of boring, mind-boggling left-right-assignment-code ....
      singulars
      1. PO
      1. USmarc_s
    2. CO@marc_s, yes, from my experiments Dapper seems like a great light-weight ORM. I am already considering it for my next project. I am getting a little sick of NHibernate.
      singulars
      1. PO
      1. USDarin Dimitrov
    3. COvery very great explanation. I am really appreciate the way which combined Repository design pattern and pure Ado.net style. Thank you @Darin.
      singulars
      1. PO
      1. USFrank Myat Thu
 

Querying!

 
Guidance
A row detail

Detail views are divided into sections. All the information in the data section comes from columns in the selected row. The other sections display data from other, related rows.

Related data can be related in a to-one or a to-many fashion. Captions of data related in a to-many fashion link to a list view showing a filtered view of the table.

Try moving around until you find a non-empty to-many entry and click on the label to get to one. You can move back to the root by clicking on the database name in the header.

SQuiL has stopped working due to an internal error.

If you are curious you may find further information in the browser console, which is accessible through the devtools (F12).

Reload