Binary Spectrum Geeks at work

 -      Tauseef.M
 

Well guys, in my previous articles I have given a preliminary description about the Stored Procedure and also had given a word that I will be dealing with it in more detail in my upcoming articles. As the saying goes “Once a word has been allowed to escape, it cannot be recalled”, and so I am back here with advanced stored procedure concepts.

Insertion using Stored Procedure’s Input Parameters
 

Let’s get on by creating a table name tblEmployee with the following fields as below:
 

 

                                    Fig (a)

Now let’s create a Stored Procedure for insertion. Open a new Query window and type the below stored procedure.

 

Stored procedure named usp_insert gets created into database.
 

Execute Stored Procedure??
Yeah!! The below syntax is used for executing the above created stored procedure. 

Here EmpId Column inside the table is a primary key with identity being set to [1].

Updating table - Stored Procedure using Input Parameters

Let’s have a glance over the fig (a) above. Now we are going to use the same table for creating the stored procedure for updating the table.

Portray the same as below in a new Query Window.

Stored procedure named usp_Update gets created into database.

Execute Stored Procedure??
Before executing let us see the records inside the table tblEmployee.

 

 

 

Deleting Records - Stored Procedure using Input Parameters

The last step in any CRUD operation is deleting the records in the table.
Let’s create a stored procedure named usp_Delete

 

Execute Stored Procedure??
 

Stored Procedure using Output variables will be explained in my upcoming articles!!

(The author, Tauseef.M, is a Software Engineer at Binary Spectrum).

 

 

Posted by Ratika at 11:38 PM | Permalink | Comments (0) | TrackBacks (0)

- Jayanth Raj

We can create an ongoing task in MS Project by creating a “Hammock Task”. Hammock task duration changes automatically when the project finish date is changed.

Steps for creating a Hammock Task:
1.     Click on Project start date cell, the start date cell will be highlighted.
2.     On the edit menu, click copy (cell)
3.     Click on the ‘ongoing task’ start date, the start date cell will be highlighted.
4.     On edit menu, click ‘Paste Special’ and click ‘Paste Link’.
5.     Click on Project end date cell, the end date cell will be highlighted.
6.     On the edit menu, click copy (cell)
7.     Click on the ‘ongoing task’ end date, the end date cell will be highlighted.
8.     On edit menu, click ‘Paste Special’ and click ‘Paste Link’.

Posted by Ratika at 08:52 PM | Permalink | Comments (1) | TrackBacks (0)

- Anjana. M

I had to upload pin codes in excel to database. After procrastinating on net for considerable time, I decided to find a quick solution... :) Though I am aware of available excel api’s, I dint want to spend time in reading api docs for breaking a thin twig. This method can be followed if you want to export a single column from excel to a table.  

- Jagadish. M

The interest of developer will always be towards learning new technologies. It’s secondary that whether in real-time you are going to use it in or not. One of the most popular and fastest growing technologies that I came across is Ruby on Rails (RoR).

Ruby on Rails was developed by David Heinemeier Hansson from his work on BaseCamp; a project management tool, which offers to-do lists, wiki-style web-based text documents, milestone management, file sharing, time tracking, and a messaging system.

Like many web frameworks, Rails uses the Model View Controller (MVC) architecture to organize applications.

• Each and Everything is Object: Even numbers in ruby are treated as object. Looking at the example, what output you can expect from this?

8.times {print “Guess what”} its prints Guess what 8 times.

• Powerful blocks: Code blocks can be passed as parameter to method. Following example prints out all the elements in an array

  jArray.each{|element| print element}

• Return is optional in Methods: In ruby return statement is optional in methods. The value of the last expression becomes the return value of that method. For example: 

  def testReturn n = 2 * 3 en

• Parallel Assignment in Ruby: We can change the multiple variables in one assignment statement. Swapping of two variables is the good example for it.   n1 = 1

  n2 = 3

   n1, n2 = n2,n1

• Everything in Ruby is open: Including the built-in classes, in ruby, additional methods can be added to the classes even at run-time also. For example: FixNum is the build in Data Type for all to which I added the method called old.                         

class Fixnum

def old return self-1

end

end

8.old  # prints 7

(The author, Jagadish.M, is a Software Engineer at Binary Spectrum).

Posted by Ratika at 09:32 PM | Permalink | Comments (0) | TrackBacks (0)

-Jagadish.M

- Anjana.M 

We often see programmers jump to their seats and start coding as soon as they just hear any requirement. They may be able to complete the task, but may actually be lost in fixing the logical errors for a long time.

I have followed this approach that I am stating below, and yes, it worked well. I also believe that this is a stress free approach towards developing and implementing the requirement.

This is just doing object modeling in a well planned way. This surely can be achieved with UML tools. But paper work at times does prove to be quicker.

Let me know your thoughts on it and looking forward to know your development approaches as well.

Here are the 10 steps for a planned approach:

Step-1: Get requirement

Step-2: Don’t start development as soon as you get the requirement

Step-3: Lets follow the divide and rule approach - Divide the requirement into subtasks! We may have a list of subtasks

Step-4: Rule Them -Recognize the dependent task

Step-5: Create a class with requirement's name

Step-6: Make the subtasks as methods in the class

Step-7: Recognize the Inputs and Outputs for each method

Step-8: Build the DBQUERY

Step-9: Include the logic

Step-10: Unit test with SOP for each method in the class.

(The author, Anjana.M, is a Software Engineer at Binary Spectrum) 

Posted by Ratika at 07:27 PM | Permalink | Comments (3) | TrackBacks (0)