Skip to main content

Prototypes in Javascript

Almost all the Javascript objects are instances of Object. Every object inherits properties and methods from Object.prototype. The developer has the flexibility to add new properties and methods to objects. The following example shows how to use Prototypes in Javascript.
 function Person(name,salary,age){  
   this.name = name;  
   this.salary = salary;  
   this.age = age;  
   this.DisplayDetails = function(){  
     var name = "Details of Employee\n";  
     name+="=============================+\n"  
     name+="Name:"+this.name+"\n";  
     name+="Salary:"+this.salary+"\n";  
     name+="Age:"+this.age+"\n";  
     return name;  
   }  
 }  
 var person1 = new Person("New Employee",25000,27);  
 console.log("Name is:"+person1.name);
 console.log(person1.DisplayDetails());
In the above example we created a new Prototype named "Person" which has the following properties:
i. name
ii. salary
iii. age
It has one function / method that has been declared named "DisplayDetails()". Please note that we use "this" keyword to set up every property and method. In simple terms, "this" means the current object on which actions are called.
The above code will display "New Employee" as the output. As we are calling the method of the prototype, it will also return the following output:
Details of Employee
=============================
Name:New Employee
Salary:25000
Age:27
Also, we can add properties and methods dynamically to the objects after they are created. For e.g. in case we want to add a property to the Prototype dynamically, the following code will work:
 Person.prototype.height="160 cm";  
 console.log(person1.height);  
In case we want to add a method dynamically:
 Person.prototype.DisplayHeight = function(){  
   console.log("The height of the person is :"+this.height);  
 }  
 person1.DisplayHeight();  
Happy Coding! | dhandrohit@gmail.com

Comments

Popular posts from this blog

Connecting Nodejs to SQL Server with Knex ORM - Part 1

Normally we connect Nodejs to the databases like SQLite, MongoDB, Postgres etc . In this multiple part post, I am going to show you, how we can connect Nodejs with Microsoft's SQL Server using Knex and run CRUD operations. 1. Installation of required packages In order to connect Nodejs to SQL Server with Knex, we will need following node packages installation: i. npm install knex ii. npm install mssql Once the packages are installed, we can write the following code to connect: //Code to KNEX connection settings. var knex = require('knex')({ client: 'mssql', connection: { user: 'sa', password: 'pwd', server: 'localhost', database: 'Test' } }); //Code to query the Table DEPT knex.select("*").from("dept") .then(function (depts){ depts.forEach((dept)=>{ //use of Arrow Function console.log({...dept}); }); }).catch(function(err) { ...

SQLServer Error: 15404, Could not obtain information about Windows NT group/user Error code 0x5. [SQLSTATE 42000] (ConnIsLoginSysAdmin)

If we encounter this error "SQLServer Error: 15404, Could not obtain information about Windows NT group/user Error code 0x5. [SQLSTATE 42000] (ConnIsLoginSysAdmin)" in SQL Server in which the job fails because of the user account related problem, then we need to take the following steps to make it work: a. Go to SQL Server Agent. b. Then select the job which is giving error and not running successfully. c. Then choose properties and in the General Tab, change the owner to "SA" or any account that has the administrative privileges. The problem will be resolved.

MAX pool size reached in ASP.NET

If you are handling large databases and big application(s) that are running on servers in a cluster, then probably this error might have occurred. In an ASP.NET app, we can use connection pooling that helps to share the connection between multiple request(s) rather than creating more connections. The settings relating to connection pool are defined in web.config file. Max pool size reached error in ASP.NET occurs, when the number of connections go beyond the maximum defined limit in Web.config file. Following are the various settings of the Connection Pooling: Name Default Description Connection Lifetime 0 When a connection is returned to the pool, its creation time is compared with the current time, and the connection is destroyed if that time span (in seconds) exceeds the value specified by  Connection Lifetime . This is useful in clustered configurations to force load balancing between a runnin...