Thursday, 2 May 2013

Difference Between Store Procedure and UDF

Stored Procedures are pre-compile objects which are compiled for first time and its compiled format is saved which executes (compiled code) whenever it is called. But Function is compiled and executed every time when it is called. 

Basic Difference

  1. Function must return a value but in Stored Procedure it is optional( Procedure can return zero or n values).
  2. Functions can have only input parameters for it whereas Procedures can have input/output parameters .
  3. Function takes one input parameter it is mandatory but Stored Procedure may take o to n input parameters..
  4. Functions can be called from Procedure whereas Procedures cannot be called from Function.

Advance Difference

  1. Procedure allows SELECT as well as DML(INSERT/UPDATE/DELETE) statement in it whereas Function allows only SELECT statement in it.
  2. Procedures can not be utilized in a SELECT statement whereas Function can be embedded in a SELECT statement.
  3. Stored Procedures cannot be used in the SQL statements anywhere in the WHERE/HAVING/SELECT section whereas Function can be.
  4. Functions that return tables can be treated as another rowset. This can be used in JOINs with other tables.
  5. Inline Function can be though of as views that take parameters and can be used in JOINs and other Rowset operations.
  6. Exception can be handled by try-catch block in a Procedure whereas try-catch block cannot be used in a Function.
  7. We can go for Transaction Management in Procedure whereas we can't go in Function.

Saturday, 23 March 2013

What is Design Patterns

What are the Design Patterns

Design Patterns are the ways to solve the problems which we getting daily while doing our task.

Design Patterns are the definite solutions for fixed problems

Design Patterns provide the ways how to solves the problems, how to handle this problem.

Object-oriented design patterns typically show relationships and interactions between classes or objects, without specifying the final application classes or objects that are involved.

Patterns that imply object-orientation or more generally mutable state, are not as applicable in functional programming languages.

Benefits of Design Patterns

1- Speed Up Development Work- Design patterns can speed up the development process by providing tested, proven development paradigms

2- Handle Major Problems - Reusing design patterns helps to prevent subtle issues that can cause major problems, and it also improves code readability for coders and architects who are familiar with the patterns.

Design Pattern Types
Creational
Structural
Behaviour

[Type - Creational]
Singleton Design Pattern















Thursday, 28 February 2013

Child Action in MVC

Child actions are action methods invoked from within a view. This lets you avoid repeating controller
logic that you want to use in several places in the application. Child actions are to actions as partial
views are to views.

Wednesday, 27 February 2013

Asp.net MVC ActionFilter

Action Filters for performing logic either before an action method is called or after its run.

Action Filters are custom attributes that provide a declarative means to add pre-action and post-action behavior to controller action methods.

ActionFilterAttribute is the base class for all the attribute filters. It provides the following methods to execute a specific logic after and before controller action’s execution:- OnActionExecuting(ActionExecutedContext filterContext)
Just before the action method is called
- OnActionExecuted(ActionExecutingContext filterContext):
After the action method is called and before the result is executed (before view render).
- OnResultExecuting(ResultExecutingContext filterContext):
Just before the result is executed (before view render).
- OnResultExecuted(ResultExecutedContext filterContext):
After the result is executed (after the view is rendered).
By overriding any of these methods into a derived class, you can execute your own filtering code.

Wednesday, 20 February 2013

Differnece Between NULL and empty in SQL

Differnece Between NULL and empty in SQL


To indicate that a value has deliberately not been specified, use the NULL keyword. NULL is the preferred way in SQL to indicate that a data value is nonexistent.
The empty string ('') is not the same thing as NULL. An empty string is a specified string. It is the shortest possible string, one that contains no characters. An empty string is represented internally by the non-display character $CHAR(0). Thus NULL and the empty string are different in nature, though in many instances the results of their use are identical. The empty string should be avoided in SQL coding. However, because many SQL operations delete trailing blank spaces, a data value that contains only whitespace characters (spaces and tabs) may be handled as an empty string. If an empty string is explicitly specified as a column default value, this value is represented by the non-display character $CHAR(0).
The SQL empty string, like all SQL strings, can also be represented with double quote characters (""), but this usage should be avoided because of potential conflict with SQL delimited identifiers.
You can convert an empty string to a NULL by using the ASCII function, as shown in the following example:
SELECT DISTINCT NULL AS NullVal,
{fn ASCII('')} AS EmpStrVal
FROM Sample.Person
 
NULL Processing
The NOT NULL data constraint requires that a field must receive a data value; specifying NULL rather than a value is not permitted. This constraint does not prevent the use of an empty string value. For further details, refer to the CREATE TABLE command.
The NULL predicate in the WHERE or HAVING clause of a SELECT statement selects NULL values; it does not select empty string values.
The IFNULL function selects NULL values, it does not select empty string values.
The COALESCE function selects the first non-NULL value from supplied data. It treats empty string values as non-NULL.
When the CONCAT function or the concatenate operator (||) concatenate a string and a NULL, the result is NULL. This is shown in the following example:
SELECT DISTINCT {fn CONCAT('fred',NULL)} AS FuncCat,
'fred'||NULL AS OpCat
FROM Sample.Person
 
The AVG, COUNT, MAX, MIN, and SUM aggregate functions ignore NULL values when performing their operations. (COUNT * counts all rows, because there cannot be a record with NULL values for all fields.) The DISTINCT keyword of the SELECT statement includes NULL in its operation; if there are NULL values for the specified field, DISTINCT returns one NULL row.
The AVG, COUNT, and MIN, aggregate functions are affected by empty string values. The MIN function considers an empty string to be the minimum value, even when there are rows that have a value of zero. The MAX and SUM aggregate functions are not affected by empty string values.
NULL Arithmetic
Any SQL arithmetic operation that has NULL as an operand returns a value of NULL. Thus, 7+NULL=NULL. This includes the binary operations addition (+), subtraction (-), multiplication (*), division (/), integer division (\), and modulo (#), and the unary sign operators plus (+) and minus (-).
An empty string specified in an arithmetic operation is treated as a value of 0 (zero).
The Length of NULL
Within SQL, the length of a NULL is undefined (it returns <null>); the length of an empty string, however, is defined as length zero, as shown in the following example:
SELECT DISTINCT CHAR_LENGTH(NULL) AS NullLen,
CHAR_LENGTH('') AS EmpStrLen
FROM Sample.Person
 
However, certain Caché extensions to standard SQL treat the length of NULL and the empty string differently. The $LENGTH function returns a length of 0 for a NULL, and a length of 1 for an empty string value. This functionality is compatible with Caché ObjectScript:
SELECT DISTINCT $LENGTH(NULL) AS NullLen,
$LENGTH('') AS EmpStrLen
FROM Sample.Person
 
Another place where the internal representation of these values is significant is in the %STRING, %SQLSTRING and %SQLUPPER functions, which append a blank space to a value. Since a NULL truly has no value, appending a blank to it creates a string of length 1. But an empty string does have a character value, so appending a blank to it creates a string of length 2. This is shown in the following example:
SELECT DISTINCT CHAR_LENGTH(%STRING(NULL)) AS NullLen,
CHAR_LENGTH(%STRING('')) AS EmpStrLen
FROM Sample.Person
 

Difference Between MVC2 and MVC3 in Asp.net