
Search In
<-- Chapter 6: SQL IN Operator
Chapter 7
SQL NOT IN Operator
Lets see an example from the below table "employees" :-
employee_id
name
code
designation
salary
101
ABC
E-101
Engineer
12000
102
DEF
E-102
Doctor
8000
103
GHI
E-103
Sof
<-- Chapter 14: SQL >= Operator
Chapter 15
SQL <= Operator
Lets see an example from the below table "employees" :-
employee_id
name
code
designation
salary
101
ABC
E-101
Engineer
12000
102
DEF
E-102
Doctor
8000
103
GHI
E-103
<-- Chapter 7: SQL NOT IN Operator
Chapter 8
SQL = Operator
Lets see an example from the below table "employees" :-
employee_id
name
code
designation
salary
101
ABC
E-101
Engineer
12000
102
DEF
E-102
Doctor
8000
103
GHI
E-103
Soft
<-- Chapter 8: SQL = Operator
Chapter 9
SQL != Operator
Lets see an example from the below table "employees" :-
employee_id
name
code
designation
salary
101
ABC
E-101
Engineer
12000
102
DEF
E-102
Doctor
8000
103
GHI
E-103
Software
<-- Chapter 11: SQL BETWEEN Operator
Chapter 12
SQL > Operator
Lets see an example from the below table "employees" :-
employee_id
name
code
designation
salary
101
ABC
E-101
Engineer
12000
102
DEF
E-102
Doctor
8000
103
GHI
E-10
<-- Chapter 12: SQL > Operator
Chapter 13
SQL < Operator
Lets see an example from the below table "employees" :-
employee_id
name
code
designation
salary
101
ABC
E-101
Engineer
12000
102
DEF
E-102
Doctor
8000
103
GHI
E-103
S
<-- Chapter 10: SQL LIKE Operator
Chapter 11
SQL BETWEEN Operator
Lets see an example from the below table "employees" :-
employee_id
name
code
designation
salary
101
ABC
E-101
Engineer
12000
102
DEF
E-102
Doctor
8000
103
GHI
E-10
Hello Guys
I configured office365 email in liferay to send email via smtp by using below properties :
mail.session.mail.transport.protocol=smtp
mail.session.mail.smtp.user=admin@domain.com
mail.session.mail.smtp.password=m8Kw
mail.session.m
A Transaction groups a set of tasks into a single execution unit. Each transaction begins with a specific task and ends when all the tasks in the group successfully finish.If all of these tasks execute successfully, then a transaction is committed an
Before SQL Server 2005, the only practical way to trap errors in SQL was using the old-fashioned @@error system variable. Although this is still supported, in this blog we will learn how to use TRY-CATCH for handling errors.TRY-CATCH block is simila
