CSC/ECE 517 Fall 2014/ch1a 8 os: Difference between revisions
Jump to navigation
Jump to search
| Line 7: | Line 7: | ||
== Features == | == Features == | ||
===Object- Relational Mapper=== | === Object- Relational Mapper === | ||
Django has its own object relational mapper which eases database access. It facilitates writing of model classes directly in python. Model classes can be defined by sub-classing [https://docs.djangoproject.com/en/1.7/ref/models/instances/#django.db.models.Model django.db.models.Model]. Each attribute of this class corresponds to a database field | Django has its own object relational mapper which eases database access. It facilitates writing of model classes directly in python. Model classes can be defined by sub-classing [https://docs.djangoproject.com/en/1.7/ref/models/instances/#django.db.models.Model django.db.models.Model]. Each attribute of this class corresponds to a database field. This makes it possible to use an automatically generated database access API. | ||
== Comparison with other Web Frameworks == | == Comparison with other Web Frameworks == | ||
== References == | == References == | ||
Revision as of 16:15, 14 September 2014
Django
Background
Architecture
Features
Object- Relational Mapper
Django has its own object relational mapper which eases database access. It facilitates writing of model classes directly in python. Model classes can be defined by sub-classing django.db.models.Model. Each attribute of this class corresponds to a database field. This makes it possible to use an automatically generated database access API.