Database - Check Constraint

-

The CHECK constraint is used to limit the value range that can be placed in a column.
If you define a CHECK constraint on a single column it allows only certain values for
this column.
If you define a CHECK constraint on a table it can limit the values
in certain columns based on values in other columns in the row.

 create table emp_det3(empno int constraint pk_empdet3 primary key,
ename varchar(20),city varchar(20),
state char(2) constraint ck_sta1 check(state in('TN','AP','KL')))
select *from emp_det3

Comments

Post a Comment

Popular posts from this blog

How to set Java Object into JaxBElement ?

-
How to set Java Object into JaxBElement ? * In JaxBElement we are having setValue(T t) method. this will help us to solve this problem. * java.xml.bind.JAXBElement.setValue() Eg. Lets Use College Class as Bean. MainJaxBElement class as main class to process the College Class. package com.javavirus.jaxbelement; import javax.xml.bind.annotation.XmlAttribute; import javax.xml.bind.annotation.XmlElement; import javax.xml.bind.annotation.XmlRootElement; @XmlRootElement public class College{ private int id; private String name; public College(int id, String name) { super(); this.id = id; this.name = name; } public int getId() { return id; } @XmlAttribute public void setId(int id) { this.id = id; } public String getName() { return name; } @XmlElement public void setName(String name) { this.name = name; } @Override public String toString() { return "College [id=" + id + ", name=" + name + "]"...
Read more

GitLab

-
Pipeline: * Group of jobs executed in Stages. * All of the jobs executed in parallel in stage. * if all jobs succeed, pipeline move to next stage. * if any one job failed, next stage is not executed. Types of Pipeline: * CI Pipeline build and test stages defined (.gitlab-ci.yml) * Deploy Pipeline: define in .gitlab-ci.yml. Flow of deploying code to server thru various stages. * Project Pipeline: Specially for microservices. Cross project CI depencies, triggered via API. GitLab Architecture: * GitLab Server and atleast one GitLab Runner. * Runner is the one will start the job. * Project Setting -CICD - * GitLab Runner is automatically provided by GitLab Server. * We can also configured our own runners. Why GITLab CI: * Simple Architecture * Docker first approach. * Pipeline as code. * Merge request with CI support. Eg. Build file location: /builds/kumarvinothjoseph/spring-boot-integration-watch-directory/target/spring-integration-moni...
Read more