ORM Frameworks – What is an Object-Relational Mapping Framework

ORM Frameworks – What is an Object-Relational Mapping Framework

In the following article we’ll learn many things regarding ORM frameworks(Object relational mapping):

What they’re.
What they are doing.
When and why to use them.
And finally, what ORM choices PHP’ers have.
Let’s begin …

If you’re operating with PHP, you’ll definitely end up operating with relative databases (like MySQL) sooner or later. Anyone UN agency has ever designed a fairly advanced internet application is aware of, that the SQL will get very bushy now and then – particularly after you contemplate all the information filtering that you simply got to deal with!

ORM frameworks to the rescue!

ORM is yet one more nerd-acronym, it’s short for Object relative Mapping. during a shell, associate ORM framework is written in associate object headed language (like PHP, Java, C# etc…) and it’s designed to just about wrap around a electronic database. If you inspect the name (ORM), it primarily interprets into: mapping objects to relative tables.

There square measure many alternative competitory ORM frameworks out there, as a result of several nerds have their own concepts on a way to best do things – nothing new here! however you recognize what, a number of these nerds square measure right … not all ORM frameworks square measure created equal.

however what will associate ORM framework do?

Basically, the ORM framework/software generates objects (as in OOP) that just about map (like the map of a city) the tables during a information. Then you as a coder, would use these objects to act with the information. that the main plan, is to do and defend the coder from having to write down optimized SQL code – the ORM generated objects beware of that for you. thus let’s take a glance at a straightforward example:

Say for example you had a information with 2 tables:

With a trifle little bit of configuration on your half, the ORM framework would then produce corresponding objects (say, clients_object and products_object) that may handle all the information interaction. thus let’s say you wish to feature a replacement shopper to the information, you’d simply got to use the ORM’s shoppers_object to feature the new client.

For example, it may be as easy as occupation the object’s save() method:

client = new consumers_object("Stefan","Mischook");

The higher than after all, is simply pseudo code, primarily as a result of the syntax can vary from ORM framework and from language to language. however hopefully you get the overall plan of what quantity easier associate ORM framework will create things (no SQL!) .. to not mention what quantity cleaner your application’s code are going to be.

Some other benefits of victimisation ORM frameworks

1. Harmonization of knowledge varieties between the OO language (in our case, PHP) and therefore the SQL information. All relative knowledgebases use data varieties for every of the fields, for example: int, small int, blob, char etc. The factor is, that typically you have got to convert the information varieties on the fly to properly add a record to the information. an honest ORM can beware of those details for you.

2. victimisation associate ORM can produce a regular code base for your application since a lot of (if not all) of the code accustomed act with the information are going to be PHP – no SQL code to mess things up. This makes it easier to write down and correct your application, particularly if you have got a lot of programmers on employment.

3. ORM frameworks can defend your application from SQL injection attacks since the framework are going to be filtering the information for you.

4. information Abstraction; i’m a trifle hesitant to create this time as a result of in apply, over the last 10-15 years, I even have solely seen it once wherever we tend to switched databases on associate application. That said, ORM can create this a lot of easier since it takes care of writing all the SQL code, knowledge sort conversions etc …

When to use associate ORM framework?

From my personal expertise, associate ORM framework becomes a lot of helpful because the size and complexness of the project will increase. If you simply have a straightforward information with say five tables associated 5-6 queries … putting in an ORM framework is also overkill. i’d get thinking about the utilization of ORM when:

You have three or a lot of programmers on an internet application.
Your information contains 10+ tables.
You have say 10+ queries to create.
ORM frameworks can’t jazz all

If you think that that victimisation associate ORM framework can enable you to forget SQL and ne’er got to recollect, re-evaluate. Once you jump into the ORM world, you’ll realize that regarding 80-90% of your queries will be handled by the ORM generated objects. it’s inevitable that at some purpose you’ll ought to sink and use some SQL or some SQL like source language.

In fact, ORM frameworks typically have their own *QL source language that appears lots like SQL. Doctrine, a well-liked PHP based mostly ORM framework has DQL (Doctrine question Language) and therefore the extremely popular Hibernate (used within the Java and .Net world) has HQL. Going even any, Hybernate permits you to write down straight SQL if want be.

Despite the necessity for a SQL like language in ORM frameworks, they’ll still be terribly valuable tools in your PHP work.

ORM Frameworks for PHP programmers

Not associate thorough list, however here square measure many ORM frameworks to consider:


Part of the cool Avestan Framework zend db
CakePHP has ORM designed into it.
RedBean ORM while not configuration!

Leave a Comment

Your email address will not be published. Required fields are marked *

  +  23  =  32

We're accepting well-written guest posts and this is a great opportunity to collaborate : Contact US