Skip to main content

Connecting Nodejs to SQL Server with Knex ORM - Part III

In this final multi part post, I am going to show how to do "Delete" and "Update" records through Knex.
1. Using DELETE
Delete is the command to delete record from the table. We should run delete query with where  condition which is normally based on Primary key.
 var knex = require('knex')({  
  client: 'mssql',  
   connection: {  
    user: 'sa',  
    password: '123',  
    server: 'localhost',  
    database: 'lovely'  
   }  
 });  
 knex("dept").where("deptno","50").del()  
 .then(function (count) {  
   console.log(count);  
 })  
 .finally(function () {  
   knex.destroy();  
 });  
In the above delete command, we are trying to delete a row which has "Deptno" = 50. In case the command is successful, it will return a Promise.resolve that has been captured in .then function.
It will also return the count of records that were deleted.
2. Using UPDATE
Update command can be used to change the column values for an existing record or records.
 var knex = require('knex')({  
  client: 'mssql',  
   connection: {  
    user: 'sa',  
    password: '123',  
    server: 'localhost',  
    database: 'lovely'  
   }  
 });  
 knex('dept').where("deptno","40")  
 .update({  
  dname: 'TEST DEPARTMENT'  
 })  
 .then((count)=>{  
  console.log("record updated"+count);  
 });  
In the above example we are trying to update the name of the an existing Deptno = 40 with the new name "TEST DEPARTMENT". It also returns a Promise. In case it ran successfully, we will get the Promise.resolve that can be used with .then
Happy Coding!1 | 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...