browse by tag: database in language
sort by
Creating Multiple Choice Exam Application Part I
in .NET added by admin, on 7/1/2008 database intermediate xml
This is the first part of a multi-part series. In this series we will cover the scenario of creating a multiple choice exam for the user. In the first part I will cover the design of the application. This will include unit tests, domain objects and NHibernate mapping files
comment save report
Creating a Data Access Layer
in .NET added by admin, on 14/12/2007 beginner tutorials data access layer database
In this tutorial we'll start from the very beginning and create the Data Access Layer (DAL), using typed DataSets, to access the information in a database.
comment save report
Ruby on Rails on Oracle: A Simple Tutorial
in Ruby added by admin, on 29/11/2007 database intermediate oracle ruby on rails
This article is not intended to be a booster piece for Rails nor is it an expose. It's simply an introduction to the technology. It contains both praise and criticism. At times the criticism might appear a bit heavy handed (especially to Rails enthusiasts), but don't be fooled. Using any Web application framework is going to be tricky, whether it's J2EE, ASP.NET, or PHP. In the long run, you can be a lot more productive with Rails than you can be with many other Web application development platforms, but it takes time to learn the ropes.
comment save report
Object-relation mapping put on rails
in Ruby added by admin, on 25/10/2007 active record beginner tutorials database reference ruby on rails
Active Record connects business objects and database tables to create a persistable domain model where logic and data are presented in one wrapping. It's an implementation of the object-relational mapping (ORM) pattern by the same name as described by Martin Fowler
comment save report
An Introduction to AJAX and Atlas with ASP.NET 2.0
in .NET added by admin, on 25/10/2007 ajax database intermediate
Traditionally, web applications have left a lot to be desired from a user experience standpoint, due primarily to the "request/response" lifecycle. Any interaction with a page typically requires a postback to the web server (a "request"), which then performs any server-side tasks needed and returns the updated page's markup (the "response"). Outside of intranet-based applications, such behavior adds a bit of a lag when interacting with a page. One approach to improving the end user's experience is to use AJAX. AJAX-enabled pages provide a slick, responsive user experience, making web-based applications function more like desktop-based ones.
comment save report