text stringlengths 6 9.38M |
|---|
CREATE Procedure sp_update_OrderQty as
Begin Tran
Update items set OrderQty = isnull(StockNorm, 0)
update items set OrderQty = OrderQty -
isnull((select sum(Batch_Products.Quantity) from batch_products
where Batch_products.Product_Code = Items.Product_Code
and (Batch_products.Expiry >= Getdate() OR Batch_Products.Expiry IS NULL)),0)
where ISNULL(StockNorm,0) <> 0
update items set OrderQty = OrderQty -
isnull((select sum(PODetail.Pending) from PODetail, POAbstract
where PODetail.Product_Code = Items.Product_Code AND
POAbstract.PONumber = PODetail.PONumber AND
(POAbstract.Status & 128) = 0),0) where ISNULL(StockNorm,0) <> 0
Update Items Set OrderQty = OrderQty -
IsNull((Select Sum(Stock_Request_Detail.Pending)
From Stock_Request_Detail, Stock_Request_Abstract
Where Stock_Request_Detail.Product_Code = Items.Product_Code And
Stock_Request_Abstract.Stock_Req_Number = Stock_Request_Detail.Stock_Req_Number And
(Stock_Request_Abstract.Status & 128) = 0), 0) Where IsNull(StockNorm, 0) <> 0
update items set OrderQty = cast(OrderQty as int) - (cast(OrderQty as int) % cast(MinOrderQty as int))
where Isnull(MinOrderQty, 0) <> 0
Commit Tran
|
------CHECKS-----
/*
SELECT
RTRIM(LTRIM(CUSKEY2)) CHECKN, SUM(AMT)
FROM
FFSBGLR1
WHERE
PERD = '1605' AND
(MODULE = 'APCQ' OR (MODULE = 'GJJB' AND SUBSTRING(CUSKEY4,2,3) IN ('510','511','512'))) AND
SUBSTRING(ACCT,7,4) = '1010'
GROUP BY
RTRIM(LTRIM(CUSKEY2))
*/
-----CHECK RUNS----------
/*
SELECT
RTRIM(LTRIM(CUSKEY1)) CHKRUN, SUM(AMT)
FROM
FFSBGLR1
WHERE
PERD = '1605' AND
MODULE = 'APCQ' AND
SUBSTRING(ACCT,7,4) = '1010'
GROUP BY
RTRIM(LTRIM(CUSKEY1))
*/
-----------AR Batches-------------------------
/*
SELECT
RTRIM(LTRIM(CUSKEY3)) CHKRUN, SUM(AMT)
FROM
FFSBGLR1
WHERE
PERD = '1605' AND
MODULE = 'ARRC' AND
SUBSTRING(ACCT,7,4) = '1010'
GROUP BY
RTRIM(LTRIM(CUSKEY3))
HAVING
SUM(AMT) <> 0
*/
----------VENDOR SPECIFIC-------------------------------------
/*
SELECT
RTRIM(LTRIM(CUSKEY1)) CHKRUN, RTRIM(LTRIM(CUSVEND)) VEND, SUM(AMT)
FROM
FFSBGLR1
WHERE
PERD = '1605' AND
MODULE = 'APCQ' AND
SUBSTRING(ACCT,7,4) = '1010'
GROUP BY
RTRIM(LTRIM(CUSKEY1)), RTRIM(LTRIM(CUSVEND))
*/ |
CREATE OR REPLACE VIEW V_ZB001_ZB AS
(
SELECT JSDE101,DE011,DE022,JSDE940,JSDE008,DE151,DE186,DE156,CZDE951,SUM(DE181) AS DE181,SUM(TZJE) AS TZJE,
SUM(SYJE) AS SYJE,SUM(ZTSYJE) AS ZTSYJE,SUM(KYJE) AS KYJE
,CZDE182 ,TO_CHAR(DE001,'YYYY-MM-DD') AS DE001,JSDE909,JSDE007,DE062,CZDE938
FROM V_ZB001_MX
GROUP BY JSDE101,DE011,DE022,JSDE940,JSDE008,DE151,DE186,DE156,CZDE951,CZDE182 ,TO_CHAR(DE001,'YYYY-MM-DD'),
JSDE909,JSDE007,DE062,CZDE938
);
|
INSERT INTO item (item_name, item_price) VALUES ('Burger', 5.00);
INSERT INTO item (item_name, item_price) VALUES ('Nuggets', 3.25);
INSERT INTO item (item_name, item_price) VALUES ('French fried', 2.50);
INSERT INTO item (item_name, item_price) VALUES ('Coffee', 1.55);
INSERT INTO item (item_name, item_price) VALUES ('Tea', 1.10);
INSERT INTO item (item_name, item_price) VALUES ('ChickenBurger', 3.50);
INSERT INTO item (item_name, item_price) VALUES ('GrillBurger', 4.00);
INSERT INTO item (item_name, item_price) VALUES ('DoubleTrouble Burger', 7.00);
INSERT INTO item (item_name, item_price) VALUES ('Cola 0,5', 1.50);
INSERT INTO item (item_name, item_price) VALUES ('Sprite 0,5', 1.50);
INSERT INTO item (item_name, item_price) VALUES ('Latte', 2.50);
INSERT INTO order_d (employee_id, order_date_time) VALUES (21, '2019-08-15 9:05:05');
INSERT INTO order_d (employee_id, order_date_time) VALUES (21, '2019-08-15 9:08:24');
INSERT INTO order_d (employee_id, order_date_time) VALUES (15, '2019-08-15 10:12:22');
INSERT INTO order_d (employee_id) VALUES (12);
INSERT INTO order_d (employee_id) VALUES (77);
INSERT INTO item_in_order (iio_order_id, iio_item_id, iio_item_name, iio_item_price, iio_item_count) VALUES (1, 1, 'Burger', 5.00, 1);
INSERT INTO item_in_order (iio_order_id, iio_item_id, iio_item_name, iio_item_price, iio_item_count) VALUES (1, 4, 'Coffee', 1.55, 1);
INSERT INTO item_in_order (iio_order_id, iio_item_id, iio_item_name, iio_item_price, iio_item_count) VALUES (1, 5, 'Tea', 1.10, 2);
INSERT INTO item_in_order (iio_order_id, iio_item_id, iio_item_name, iio_item_price, iio_item_count) VALUES (2, 2, 'Nuggets', 3.25, 2);
INSERT INTO item_in_order (iio_order_id, iio_item_id, iio_item_name, iio_item_price, iio_item_count) VALUES (2, 3, 'French fried', 2.50, 2);
INSERT INTO item_in_order (iio_order_id, iio_item_id, iio_item_name, iio_item_price, iio_item_count) VALUES (3, 4, 'Coffee', 1.55, 2);
INSERT INTO item_in_order (iio_order_id, iio_item_id, iio_item_name, iio_item_price, iio_item_count) VALUES (3, 5, 'Tea', 1.10, 3);
INSERT INTO item_in_order (iio_order_id, iio_item_id, iio_item_name, iio_item_price, iio_item_count) VALUES (4, 2, 'Nuggets', 3.25, 2);
INSERT INTO item_in_order (iio_order_id, iio_item_id, iio_item_name, iio_item_price, iio_item_count) VALUES (4, 3, 'French fried', 2.50, 3);
INSERT INTO item_in_order (iio_order_id, iio_item_id, iio_item_name, iio_item_price, iio_item_count) VALUES (4, 4, 'Coffee', 1.55, 2);
INSERT INTO item_in_order (iio_order_id, iio_item_id, iio_item_name, iio_item_price, iio_item_count) VALUES (4, 5, 'Tea', 1.10, 1);
INSERT INTO item_in_order (iio_order_id, iio_item_id, iio_item_name, iio_item_price, iio_item_count) VALUES (5, 2, 'Nuggets', 3.25, 2);
INSERT INTO item_in_order (iio_order_id, iio_item_id, iio_item_name, iio_item_price, iio_item_count) VALUES (5, 3, 'French fried', 2.50, 3);
INSERT INTO item_in_order (iio_order_id, iio_item_id, iio_item_name, iio_item_price, iio_item_count) VALUES (5, 4, 'Coffee', 1.55, 2);
INSERT INTO item_in_order (iio_order_id, iio_item_id, iio_item_name, iio_item_price, iio_item_count) VALUES (5, 5, 'Burger', 5.00, 8);
INSERT INTO item_in_order (iio_order_id, iio_item_id, iio_item_name, iio_item_price, iio_item_count) VALUES (5, 6, 'ChickenBurger', 3.50, 2);
INSERT INTO item_in_order (iio_order_id, iio_item_id, iio_item_name, iio_item_price, iio_item_count) VALUES (5, 7, 'GrillBurger', 4.00, 2);
INSERT INTO item_in_order (iio_order_id, iio_item_id, iio_item_name, iio_item_price, iio_item_count) VALUES (5, 9, 'Cola 0,5', 1.50, 5);
INSERT INTO item_in_order (iio_order_id, iio_item_id, iio_item_name, iio_item_price, iio_item_count) VALUES (5, 10, 'Sprite 0,5', 1.50, 12);
|
INSERT INTO `leads_records` (
`id`, `content_id`, `name`, `email`, `phone`, `profile_id`, `date_time`
) VALUES (
1, 5, 'Leonardo da Vince', 'leo@art.com', '0012341234', 1, '2020-06-01 16:28:00'
),(
2, 4, 'Salvador Dalí', 'salvador@art.com', '0012345678', 2, '2020-06-01 17:28:00'
),(
3, 3, 'Michelangelo', 'michelangelo@art.com', '0012340123', 3, '2020-06-01 18:28:00'
),(
4, 3, 'Rafael Sanzio', 'rafael@art.com', '0012343210', 4, '2020-06-02 16:04:00'
); |
select * from PortfolioProject.dbo.CovidDeaths
--select count(*) from PortfolioProject.dbo.CovidDeaths
--select count(*), location from PortfolioProject.dbo.CovidDeaths group by location;
select * from PortfolioProject.dbo.CovidDeaths order by 3,4
--select * from PortfolioProject.dbo.CovidVactinations order by 3,4
select location,date,total_cases,new_cases,total_deaths,population
from PortfolioProject.dbo.CovidDeaths order by 1,2
--Looking for total cases vs total deaths
select sum(total_cases) as total,location
from PortfolioProject.dbo.CovidDeaths group by location
--shows likelihood dying if you contract covid in your country
select location,date,total_cases,total_deaths,(total_deaths/total_cases)*100 as DeathPercentage
from PortfolioProject.dbo.CovidDeaths where location like '%india%' order by 1,2
--Looking total cases vs population
select location,date,total_cases,population, (total_cases/population)*100 as InfetctedPopulation
from PortfolioProject.dbo.CovidDeaths --where location like '%india%'
order by 1,2
--What country have the highest infection rate compare to population
select location,population,Max(total_cases) as cases , Max((total_cases/population)*100) as PercentInfetctedPopulation
from PortfolioProject.dbo.CovidDeaths --where location like '%india%'
group by location,population
order by PercentInfetctedPopulation desc
--check in India, have the highest infection rate compare to population
select location,Max(total_cases) as cases , Max((total_cases/population)*100) as PercentInfetctedPopulation
from PortfolioProject.dbo.CovidDeaths
group by location
having location='india'
--showing countries with highest death count per population
select location,Max(cast(total_deaths as int)) as deaths
From PortfolioProject.dbo.CovidDeaths
where continent is not null
group by location
order by deaths desc
--showing continent with highest death counts
select continent,Max(cast(total_deaths as int)) as deaths
From PortfolioProject.dbo.CovidDeaths
where continent is not null
group by continent
order by deaths desc
--Global wise numbers
select sum(new_cases) as totalcase, sum(cast(new_deaths as int)) as totaldeaths,
sum(cast(new_deaths as int))/sum(new_cases)*100 as deathpercentage
From PortfolioProject.dbo.CovidDeaths
where continent is not null
order by 1,2
select * from PortfolioProject.dbo.CovidVactinations order by 1,2
select * from PortfolioProject.dbo.CovidDeaths
--Lets Join this two tables:
--total vactination vs total population
select * from PortfolioProject.dbo.CovidDeaths dea join PortfolioProject.dbo.CovidVactinations vac
on dea.location=vac.location and dea.date=vac.date
select dea.continent,dea.location,dea.date,dea.population,vac.new_vaccinations from PortfolioProject.dbo.CovidDeaths dea join PortfolioProject.dbo.CovidVactinations vac
on dea.location=vac.location and dea.date=vac.date
where dea.continent is not null
and dea.date=vac.date order by 1,2,3
--Total vaccination location wise
select dea.continent,dea.location,dea.date,dea.population,vac.new_vaccinations
from PortfolioProject.dbo.CovidDeaths dea join PortfolioProject.dbo.CovidVactinations vac
on dea.location=vac.location and dea.date=vac.date
where dea.continent is not null
and dea.date=vac.date order by 1,2,3
select dea.continent,dea.location,dea.date,dea.population,vac.new_vaccinations,
sum(convert(int,vac.new_vaccinations)) over (partition by dea.location order by dea.location, dea.date) as RolllingPeopleVaccinated
--(RolllingPeopleVaccinated/poulation)*100// this is as error and that is why we are creatting CTE
from PortfolioProject.dbo.CovidDeaths dea join PortfolioProject.dbo.CovidVactinations vac
on dea.location=vac.location and dea.date=vac.date
where dea.continent is not null
and dea.date=vac.date order by 1,2,3
--by using CTE, it will add extra column which is created by alias and allow you to calculate the same.
with PopVsVac ( continent,location,date,population,new_vaccinations,RolllingPeopleVaccinated)
as
(select dea.continent,dea.location,dea.date,dea.population,vac.new_vaccinations,
sum(convert(int,vac.new_vaccinations)) over (partition by dea.location order by dea.location, dea.date) as RolllingPeopleVaccinated
--(RolllingPeopleVaccinated/poulation)*100// this is as error and that is why we are creatting CTE
from PortfolioProject.dbo.CovidDeaths dea join PortfolioProject.dbo.CovidVactinations vac
on dea.location=vac.location and dea.date=vac.date
where dea.continent is not null
and dea.date=vac.date )
select *,(RolllingPeopleVaccinated/population)*100 from PopVsVac
--By using temp table
create table PercentPopulationVacinated
(continent nvarchar(255),location nvarchar(255),date datetime,population numeric,new_vaccinations numeric,RolllingPeopleVaccinated numeric)
insert into PercentPopulationVacinated
select dea.continent,dea.location,dea.date,dea.population,vac.new_vaccinations,
sum(convert(int,vac.new_vaccinations)) over (partition by dea.location order by dea.location, dea.date) as RolllingPeopleVaccinated
--(RolllingPeopleVaccinated/poulation)*100// this is as error and that is why we are creatting CTE
from PortfolioProject.dbo.CovidDeaths dea join PortfolioProject.dbo.CovidVactinations vac
on dea.location=vac.location and dea.date=vac.date
where dea.continent is not null
and dea.date=vac.date
select * from PercentPopulationVacinated
select max(RolllingPeopleVaccinated),location from PercentPopulationVacinated group by location
--Creating view to store data for later visualization
create view PercentagePopulationVacinated as select dea.continent,dea.location,dea.date,dea.population,vac.new_vaccinations,
sum(convert(int,vac.new_vaccinations)) over (partition by dea.location order by dea.location, dea.date) as RolllingPeopleVaccinated
--(RolllingPeopleVaccinated/poulation)*100// this is as error and that is why we are creatting CTE
from PortfolioProject.dbo.CovidDeaths dea join PortfolioProject.dbo.CovidVactinations vac
on dea.location=vac.location and dea.date=vac.date
where dea.continent is not null
select * from dbo.PercentagePopulationVacinated
--
on
|
-- Apr 19, 2010 5:37:09 PM COT
-- 2987531_Cannot search on Posted field
UPDATE AD_Column SET AD_Reference_Value_ID=234,Updated=TO_DATE('2010-04-19 17:37:09','YYYY-MM-DD HH24:MI:SS'),UpdatedBy=100 WHERE AD_Column_ID=56347
;
-- Apr 19, 2010 5:43:13 PM COT
UPDATE AD_Column SET AD_Reference_ID=28, AD_Reference_Value_ID=234,Updated=TO_DATE('2010-04-19 17:43:13','YYYY-MM-DD HH24:MI:SS'),UpdatedBy=100 WHERE AD_Column_ID=57934
;
-- Apr 19, 2010 5:44:04 PM COT
UPDATE AD_Column SET AD_Reference_ID=17, AD_Reference_Value_ID=234,Updated=TO_DATE('2010-04-19 17:44:04','YYYY-MM-DD HH24:MI:SS'),UpdatedBy=100 WHERE AD_Column_ID=58179
;
|
-- MySQL dump 10.13 Distrib 5.7.9, for osx10.9 (x86_64)
--
-- Host: 127.0.0.1 Database: glucometer
-- ------------------------------------------------------
-- Server version 5.7.11
/*!40101 SET @OLD_CHARACTER_SET_CLIENT=@@CHARACTER_SET_CLIENT */;
/*!40101 SET @OLD_CHARACTER_SET_RESULTS=@@CHARACTER_SET_RESULTS */;
/*!40101 SET @OLD_COLLATION_CONNECTION=@@COLLATION_CONNECTION */;
/*!40101 SET NAMES utf8 */;
/*!40103 SET @OLD_TIME_ZONE=@@TIME_ZONE */;
/*!40103 SET TIME_ZONE='+00:00' */;
/*!40014 SET @OLD_UNIQUE_CHECKS=@@UNIQUE_CHECKS, UNIQUE_CHECKS=0 */;
/*!40014 SET @OLD_FOREIGN_KEY_CHECKS=@@FOREIGN_KEY_CHECKS, FOREIGN_KEY_CHECKS=0 */;
/*!40101 SET @OLD_SQL_MODE=@@SQL_MODE, SQL_MODE='NO_AUTO_VALUE_ON_ZERO' */;
/*!40111 SET @OLD_SQL_NOTES=@@SQL_NOTES, SQL_NOTES=0 */;
--
-- Table structure for table `remarks_table`
--
DROP TABLE IF EXISTS `remarks_table`;
/*!40101 SET @saved_cs_client = @@character_set_client */;
/*!40101 SET character_set_client = utf8 */;
CREATE TABLE `remarks_table` (
`remarkID` bigint(20) NOT NULL AUTO_INCREMENT,
`isCreatedOn` varchar(255) DEFAULT NULL,
`remarkString` varchar(255) DEFAULT NULL,
`remarkTitle` varchar(255) DEFAULT NULL,
`assignedDoctor_personID` bigint(20) DEFAULT NULL,
`assignedPatient_personId` bigint(20) DEFAULT NULL,
`additionalCommentsFromUser` varchar(255) DEFAULT NULL,
`isAvaliable` bit(1) DEFAULT NULL,
`doctorUsername` varchar(255) DEFAULT NULL,
`patientUsername` varchar(255) DEFAULT NULL,
PRIMARY KEY (`remarkID`),
KEY `FK_j2k84i63o5ybk5mn5wq8j1ij6` (`assignedDoctor_personID`),
KEY `FK_lscn9bm8weqfql348hx8f2wnh` (`assignedPatient_personId`),
CONSTRAINT `FK_j2k84i63o5ybk5mn5wq8j1ij6` FOREIGN KEY (`assignedDoctor_personID`) REFERENCES `doctor_table` (`personID`),
CONSTRAINT `FK_lscn9bm8weqfql348hx8f2wnh` FOREIGN KEY (`assignedPatient_personId`) REFERENCES `user_table` (`personId`)
) ENGINE=InnoDB AUTO_INCREMENT=4 DEFAULT CHARSET=latin1;
/*!40101 SET character_set_client = @saved_cs_client */;
--
-- Dumping data for table `remarks_table`
--
LOCK TABLES `remarks_table` WRITE;
/*!40000 ALTER TABLE `remarks_table` DISABLE KEYS */;
INSERT INTO `remarks_table` VALUES (2,NULL,'The Glucose Levels are looking fine','Everything is fine',NULL,NULL,NULL,'','mike','aapeshave'),(3,NULL,'The Glucose Levels are looking fine','Keep Up!',NULL,NULL,NULL,'','mike','aapeshave');
/*!40000 ALTER TABLE `remarks_table` ENABLE KEYS */;
UNLOCK TABLES;
/*!40103 SET TIME_ZONE=@OLD_TIME_ZONE */;
/*!40101 SET SQL_MODE=@OLD_SQL_MODE */;
/*!40014 SET FOREIGN_KEY_CHECKS=@OLD_FOREIGN_KEY_CHECKS */;
/*!40014 SET UNIQUE_CHECKS=@OLD_UNIQUE_CHECKS */;
/*!40101 SET CHARACTER_SET_CLIENT=@OLD_CHARACTER_SET_CLIENT */;
/*!40101 SET CHARACTER_SET_RESULTS=@OLD_CHARACTER_SET_RESULTS */;
/*!40101 SET COLLATION_CONNECTION=@OLD_COLLATION_CONNECTION */;
/*!40111 SET SQL_NOTES=@OLD_SQL_NOTES */;
-- Dump completed on 2016-04-30 10:36:00
|
create or replace package github_repos
as
/** Interface to Github repositories API. To call any of these, we expect that github session has been
* set up prior to calling.
* @author Morten Egan (github.com/morten-egan)
* @project OracleGit
* @version 0.1.0
*/
/** Create a repository.
* @author Morten Egan
* @param git_account The account that creates the repository on github
* @param repos_name The name of the repository
* @param homepage A URL with more information about the repository
* @param private Either true to create a private repository, or false to create a public one. Creating private repositories requires a paid GitHub account. Default: false
* @param has_issues Either true to enable issues for this repository, false to disable them. Default: true
* @param has_wiki Either true to enable the wiki for this repository, false to disable it. Default: true
* @param has_downloads Either true to enable downloads for this repository, false to disable them. Default: true
* @param team_id The id of the team that will be granted access to this repository. This is only valid when creating a repository in an organization.
* @param auto_init Pass true to create an initial commit with empty README. Default: false
* @param gitignore_template Desired language or platform .gitignore template to apply. Use the name of the template without the extension. For example, “Haskell”. Ignored if the auto_init parameter is not provided.
* @param use_org Boolean value to define if it should be created in an organization
* @param org_name The name of the organization to create the repository under.
*/
procedure repos_create (
git_account varchar2
, repos_name varchar2
, description varchar2 default null
, homepage varchar2 default null
, private boolean default false
, has_issues boolean default true
, has_wiki boolean default true
, has_downloads boolean default true
, team_id number default null
, auto_init boolean default false
, gitignore_template varchar2 default null
, use_org boolean default false
, org_name varchar2 default null
);
/** Return information about specific repository.
* @author Morten Egan
* @param git_account The account owner of the repository
* @param repos_name The name of the repository to get
*/
function repos_get (
git_account varchar2
, repos_name varchar2
)
return github.call_result;
/** Repository list
* @author Morten Egan
* @param repos_type Can be one of all, owner, member. Default: owner
* @param repos_sort Can be one of created, updated, pushed, full_name. Default: full_name
* @param repos_direction Can be one of asc or desc. Default: when using full_name: asc, otherwise desc
*/
function repositories (
git_account varchar2
, repos_type varchar2 default 'owner'
, repos_sort varchar2 default 'full_name'
, repos_direction varchar2 default 'asc'
)
return github.call_result;
/** Edit an existing repository
* @author Morten Egan
* @param git_account The account that owns the repository
* @param repos_name The name of the repository
* @param description A short description of the repository
* @param homepage A URL with more information about the repository
* @param private Either true to make the repository private, or false to make it public. Creating private repositories requires a paid GitHub account. Default: false
* @param has_issues Either true to enable issues for this repository, false to disable them. Default: true
* @param has_wiki Either true to enable the wiki for this repository, false to disable it. Default: true
* @param has_downloads Either true to enable downloads for this repository, false to disable them. Default: true
* @param default_branch Updates the default branch for this repository.
*/
procedure repos_edit (
git_account varchar2
, repos_name varchar2
, description varchar2 default null
, homepage varchar2 default null
, private boolean default false
, has_issues boolean default true
, has_wiki boolean default true
, has_downloads boolean default true
, default_branch varchar2 default null
);
/** List contributors to the specified repository, sorted by the number of commits per contributor in descending order.
* @author Morten Egan
* @param git_account The owner of the repository
* @param repos_name The name of the repository
* @param anon Set to 1 or true to include anonymous contributors in results.
* @return
*/
function repos_contributors (
git_account varchar2
, repos_name varchar2
, anon varchar2 default '1'
)
return github.call_result;
/** List languages for the specified repository. The value on the right of a language is the number of bytes of code written in that language.
* @author Morten Egan
* @param git_account The owner of the repository
* @param repos_name The name of the repository
* @return Languages used
*/
function repos_languages (
git_account varchar2
, repos_name varchar2
)
return github.call_result;
/** List teams for the specified repository
* @author Morten Egan
* @param git_account The owner of the repository
* @param repos_name The name of the repository
* @return Teams in the repository
*/
function repos_teams (
git_account varchar2
, repos_name varchar2
)
return github.call_result;
/** List tags for the specified repository
* @author Morten Egan
* @param git_account The owner of the repository
* @param repos_name The name of the repository
* @return Tags in the repository
*/
function repos_tags (
git_account varchar2
, repos_name varchar2
)
return github.call_result;
/** List branches for the specified repository
* @author Morten Egan
* @param git_account The owner of the repository
* @param repos_name The name of the repository
* @return Branches in the repository
*/
function repos_branches (
git_account varchar2
, repos_name varchar2
)
return github.call_result;
/** Get specific branch in repository
* @author Morten Egan
* @param git_account The owner of the repository
* @param repos_name The name of the repository
* @return Branch details of specified branch
*/
function repos_branch_get (
git_account varchar2
, repos_name varchar2
, branch varchar2
)
return github.call_result;
/** Deleting a repository requires admin access. If OAuth is used, the delete_repo scope is required.
* @author Morten Egan
* @param git_account The owner of the repository
* @param repos_name The name of the repository
*/
procedure repos_delete (
git_account varchar2
, repos_name varchar2
);
end github_repos;
/ |
Create VIEW [V_Quotation_Abstract]
([Quotation_ID],[Customer_ID],[From_Date],[To_Date],[Invoice_Scheme_Allowed])
AS
SELECT QuotationAbstract.QuotationID,QuotationCustomers.CustomerID,QuotationAbstract.ValidFromDate,QuotationAbstract.ValidToDate,
QuotationAbstract.AllowInvoiceScheme
FROM QuotationAbstract
Left Outer Join QuotationCustomers On QuotationCustomers.QuotationID = QuotationAbstract.QuotationID
join tbl_merp_OLClassMapping OLM on OLM.CustomerID =QuotationCustomers.CustomerID
join tbl_merp_OLClass OL on OL.ID = OLM.OLClassID
join tbl_mERP_QuotChannelDetail CD on CD.Channel_Type_Code =OL.Channel_Type_Code
Where QuotationAbstract.Active = 1
And OLM.Active =1
And CD.Active = 1
AND validtodate > = getdate()
And QuotationAbstract.QuotationType <> 4
union
select cast(SubGrp.GroupID as varchar(5))+cast(SC.SchemeID+10000 as varchar(25)), SC.CustomerCode,SD.ActiveFrom,SD.ActiveTo,1 'Invoice_Scheme_Allowed'
from dbo.mERP_fn_Get_CSOutletScopeHH_QuotPR() SC
inner join
(select distinct TSA.*,TSSD.SlabID as SlabID,TSSD.groupid as Groupid, TSSD.Value from tbl_mERP_SchemeAbstract TSA
inner join tbl_mERP_SchemeSlabDetail TSSD on TSSD.SchemeID = TSA.SchemeID
--CC
Inner Join tbl_mERP_SchemeSubGroup SubGrp On SubGrp.SubGroupID = TSSD.GroupID And SubGrp.SchemeID = TSSD.SchemeID
--And TSSD.GroupID In(Select Max(SubGroupID) From tbl_mERP_SchemeSubGroup Where SchemeID = TSSD.SchemeID And GroupID = SubGrp.GroupID)
--CC
where isnull(TSSD.GroupID,0)<>0 and TSA.SchemeType = 5) SD
on SD.Schemeid=SC.schemeid and SD.groupid=SC.groupid
Inner Join tbl_mERP_SchemeSubGroup SubGrp On SubGrp.SubGroupID = SC.GroupID And SubGrp.SchemeID = SC.SchemeID
where SC.CustomerCode not in
(
select distinct QuotationCustomers.CustomerID from QuotationCustomers
Join QuotationAbstract On QuotationCustomers.QuotationID = QuotationAbstract.QuotationID
join tbl_merp_OLClassMapping OLM on OLM.CustomerID =QuotationCustomers.CustomerID
join tbl_merp_OLClass OL on OL.ID = OLM.OLClassID
join tbl_mERP_QuotChannelDetail CD on CD.Channel_Type_Code =OL.Channel_Type_Code
Where OLM.Active =1
And CD.Active = 1
And QuotationAbstract.Active = 1
)
|
--CREATE SCHEMA Examples;
--GO
CREATE TABLE Examples.Widget (
WidgetCode Varchar (10) NOT NULL CONSTRAINT PKWidget PRIMARY KEY,
WidgetName varchar (100) NULL,
WidgetPrice varchar (10) NULL
);
select * from examples.widget
DROP TABLE Examples.Widget; |
BEGIN TRANSACTION;
CREATE TABLE IF NOT EXISTS `plant` (
`PlantID` INTEGER PRIMARY KEY AUTOINCREMENT,
`PlantNameSinhala` TEXT,
`PlantNameEnglish` TEXT,
`PlantScientificName` TEXT,
`PlantFamily` TEXT,
`Description` TEXT
);
INSERT INTO `plant` VALUES (1,'Koboleela','Orchid tree','Bauhinia variegata','FABACEAE','A medium sized deciduous tree. Leaves alternate, simple, 5-10 cm long, bilobed at apex. Flowers in racemes, irregular, fragrant, white or purplish, large. Fruit a legume, 15-20 cm long and 1.8 cm broad, 6-15 seeded.');
INSERT INTO `plant` VALUES (2,'Heen bovitiya','-','Osbeckia octandra','MELASTOMACEAE','A much branched shrublet, up to about 2 m tall. Leaves 1.5-6 x 0.5-2 cm; petiole 1-5 mm long. Flowers few or up to 10 in loose clusters; hypanthium3-6 wide; Petals 15-19 mm long, pink to mauve and purple. Fruit a dry capsule inside the persistent hypanthium; seeds numerous.');
INSERT INTO `plant` VALUES (3,'atha','Pond apple','Annona glabra','ANNONACEAE','A tree 1 – 12 m tall. Leaf blade 6 – 20 cm long, 3 – 8 cm wide, elliptical or elliptical ovate, obtuse or rounded at base but shortly decurrent along petiole, acute, rarely obtuse at apex, thinly coriaceous, quite glabrous at maturity. Flowers solitary, intermodal or terminal on a short branchelets. Ripe fruit ovoid, rounded at apex, yellow to orange, smooth, pulp not edible, yellowish. Seeds 13 – 15 mm long, pale reddish-brown, testa readily peeling.');
INSERT INTO `plant` VALUES (4,'Kalu weraniya','-','Justicia gendarussa','ACANTHACEAE','Undershrub, to 1.5 m high. Leaves oblong-lanceolate, 4 – 12.6 X 0.4 – 2.6 cm, cuneate at base, acute to shortly acuminate at apex, undulate, glabrous, with prominent nerves beneath. Spikes terminal, lax, to 10 cm long. Capsuie not seen.');
INSERT INTO `plant` VALUES (5,'Thippili','Long pepper','Piper longum','PIPERACEAE','Perennial herb; stems numerous, 60-90 cm long, ascending or prostrate; nodes thickened; young parts glabrous. Leaves 3.7-8. cm long, cordate at base; petioles 7 5-7.5 cm long. Flowers dioecious in dense cylindrical spikes; sikes 2.5-3.7 cm long. Fruit very small, completely sunk in solid fleshy spike, blackish green.');
CREATE TABLE IF NOT EXISTS `Treatment` (
`TreatmentID` INTEGER PRIMARY KEY AUTOINCREMENT,
`PlantID` INTEGER,
`TreamentFor` TEXT
);
INSERT INTO `Treatment` VALUES (1,1,'Worm diseases');
INSERT INTO `Treatment` VALUES (2,1,'Wounds');
INSERT INTO `Treatment` VALUES (3,1,'Skin diseases');
INSERT INTO `Treatment` VALUES (4,1,'Dysentery');
INSERT INTO `Treatment` VALUES (5,1,'Rectal prolapse');
INSERT INTO `Treatment` VALUES (6,1,'Haemorrhoids');
INSERT INTO `Treatment` VALUES (7,1,'Constipation');
INSERT INTO `Treatment` VALUES (8,1,'Coughs');
INSERT INTO `Treatment` VALUES (9,1,'Hyperthyroidism');
INSERT INTO `Treatment` VALUES (10,1,'Flatulence');
INSERT INTO `Treatment` VALUES (11,1,'Snake poison');
INSERT INTO `Treatment` VALUES (12,2,'Diabetes mellitus');
INSERT INTO `Treatment` VALUES (13,2,'Haemorrhoids');
INSERT INTO `Treatment` VALUES (14,2,'Hepatitis');
INSERT INTO `Treatment` VALUES (15,2,'Ascites');
INSERT INTO `Treatment` VALUES (16,2,'Liver disorders');
INSERT INTO `Treatment` VALUES (17,2,'Jaundice');
INSERT INTO `Treatment` VALUES (18,2,'Hyperlipidaemia');
INSERT INTO `Treatment` VALUES (19,3,'Naso - Pharyngeal infections');
INSERT INTO `Treatment` VALUES (20,3,'Cancer growth');
INSERT INTO `Treatment` VALUES (21,3,'Coughs');
INSERT INTO `Treatment` VALUES (22,3,'Fevers');
INSERT INTO `Treatment` VALUES (23,3,'Dysentery');
INSERT INTO `Treatment` VALUES (24,4,'Rheumatism');
INSERT INTO `Treatment` VALUES (25,4,'Fevers');
INSERT INTO `Treatment` VALUES (26,4,'Jaundice');
INSERT INTO `Treatment` VALUES (27,4,'Diarrhoea');
INSERT INTO `Treatment` VALUES (28,4,'Hemiplegia');
INSERT INTO `Treatment` VALUES (29,4,'Facial paralysis');
INSERT INTO `Treatment` VALUES (30,4,'Coughs');
INSERT INTO `Treatment` VALUES (31,4,'Ear ache');
INSERT INTO `Treatment` VALUES (32,4,'Glandular swellings');
INSERT INTO `Treatment` VALUES (33,4,'Eczema');
INSERT INTO `Treatment` VALUES (34,4,'Asthma');
INSERT INTO `Treatment` VALUES (35,4,'Oedema of Beri Beri');
INSERT INTO `Treatment` VALUES (36,5,'Acute & chronic bronchitis');
INSERT INTO `Treatment` VALUES (37,5,' Fever');
INSERT INTO `Treatment` VALUES (38,5,'Cough');
INSERT INTO `Treatment` VALUES (39,5,'Spleenomegaly');
INSERT INTO `Treatment` VALUES (40,5,'Hemorrhoids');
INSERT INTO `Treatment` VALUES (41,5,'Piles');
INSERT INTO `Treatment` VALUES (42,5,'Dropsy');
COMMIT;
|
/* point 7 */
select round(avg(om.price - 0.3*om.price),2), os.cid /* avg profit on downloads per customer in total*/
from online_sell os, online_media om
where os.omid=om.id and om.type='download'
group by cid into outfile '/tmp/q2_p7_1.txt';
/*time : 0.19sec */
select round(avg(om.price - 0.3*om.price),2), os.cid, extract(year from os.sell_date) as year /* avg profit on downloads per customer per year*/
from online_sell os, online_media om
where os.omid=om.id and om.type='download'
group by os.cid,extract(year from os.sell_date) into outfile '/tmp/q2_p7_2.txt';
/*time : 0.24sec */
select round(avg(om.price - 0.25*om.price),2), os.cid /* avg profit on views per customer in total*/
from online_sell os, online_media om
where os.omid=om.id and om.type='view'
group by os.cid into outfile '/tmp/q2_p7_3.txt';
/*time : 0.90sec */
select round(avg(om.price - 0.25*om.price),2), os.cid, extract(year from os.sell_date) as year/* avg profit on views per customer per year*/
from online_sell os, online_media om
where os.omid=om.id and om.type='view'
group by os.cid, extract(year from os.sell_date) into outfile '/tmp/q2_p7_4.txt';
/*time : 1.48sec */
select round(avg(pm.price-pm.bought_price),2), ps.cid /* avg profit on hard copies per customer in total */
from physical_sell ps, physical_media pm
where ps.pmid=pm.id
group by ps.cid into outfile '/tmp/q2_p7_5.txt';
/*time : 0.91sec */
select round(avg(pm.price-pm.bought_price),2), ps.cid, extract(year from ps.sell_date) as year/* avg profit on hard copies per customer per year */
from physical_sell ps, physical_media pm
where ps.pmid=pm.id
group by ps.cid, extract(year from ps.sell_date) into outfile '/tmp/q2_p7_6.txt';
/*time : 1.50sec */
|
select stddev_pop(`c_bigint`), stddev_pop(`c_double`)
from `datatype` |
DROP FUNCTION IF EXISTS financialStudentsReport;
DROP FUNCTION IF EXISTS financialProjectsReport; |
ALTER TABLE USER_GROUP_DATABASE_REP DROP INDEX user_group_database_rep_user_id_key;
ALTER TABLE USER_GROUP_DATABASE_REP DROP INDEX user_group_database_rep_representation_id_key; |
CREATE TABLE assets (
asset_id INTEGER PRIMARY KEY
NOT NULL
UNIQUE,
user_id INTEGER REFERENCES users (user_id)
NOT NULL,
name TEXT NOT NULL
);
CREATE TABLE assetValue (
assetValue_id INTEGER PRIMARY KEY
NOT NULL
UNIQUE,
asset_id REFERENCES assets (asset_id)
NOT NULL,
value INTEGER NOT NULL,
amount INTEGER NOT NULL,
dateTimeEntered DATETIME NOT NULL
);
CREATE TABLE liabilities (
liability_id INTEGER PRIMARY KEY
NOT NULL
UNIQUE,
user_id INTEGER REFERENCES users (user_id)
NOT NULL,
name TEXT NOT NULL
);
CREATE TABLE liabilityValue (
liabilityValue_id INTEGER PRIMARY KEY
NOT NULL
UNIQUE,
liability_id REFERENCES liabilities (liability_id)
NOT NULL,
value INTEGER NOT NULL,
amount INTEGER NOT NULL,
dateTimeEntered DATETIME NOT NULL
);
CREATE TABLE users (
user_id INTEGER PRIMARY KEY
UNIQUE
NOT NULL,
name TEXT,
currency TEXT DEFAULT GDP
NOT NULL
); |
CREATE TABLE IF NOT EXISTS `version` (
`id` int(11) NOT NULL,
`sql_version` varchar(128) NOT NULL,
PRIMARY KEY (`id`)
) ENGINE=InnoDB; |
--DROP TABLE m1board;
--DROP SEQUENCE m1board_seq;
CREATE TABLE m1board(
no NUMBER PRIMARY KEY,
title VARCHAR2(100) NOT NULL,
name VARCHAR2(30) NOT NULL,
password VARCHAR2(30) NOT NULL,
content VARCHAR2(4000) NOT NULL,
writeday DATE DEFAULT SYSDATE,
readcount NUMBER DEFAULT 0
);
CREATE SEQUENCE m1board_seq NOCACHE;
select * from m1board;
delete from m1board where no=18;
|
INSERT INTO raw_committee_transactions_errors
(SELECT *
FROM working_transactions
WHERE tran_date > current_date);
DELETE FROM working_transactions
WHERE tran_date > current_date;
INSERT INTO raw_committee_transactions_errors
(SELECT *
FROM working_transactions
WHERE filed_date > current_date);
DELETE FROM working_transactions
WHERE filed_date > current_date; |
-- Some of the classes import their spell access as dashes instead of nulls. Fix them.
update ClassAdvancement set SpellsLevel0 = null where SpellsLevel0 = '—';
update ClassAdvancement set SpellsLevel1 = null where SpellsLevel1 = '—';
update ClassAdvancement set SpellsLevel2 = null where SpellsLevel2 = '—';
update ClassAdvancement set SpellsLevel3 = null where SpellsLevel3 = '—';
update ClassAdvancement set SpellsLevel4 = null where SpellsLevel4 = '—';
update ClassAdvancement set SpellsLevel5 = null where SpellsLevel5 = '—';
update ClassAdvancement set SpellsLevel6 = null where SpellsLevel6 = '—';
update ClassAdvancement set SpellsLevel7 = null where SpellsLevel7 = '—';
update ClassAdvancement set SpellsLevel8 = null where SpellsLevel8 = '—';
update ClassAdvancement set SpellsLevel9 = null where SpellsLevel9 = '—';
update ClassAdvancement set KnownSpellsLevel0 = null where KnownSpellsLevel0 = '—';
update ClassAdvancement set KnownSpellsLevel1 = null where KnownSpellsLevel1 = '—';
update ClassAdvancement set KnownSpellsLevel2 = null where KnownSpellsLevel2 = '—';
update ClassAdvancement set KnownSpellsLevel3 = null where KnownSpellsLevel3 = '—';
update ClassAdvancement set KnownSpellsLevel4 = null where KnownSpellsLevel4 = '—';
update ClassAdvancement set KnownSpellsLevel5 = null where KnownSpellsLevel5 = '—';
update ClassAdvancement set KnownSpellsLevel6 = null where KnownSpellsLevel6 = '—';
update ClassAdvancement set KnownSpellsLevel7 = null where KnownSpellsLevel7 = '—';
update ClassAdvancement set KnownSpellsLevel8 = null where KnownSpellsLevel8 = '—';
update ClassAdvancement set KnownSpellsLevel9 = null where KnownSpellsLevel9 = '—';
begin transaction;
alter table ClassAdvancement add CasterLevel float null;
update ClassAdvancement set CasterLevel = Level where ClassID in (
select distinct ClassID from ClassAdvancement where SpellsLevel1 is not null and Level = 1
);
update ClassAdvancement set CasterLevel = Level/2 where ClassID in (
select ClassID from Class where
ClassID in (
select distinct ClassID from ClassAdvancement where SpellsLevel1 is not null
)
and ClassID not in (
select distinct ClassID from ClassAdvancement where SpellsLevel1 is not null and Level = 1
)
);
commit;
alter table Class add SpellAbilityScore int references AbilityScore( AbilityScoreID );
update Class set SpellAbilityScore = (select AbilityScoreID from AbilityScore where Name = 'Intelligence') where Name in ( 'Wizard' );
update Class set SpellAbilityScore = (select AbilityScoreID from AbilityScore where Name = 'Wisdom' ) where Name in ( 'Druid', 'Ranger', 'Paladin', 'Cleric' );
update Class set SpellAbilityScore = (select AbilityScoreID from AbilityScore where Name = 'Charisma' ) where Name in ( 'Sorcerer', 'Bard' );
|
USE SIAR
ALTER TABLE Prato_Insumo
drop column Tipo
ALTER TABLE Prato_Insumo
ALTER COLUMN Quantidade float |
SELECT DISTINCT site.site_name, stu.local_student_id, stu.last_name, stu.first_name
FROM public.students stu
JOIN matviews.student_session_aff aff ON stu.student_id = aff.student_id
JOIN public.sessions ses ON ses.session_id = aff.session_id
JOIN public.sites site ON site.site_id = ses.site_id
WHERE aff.entry_date >= current_date - 7
ORDER BY site.site_name, stu.last_name |
with na as
(select
year, sport, sex, count(*) lp, sum(case when height = 'NA' or weight = 'NA' then 0 else 1 end) no_na,
avg(case when height = 'NA' or weight = 'NA' then 1 else 0 end) proc_na
from (select id, year, sex, sport,height ,weight from athlete_events a group by id, year, sport,height ,weight, sex) a
group by year, sport, sex),
mediany as
(select a.year, a.sport, a.sex,
percentile_cont(0.5) within group (order by cast( case when height != 'NA' then height end as float)) median_height,
percentile_cont(0.5) within group (order by cast( case when weight != 'NA' then weight end as float)) median_weight
from (select id, year, sex, sport,height ,weight from athlete_events a group by id, year, sport,height ,weight, sex) a
join na on na.year = a.year and na.sport = a.sport and a.sex = na.sex
where na.proc_na < 0.5
and no_na >= 10
group by a.year, a.sport, a.sex),
###-------------- to jest zbiór do eksportu do Tableu ------
baza as
(select a.*, weight/(height/100)^2 bmi
from
(select
id,
name,
a.sex,
age,
case when height = 'NA' then median_height else cast(height as float) end height,
case when weight = 'NA' then median_weight else cast(weight as float) end weight,
team,
noc,
games,
a.year,
season,
city,
a.sport,
event,
medal
from athlete_events a
join mediany m on m.year = a.year and m.sport = a.sport and m.sex = a.sex)a)
select * from
(select
*, rank()over(partition by sex order by std_bmi desc ) rk
from
(select
sex, sport,
stddev_pop(avg_bmi) std_bmi
from
(select year, sex, sport, avg(bmi) avg_bmi
from (select sex, sport, year, id , bmi from baza ) b
group by year, sex, sport)b
group by sex, sport) s)r
where rk = 1
###---------- mój link do Dashboardu Tableu ----
https://public.tableau.com/profile/kglapiak#!/vizhome/BMI_17/Dashboard1?publish=yes |
SELECT * FROM company_management.company WHERE phone LIKE '%817%' ORDER BY company_name; |
alter PROFILE DEFAULT LIMIT PASSWORD_LIFE_TIME UNLIMITED;
alter user system identified by "oracle" replace "oracle";
|
-- #Migration type_chat_type
-- #UP
CREATE TYPE chat_type AS ENUM ('pm', 'group', 'channel');
-- #DOWN
DROP TYPE chat_type;
|
CREATE TABLE [Common].[Users] (
[Id] INT IDENTITY (100000, 4) NOT NULL,
[CredentialsTypeId] SMALLINT NULL,
PRIMARY KEY CLUSTERED ([Id] ASC),
FOREIGN KEY ([CredentialsTypeId]) REFERENCES [Classifications].[CredentialsType] ([Id])
);
|
SELECT DISTINCT M.title
FROM Movies AS M
WHERE M.mID IN (
SELECT RA.mID
FROM Rating AS RA, Reviewer AS RE
WHERE RE.rID = RA.rID AND re.name = 'Sarah Martinez') AND M.title NOT IN (
SELECT DISTINCT M.title
FROM Movies AS M
WHERE M.mID IN (
SELECT RA.mID
FROM Rating AS RA, Reviewer AS RE
WHERE RE.rID = RA.rID AND re.name = 'Chris Jackson'))
|
DROP FUNCTION IF EXISTS createassociated_career;
DROP FUNCTION IF EXISTS updateassociated_career;
DROP FUNCTION IF EXISTS deleteassociated_career;
DROP FUNCTION IF EXISTS getasocareer;
DROP FUNCTION IF EXISTS getasocareers;
DROP FUNCTION IF EXISTS getasocareercenter;
DROP FUNCTION IF EXISTS getasocareerfromcenter;
DROP FUNCTION IF EXISTS getasocareerfromcenterenable;
DROP FUNCTION IF EXISTS disableassocareer;
DROP FUNCTION IF EXISTS enableassocareer; |
USE Cricket
EXEC INSERT_into_Temporarytables
EXEC INSERT_into_Finaltables
EXEC CRICKET..Insert_Umpires_table
EXEC Insert_OR_UPDATE_Venue__Cricketplaying_nations_table
EXEC INSERT_PLAYER_DETAILS
INSERT INTO Cricket..temporaryMatchessummary select * FROM Cricket..Matchessummary
INSERT INTO Cricket..temporarybatsmendetails select * FROM Cricket..batsmendetails
INSERT INTO Cricket..temporarybowlingsummary select * FROM Cricket..bowlingsummary
INSERT INTO cricket..temporaryfallofwickets select * FROM cricket..fallofwickets
|
-- wofh-tools
-- @since 09.11.2014 20:16
-- @package
-- @author DelphinPRO delphinpro@yandex.ru
-- @copyright Copyright (C) 2014 DelphinPRO. All rights reserved.
-- @license Licensed under the MIT license
SELECT
country.countryId,
country.countryTitle,
country.countryFlag,
country.extra,
countryData.pop,
countryData.accounts,
countryData.towns,
countryData.science,
countryData.production,
countryData.war
FROM z_ruXX_countries country
LEFT JOIN z_ruXX_countries_stat countryData
ON country.countryId = countryData.countryId
WHERE countryData.stateDate = :lastDate
AND country.active = 1 |
/*SESSION 2 ASSIGNMENT 3*/
/* 1. Display Recent 50 Orders placed (Id, Order Date, Order Total).*/
use storefront;
SELECT ORDER_PLACED.ORDER_ID, ORDER_PLACED.DATE_OF_ORDER, ORDER_PLACED.BILL_AMOUNT
FROM ORDER_PLACED ORDER BY DATE_OF_ORDER DESC LIMIT 2;
/* 2. Display 10 most expensive Orders.*/
SELECT ORDER_PLACED.ORDER_ID,ORDER_PLACED.BILL_AMOUNT FROM ORDER_PLACED
ORDER BY ORDER_PLACED.BILL_AMOUNT DESC
LIMIT 3;
/* 3. Display all the Orders which are placed more than 10 days old
and one or more items from those orders are still not shipped.*/
SELECT order_placed.Date_of_order,order_placed.Order_id,Order_details.Product_id,product.Name,Order_details.Order_status
FROM PRODUCT
LEFT JOIN Order_details
ON Order_details.Product_id=product.Product_id
LEFT JOIN order_placed
ON order_placed.Order_id=Order_details.Order_id
WHERE Order_details.Order_status="PLACED" AND order_placed.Date_of_order<DATE_SUB(now(), INTERVAL 10 DAY)
/* 4.Display list of shoppers which haven't ordered anything since last month.*/
/* 5. Display list of shopper along with orders placed by them in last 15 days. */
SELECT U.FIRST_NAME,P.NAME, O.DATE_OF_ORDER
FROM USER U
LEFT JOIN ORDER_PLACED O
ON O.USER_ID=U.USER_ID
LEFT JOIN ORDER_DETAILS OD
ON OD.ORDER_ID=O.ORDER_ID
LEFT JOIN PRODUCT P
ON OD.PRODUCT_ID=P.PRODUCT_ID
WHERE O.DATE_OF_ORDER >DATE_SUB(now(), INTERVAL 15 DAY) ;
/* 6. Display list of order items which are in “shipped” state for particular Order Id (i.e.: 8))*/
SELECT P.NAME,OD.QUANTITY, OD.ORDER_ID
FROM PRODUCT P
LEFT JOIN ORDER_DETAILS OD
ON P.PRODUCT_ID=OD.Product_id
WHERE OD.ORDER_STATUS ="SHIPPED" AND OD.Order_id=8;
/* 7. Display list of order items along with order placed date which fall between Rs 50 to Rs 250 price.*/
SELECT P.NAME, OP.DATE_OF_ORDER
FROM PRODUCT P
LEFT JOIN order_details OD
ON OD.Product_id=P.Product_id
LEFT JOIN order_placed OP
ON OD.Order_id=OP.Order_id
WHERE OD.PRICE>200 AND OD.PRICE<400;
/* 8. Update first 20 Order items status to “Shipped” which are placed today.*/
#WRONG
UPDATE ORDER_DETAILS O
LEFT JOIN ORDER_PLACED OP
ON OP.ORDER_ID=O.ORDER_ID
SET O.ORDER_STATUS="SHPPED"
WHERE OP.DATE_OF_ORDER ='2018-8-17'
LIMIT 3;
|
USE db_book
/*Books Table */
CREATE TABLE tbl_Book (
book_id INT PRIMARY KEY,
book_title VARCHAR(50) NOT NULL,
book_publishername VARCHAR(50) NOT NULL
);
INSERT INTO tbl_Book
(book_id, book_title, book_publishername)
VALUES
('1', 'The Lost Tribe', 'Weekly'),
('2', 'Good Life', 'Pinguin'),
('3', 'Deschutes', 'Simon & Schuster'),
('4', 'Send', 'Random House of Canada'),
('5', 'Koffmann', 'Pinguin'),
('6', 'Biking', 'Simon & Schuster'),
('7', 'End of Watch', 'Pinguin'),
('8', 'Soccer', 'Random House of Canada'),
('9', 'Life of Pi', 'Random House of Canada'),
('10', 'Barcelona', 'Weekly'),
('11', 'Rebel of the Sand', 'Weekly'),
('12', 'Gordo', 'Pinguin'),
('13', 'Eileen', 'Random House of Canada'),
('14', 'Moving', 'Simon & Schuster'),
('15', 'Fishing', 'Simon & Schuster'),
('16', 'Flash FIre', 'Weekly'),
('17', 'Boneyard', 'Weekly'),
('18', 'Milk Made', 'Hachette'),
('19', 'Apollo', 'Hachette Book'),
('20', 'Space', 'Hachette')
;
SELECT * FROM tbl_Book
/* END BOOK TABLE*/
/* BOOK AUTHORS*/
CREATE TABLE tbl_Bookauthor (
aurthur_bookid INT PRIMARY KEY,
aurthur_name VARCHAR(50) NOT NULL
);
INSERT INTO tbl_Bookauthor
(aurthur_bookid, aurthur_name)
VALUES
('1', 'Stephen King'),
('2', 'Juan Mata'),
('3', 'Raul Jimenez'),
('4', 'Rafa Marquez'),
('5', 'Alberto James'),
('6', 'Cody Smith'),
('7', 'Bruce Brown'),
('8', 'Pete Parker'),
('9', 'Dan Johnson'),
('10', 'Morgan Stanley'),
('11', 'Michael Scott'),
('12', 'Dylan Jones'),
('13', 'Allen Tylor'),
('14', 'Sue Miller'),
('15', 'Adres Perez'),
('16', 'Jacob Gibbson'),
('17', 'Debbie WIlliams'),
('18', 'Alex Moore'),
('19', 'Mark Jackson'),
('20', 'Jennifer Garcia')
;
SELECT * FROM tbl_Bookauthor
/* END BOOK AUTHORS*/
/*BOOK PUBLISHERS*/
CREATE TABLE tbl_Publisher (
publisher_name VARCHAR (50) PRIMARY KEY,
publisher_address VARCHAR(50) NULL,
publisher_phone VARCHAR(50) NULL
);
INSERT INTO tbl_Publisher
(publisher_name, publisher_address, publisher_phone)
VALUES
('Red', '12 S Elm St Madras, OR 82732', '511-222-3333'),
('Simon & Schuster', '1202 SW Evergreen Ave Madras, OR 82732','511-567-1234'),
('Random House of Canada', '76784 Chivas St La Pine, OR 28981', '511-321-7823'),
('Pinguin', '117 Soccer St La Pine, OR 28981', '435-722-1730'),
('Hachette Book', '555 SW Shevlin Scranton, PA 45392', '345-221-6342')
;
SELECT * FROM tbl_Publisher
/*END BOOK PUBLISHERS*/
/*BOOK LOANS*/
CREATE TABLE tbl_Bookloans (
loans_bookid INT NOT NULL,
loans_branchid INT NOT NULL,
loans_cardno INT NOT NULL,
loans_dateout VARCHAR(50) NOT NULL,
loans_duedate VARCHAR(50) NOT NULL
CONSTRAINT pk_Bookloans PRIMARY KEY (loans_bookid, loans_branchid, loans_cardno)
);
INSERT INTO tbl_Bookloans
(loans_bookid, loans_branchid, loans_cardno, loans_dateout, loans_duedate)
VALUES
('2', '1', '12345', '7-16-2017', '7-23-2017'),
('4', '1', '12345', '7-16-2017', '7-23-2017'),
('6', '1', '12345', '7-16-2017', '7-20-2017'),
('8', '1', '12345', '7-16-2017', '7-23-2017'),
('10', '1', '12345', '7-16-2017', '7-23-2017'),
('12', '1', '12345', '7-16-2017', '7-23-2017'),
('14', '3', '26192', '7-14-2017', '7-21-2017'),
('16', '3', '26192', '7-14-2017', '7-21-2017'),
('18', '3', '26192', '7-14-2017', '7-21-2017'),
('20', '3', '26192', '7-14-2017', '7-20-2017'),
('1', '3', '26192', '7-14-2017', '7-21-2017'),
('3', '3', '26192', '7-14-2017', '7-20-2017'),
('5', '2', '35781', '7-15-2017', '7-22-2017'),
('7', '2', '35781', '7-15-2017', '7-22-2017'),
('9', '4', '87399', '7-16-2017', '7-23-2017'),
('11', '4', '87399', '7-16-2017', '7-20-2017'),
('13', '5', '38293', '7-16-2017', '7-23-2017'),
('15', '5', '38293', '7-16-2017', '7-23-2017'),
('17', '5', '38293', '7-16-2017', '7-20-2017'),
('19', '5', '38293', '7-16-2017', '7-20-2017'),
('10', '1', '65432', '7-16-2017', '7-23-2017'),
('12', '1', '65432', '7-16-2017', '7-23-2017'),
('14', '1', '65432', '7-14-2017', '7-21-2017'),
('16', '3', '77221', '7-14-2017', '7-21-2017'),
('18', '3', '77221', '7-14-2017', '7-21-2017'),
('20', '3', '77221', '7-14-2017', '7-21-2017'),
('1', '3', '77221', '7-14-2017', '7-21-2017'),
('3', '3', '77221', '7-14-2017', '7-21-2017'),
('5', '2', '81976', '7-15-2017', '7-20-2017'),
('7', '2', '81976', '7-15-2017', '7-20-2017'),
('10', '2', '81976', '7-16-2017', '7-23-2017'),
('11', '2', '81976', '7-16-2017', '7-23-2017'),
('8', '2', '81976', '7-15-2017', '7-20-2017'),
('9', '2', '81976', '7-16-2017', '7-20-2017'),
('12', '4', '87399', '7-16-2017', '7-23-2017'),
('13', '1', '92349', '7-16-2017', '7-23-2017'),
('15', '1', '92349', '7-16-2017', '7-23-2017'),
('17', '1', '92349', '7-16-2017', '7-23-2017'),
('19', '1', '92349', '7-16-2017', '7-23-2017'),
('10', '1', '92349', '7-16-2017', '7-23-2017'),
('12', '1', '92349', '7-16-2017', '7-23-2017'),
('14', '3', '10984', '7-14-2017', '7-21-2017'),
('16', '3', '10984', '7-14-2017', '7-21-2017'),
('18', '3', '10984', '7-14-2017', '7-21-2017'),
('20', '3', '10984', '7-14-2017', '7-21-2017'),
('1', '3', '10984', '7-14-2017', '7-21-2017'),
('3', '3', '10984', '7-14-2017', '7-21-2017'),
('5', '4', '11223', '7-15-2017', '7-22-2017'),
('7', '4', '11223', '7-15-2017', '7-22-2017'),
('9', '4', '11223', '7-16-2017', '7-23-2017')
;
SELECT * FROM tbl_Bookloans
/*END BOOK LOANS*/
/*BOOK COPIES*/
CREATE TABLE tbl_Bookcopies (
copies_bookid INT,
copies_branchid INT NOT NULL,
copies_noofcopies VARCHAR NULL
CONSTRAINT pk_Bookcopies PRIMARY KEY (copies_bookid, copies_branchid)
);
INSERT INTO tbl_Bookcopies
(copies_bookid, copies_branchid, copies_noofcopies)
VALUES
('1', '1', '3'),
('3', '1', '3'),
('5', '1', '3'),
('7', '1', '3'),
('9', '1', '3'),
('11', '1', '3'),
('13', '1', '5'),
('15', '1', '2'),
('17', '1', '4'),
('19', '1', '4'),
('2', '2', '2'),
('4', '2', '2'),
('6', '2', '2'),
('8', '2', '3'),
('1', '2', '3'),
('3', '2', '3'),
('5', '2', '3'),
('7', '2', '3'),
('9', '2', '3'),
('11', '2', '3'),
('13', '3', '5'),
('15', '3', '2'),
('17', '3', '4'),
('19', '3', '4'),
('1', '3', '3'),
('2', '3', '2'),
('4', '3', '2'),
('6', '3', '2'),
('8', '3', '3'),
('10', '3', '4'),
('12', '3', '4'),
('1', '4', '4'),
('3', '4', '5'),
('5', '4', '5'),
('7', '4', '3'),
('9', '4', '3'),
('11', '4', '3'),
('13', '4', '5'),
('15', '4', '2'),
('17', '4', '4'),
('19', '4', '4'),
('2', '5', '5'),
('4', '5', '5'),
('6', '5', '5'),
('8', '5', '5'),
('1', '5', '2'),
('3', '5', '2'),
('5', '5', '2'),
('7', '5', '2'),
('9', '5', '3'),
('11', '5', '3')
;
SELECT * FROM tbl_Bookcopies
/*END BOOK COPIES*/
/*BORROWERS*/
CREATE TABLE tbl_Borrower (
borrower_cardno INT PRIMARY KEY NOT NULL,
borrower_name VARCHAR(50) NOT NULL,
borrower_address VARCHAR(50) NOT NULL,
borrower_phone VARCHAR(50) NOT NULL
);
INSERT INTO tbl_Borrower
(borrower_cardno, borrower_name, borrower_address, borrower_phone)
VALUES
('99999', 'Joe Brown', '234 W 48th St Bend, OR 97702', '777-777-7777'),
('12345', 'John Smith', '333 2nd St Bend, OR 97702', '444-222-3333'),
('26192', 'Carol Jones', '799 Harrison ST Redmond, OR 97756', '231-857-9382'),
('35781', 'Christopher Muller', '223 Jackson St Portland, OR 97203', '536-849-1236'),
('87399', 'Roberto Carlos', '556 6th St Prineville, OR 34214', '675-822-3218'),
('38293', 'Kevin Allen', '884 California St Redmond, OR 97756', '243-857-4892'),
('65432', 'Ramon Silvester', '405 Holms Ave Bend, OR 97702', '284-890-3432'),
('77221', 'Frank Walker', '622 Hemlock St Redmond, OR 97756', '547-325-2495'),
('81976', 'Bret Scott', '992 18th St Portland, OR 97203', '537-452-5356'),
('92349', 'Eric Cortez', '294 Columbia St Bend, OR 97702', '302-421-9040'),
('10984', 'Andres Garza', '890 Canal St Redmond, OR 97756', '826-478-3322'),
('11223', 'Jaime Sanchez', '111 2nd St Prineville, OR 34214', '683-321-1111')
;
SELECT * FROM tbl_Borrower
/*END BORROWERS*/
/*LIBRARY BRANCH*/
CREATE TABLE tbl_Librarybranch (
branch_branchid VARCHAR (50) PRIMARY KEY,
branch_branchname VARCHAR(50) NOT NULL,
branch_address VARCHAR(50) NOT NULL
);
INSERT INTO tbl_Librarybranch
(branch_branchid, branch_branchname, branch_address)
VALUES
('1', 'Central', '1771 Jefferson St Bend, OR 97702'),
('2', 'Sharpstown', '4732 Couch St Portland, OR 97203'),
('3', 'Lincoln', '2932 17th St Redmond, OR 97756'),
('4', 'Deschutes', '9921 Main St Prineville, OR 34214'),
('5', 'Mazama', '3812 Salmon Ave Redmond, OR 97756')
;
SELECT * FROM tbl_Librarybranch
/*END LIBRARY BRANCH*/
/*DRILL 1 */
SELECT A.book_title AS 'Title', B.copies_noofcopies AS 'Copies', C.branch_branchname AS 'Branch'
FROM tbl_Book AS a
INNER JOIN tbl_Bookcopies b ON a.book_id = b.copies_bookid
INNER JOIN tbl_Librarybranch c ON b.copies_branchid = c.branch_branchid
WHERE a.book_title = 'The Lost Tribe' AND c.branch_branchname = 'Sharpstown'
/* END DRILL 1 */
/*DRILL 2 */
SELECT A.book_title AS 'Title', B.copies_noofcopies AS 'Copies', C.branch_branchname AS 'Branch'
FROM tbl_Book AS a
INNER JOIN tbl_Bookcopies b ON a.book_id = b.copies_bookid
INNER JOIN tbl_Librarybranch c ON b.copies_branchid = c.branch_branchid
WHERE a.book_title = 'The Lost Tribe'
/*END DRILL 2*/
/*DRILL 3*/
SELECT * FROM tbl_Borrower AS BR
FULL OUTER JOIN tbl_Bookloans BL ON BR.borrower_cardno = BL.loans_cardno
WHERE BL.loans_cardno IS NULL
/*END DRILL 3*/
/*DRILL 4*/
SELECT A.book_title AS 'Title', C.borrower_name AS 'Name', C.borrower_address AS 'Address'
FROM tbl_Bookloans AS B
INNER JOIN tbl_Borrower C ON B.loans_cardno = C.borrower_cardno
INNER JOIN tbl_Book A ON B.loans_bookid = A.book_id
WHERE B.loans_branchid = 2 AND B.loans_duedate = '7-20-2017'
/*END DRILL 4*/
/*DRILL 5*/
SELECT DISTINCT B.branch_branchname AS 'Branch', COUNT(L.loans_branchid) AS Quantity
FROM tbl_Librarybranch B
INNER JOIN tbl_Bookloans L ON B.branch_branchid = L.loans_branchid
GROUP BY B.branch_branchname, L.loans_branchid
/*END DRILL 5*/
/*DRILL 6*/
SELECT B.borrower_name AS 'Borrower', B.borrower_address AS 'Address', COUNT(L.loans_cardno) AS Quantity
FROM tbl_Borrower B
INNER JOIN tbl_Bookloans L ON B.borrower_cardno = L.loans_cardno
GROUP BY B.borrower_name, B.borrower_address
HAVING COUNT(L.loans_cardno) > 5;
/*END DRILL 6*/
/*DRILL 7*/
SELECT A.book_title, B.branch_branchname, C.copies_noofcopies
FROM tbl_Book AS A
INNER JOIN tbl_Bookauthor D ON A.book_id = D.aurthur_bookid
INNER JOIN tbl_Bookcopies C ON A.book_id = C.copies_bookid
INNER JOIN tbl_Librarybranch B ON C.copies_branchid = B.branch_branchid
WHERE D.aurthur_name = 'Stephen King' AND B.branch_branchname = 'Central'
/*END DRILL 7*/ |
-- W3C Parser
create transform function w3cLogParser
as language 'C++' name 'w3cLogParserFactory' library w3cLogParser;
CREATE TABLE raw_w3c_logs (id AUTO_INCREMENT, data VARCHAR(4096), filename VARCHAR(1024));
COPY raw_w3c_logs (
data,
filename as 'w3c.log'
)
FROM STDIN DELIMITER '|';
#Fields: date time c-ip s-sitename s-ip s-port cs-uri-stem cs-uri-query sc-status
2011-10-29 17:35:56 192.168.50.20 W3SVC1 192.168.50.20 80 /exchange/joedoe@example.com/NON_IPM_SUBTREE/Microsoft-Server-ActiveSync/iPad/ApplGB022BTTZ38 - 302
2011-10-29 17:35:56 192.168.50.20 W3SVC1 192.168.50.20 80 /exchange/joedoe@example.com/NON_IPM_SUBTREE/Microsoft-Server-ActiveSync/iPad/ApplGB022BTTZ38/AutdState.xml - 200
2011-10-29 17:35:56 192.168.50.20 W3SVC1 192.168.50.20 80 /exchange/joedoe@example.com/NON_IPM_SUBTREE/Microsoft-Server-ActiveSync/iPad/ApplGB022BTTZ38/FolderSyncFile - 200
#Fields: date time s-sitename s-ip cs-method cs-uri-stem cs-uri-query s-port cs-username c-ip cs(User-Agent) sc-status sc-substatus sc-win32-status
2011-10-29 17:35:56 W3SVC1 192.168.50.20 GET /exchange/joedoe@example.com/NON_IPM_SUBTREE/Microsoft-Server-ActiveSync/iPad/ApplGB022BTTZ38 - 80 MYCORPjoedoe 192.168.50.20 Microsoft-Server-ActiveSync/6.5.7653.5 302 0 0
2011-10-29 17:35:56 W3SVC1 192.168.50.20 GET /exchange/joedoe@example.com/NON_IPM_SUBTREE/Microsoft-Server-ActiveSync/iPad/ApplGB022BTTZ38/AutdState.xml - 80 MYCORPjoedoe 192.168.50.20 Microsoft-Server-ActiveSync/6.5.7653.5 200 0 0
2011-10-29 17:35:56 W3SVC1 192.168.50.20 GET /exchange/joedoe@example.com/NON_IPM_SUBTREE/Microsoft-Server-ActiveSync/iPad/ApplGB022BTTZ38/FolderSyncFile - 80 MYCORPjoedoe 192.168.50.20 Microsoft-Server-ActiveSync/6.5.7653.5 200 0 0
#Fields: date time c-ip s-sitename s-ip s-port cs-uri-stem cs-uri-query sc-status
2011-10-29 17:35:56 192.168.50.20 W3SVC1 192.168.50.20 80 /exchange/joedoe@example.com/NON_IPM_SUBTREE/Microsoft-Server-ActiveSync/iPad/ApplGB022BTTZ38 - 302
2011-10-29 17:35:56 192.168.50.20 W3SVC1 192.168.50.20 80 /exchange/joedoe@example.com/NON_IPM_SUBTREE/Microsoft-Server-ActiveSync/iPad/ApplGB022BTTZ38/AutdState.xml - 200
2011-10-29 17:35:56 192.168.50.20 W3SVC1 192.168.50.20 80 /exchange/joedoe@example.com/NON_IPM_SUBTREE/Microsoft-Server-ActiveSync/iPad/ApplGB022BTTZ38/FolderSyncFile - 200
\.
-- Invoke the UDT to parse each log line into
CREATE TABLE parsed_w3c_logs AS
SELECT *
FROM (SELECT w3cLogParser(data) OVER (PARTITION BY filename ORDER BY id)
FROM raw_w3c_logs) AS sq;
-- Show the parsed log lines
SELECT * FROM parsed_w3c_logs LIMIT 10;
SELECT date, c_ip, count(distinct(cs_user_agent))
FROM parsed_w3c_logs
GROUP BY date, c_ip
LIMIT 10;
DROP TABLE raw_w3c_logs;
DROP TABLE parsed_w3c_logs;
|
/*
Navicat MySQL Data Transfer
Source Server : mysql
Source Server Version : 50514
Source Host : localhost:3306
Source Database : odontologia
Target Server Type : MYSQL
Target Server Version : 50514
File Encoding : 65001
Date: 2011-08-18 21:32:23
*/
SET FOREIGN_KEY_CHECKS=0;
-- ----------------------------
-- Table structure for `procedimiento`
-- ----------------------------
DROP TABLE IF EXISTS `procedimiento`;
CREATE TABLE `procedimiento` (
`codigo` int(11) NOT NULL,
`descripcion` varchar(100) DEFAULT NULL,
`costo` float DEFAULT NULL,
PRIMARY KEY (`codigo`)
) ENGINE=InnoDB DEFAULT CHARSET=latin1;
-- ----------------------------
-- Records of procedimiento
-- ----------------------------
INSERT INTO `procedimiento` VALUES ('1', 'Limpieza Bucal', '600');
INSERT INTO `procedimiento` VALUES ('2', 'Tratamiento de canal', '4000');
INSERT INTO `procedimiento` VALUES ('3', 'Extraccion de pieza', '500');
INSERT INTO `procedimiento` VALUES ('4', 'Limpieza Profunda', '6000');
INSERT INTO `procedimiento` VALUES ('5', 'Ortodoncia', '4000');
|
with wsul as (
select
month_n, state_n,
sum(no_chld_svr_wasting) as svrly_wstd,
sum(no_mdrtly_wasted_chld) as mdrtly_wstd,
sum(no_svrly_stunted_chld) as svrly_stntd,
sum(no_mdrtly_stunted_chld) as mdrtly_stntd,
sum(no_svrly_uw_chld) as svrly_uw,
sum(no_mdrtly_uw_chld) as mdrtly_uw,
sum(no_nwborns_wid_lbw) as nb_lbw,
sum(total_no_chld_ht_msrd) as total_no_chld_ht_msrd,
sum(total_no_chld_ht_wt_msrd) as total_no_chld_ht_wt_msrd,
sum(total_no_chld_wgd) as total_no_chld_wgd,
sum(total_no_chld_born_wgd_in_mnth) as total_no_chld_born_wgd_in_mnth
from consolidated_child_ndj
group by
consolidated_child_ndj.month_n, consolidated_child_ndj.state_n
order by
consolidated_child_ndj.month_n,
consolidated_child_ndj.state_n)
select month_n, state_n, mdrtly_stntd,svrly_stntd, svrly_wstd, mdrtly_wstd, svrly_uw, mdrtly_uw,nb_lbw,
round(svrly_wstd + mdrtly_wstd) as wstd_chld,
round(svrly_stntd + mdrtly_stntd) as stntd_chld,
round(svrly_uw + mdrtly_uw) as uw_chld,
round(((svrly_stntd + mdrtly_stntd)/NULLIF(total_no_chld_ht_msrd,0))*100,2) as stunting_percent,
round(((svrly_wstd + mdrtly_wstd)/NULLIF(total_no_chld_ht_wt_msrd,0))*100,2) as wasting_percent,
round(((svrly_uw + mdrtly_uw)/NULLIF(total_no_chld_wgd,0))*100,2) as underweight_percent,
round((nb_lbw/NULLIF(total_no_chld_born_wgd_in_mnth,0))*100,2) as low_birth_weight_percent
from wsul;
|
Create procedure SP_Get_DandDDivisons @ID int
AS
BEGIN
Select Distinct CategoryID From DandDCategory where ID=@ID
END
|
CREATE TABLE d3_article (
id int(11) NOT NULL AUTO_INCREMENT,
author_name VARCHAR(50) NOT NULL,
title VARCHAR(50) NOT NULL,
text LONGTEXT,
source VARCHAR(200) NOT NULL UNIQUE,
date_of_publish DATE NOT NULL,
date_of_upload DATE NOT NULL
PRIMARY KEY (id)
);
CREATE TABLE d3_read (
id int(11) NOT NULL AUTO_INCREMENT,
d3_user_id int(11) NOT NULL,
d3_article_id int(11) NOT NULL,
date DATE NOT NULL,
PRIMARY KEY (id)
FOREIGN KEY (d3_user_id, d3_article_id)
); |
-- phpMyAdmin SQL Dump
-- version 4.7.7
-- https://www.phpmyadmin.net/
--
-- Хост: 127.0.0.1:3306
-- Время создания: Апр 10 2019 г., 12:54
-- Версия сервера: 5.6.38-log
-- Версия PHP: 7.2.0
SET SQL_MODE = "NO_AUTO_VALUE_ON_ZERO";
SET AUTOCOMMIT = 0;
START TRANSACTION;
SET time_zone = "+00:00";
/*!40101 SET @OLD_CHARACTER_SET_CLIENT=@@CHARACTER_SET_CLIENT */;
/*!40101 SET @OLD_CHARACTER_SET_RESULTS=@@CHARACTER_SET_RESULTS */;
/*!40101 SET @OLD_COLLATION_CONNECTION=@@COLLATION_CONNECTION */;
/*!40101 SET NAMES utf8mb4 */;
--
-- База данных: `instagram`
--
-- --------------------------------------------------------
--
-- Структура таблицы `action_users`
--
CREATE TABLE `action_users` (
`id` int(11) NOT NULL,
`action_user` int(11) NOT NULL,
`action` set('subscribe_user','like_publication','like_comment','add_comment') NOT NULL,
`object` int(11) NOT NULL,
`more` int(11) DEFAULT NULL COMMENT 'id объекта с которым произошло действие. Если подписались будет null.',
`checked` tinyint(1) NOT NULL DEFAULT '0',
`action_date` datetime NOT NULL DEFAULT CURRENT_TIMESTAMP
) ENGINE=InnoDB DEFAULT CHARSET=utf8;
--
-- Дамп данных таблицы `action_users`
--
INSERT INTO `action_users` (`id`, `action_user`, `action`, `object`, `more`, `checked`, `action_date`) VALUES
(2, 63, 'subscribe_user', 66, NULL, 0, '2019-04-10 11:28:02'),
(3, 63, 'subscribe_user', 68, NULL, 0, '2019-04-10 11:28:05'),
(4, 63, 'subscribe_user', 71, NULL, 0, '2019-04-10 11:28:09'),
(5, 63, 'subscribe_user', 72, NULL, 1, '2019-04-10 11:28:10'),
(6, 63, 'subscribe_user', 73, NULL, 1, '2019-04-10 11:28:11'),
(7, 63, 'subscribe_user', 53, NULL, 0, '2019-04-10 11:28:16'),
(8, 71, 'subscribe_user', 53, NULL, 0, '2019-04-10 11:28:35'),
(9, 71, 'subscribe_user', 72, NULL, 1, '2019-04-10 11:28:37'),
(10, 71, 'subscribe_user', 68, NULL, 0, '2019-04-10 11:28:39'),
(11, 71, 'subscribe_user', 67, NULL, 0, '2019-04-10 11:28:42'),
(12, 71, 'subscribe_user', 70, NULL, 0, '2019-04-10 11:28:47'),
(13, 69, 'subscribe_user', 68, NULL, 0, '2019-04-10 11:29:07'),
(14, 69, 'subscribe_user', 72, NULL, 1, '2019-04-10 11:29:09'),
(15, 69, 'subscribe_user', 67, NULL, 0, '2019-04-10 11:29:10'),
(16, 69, 'subscribe_user', 71, NULL, 0, '2019-04-10 11:29:14'),
(17, 70, 'subscribe_user', 68, NULL, 0, '2019-04-10 11:29:30'),
(18, 70, 'subscribe_user', 72, NULL, 1, '2019-04-10 11:29:32'),
(19, 70, 'subscribe_user', 67, NULL, 0, '2019-04-10 11:29:34'),
(20, 70, 'subscribe_user', 71, NULL, 0, '2019-04-10 11:29:35'),
(21, 70, 'subscribe_user', 69, NULL, 0, '2019-04-10 11:29:38'),
(22, 67, 'subscribe_user', 68, NULL, 0, '2019-04-10 11:29:55'),
(23, 67, 'subscribe_user', 72, NULL, 1, '2019-04-10 11:29:56'),
(24, 67, 'subscribe_user', 69, NULL, 0, '2019-04-10 11:29:57'),
(25, 67, 'subscribe_user', 71, NULL, 0, '2019-04-10 11:30:01'),
(26, 73, 'subscribe_user', 68, NULL, 0, '2019-04-10 11:30:17'),
(27, 73, 'subscribe_user', 72, NULL, 1, '2019-04-10 11:30:17'),
(28, 73, 'subscribe_user', 53, NULL, 0, '2019-04-10 11:30:19'),
(29, 73, 'subscribe_user', 64, NULL, 0, '2019-04-10 11:30:21'),
(30, 73, 'subscribe_user', 65, NULL, 0, '2019-04-10 11:30:22'),
(31, 73, 'subscribe_user', 70, NULL, 0, '2019-04-10 11:30:24'),
(32, 73, 'subscribe_user', 63, NULL, 1, '2019-04-10 11:30:26'),
(33, 73, 'subscribe_user', 44, NULL, 0, '2019-04-10 11:30:27'),
(34, 68, 'subscribe_user', 72, NULL, 0, '2019-04-10 11:35:10'),
(35, 68, 'subscribe_user', 71, NULL, 0, '2019-04-10 11:35:11'),
(36, 68, 'subscribe_user', 67, NULL, 0, '2019-04-10 11:35:12'),
(37, 68, 'subscribe_user', 69, NULL, 0, '2019-04-10 11:35:14'),
(38, 68, 'subscribe_user', 63, NULL, 1, '2019-04-10 11:35:18'),
(39, 74, 'subscribe_user', 72, NULL, 0, '2019-04-10 11:41:40'),
(40, 74, 'subscribe_user', 71, NULL, 0, '2019-04-10 11:41:42'),
(41, 74, 'subscribe_user', 67, NULL, 0, '2019-04-10 11:41:42'),
(42, 74, 'subscribe_user', 68, NULL, 0, '2019-04-10 11:41:44'),
(43, 74, 'subscribe_user', 69, NULL, 0, '2019-04-10 11:41:45'),
(44, 74, 'subscribe_user', 73, NULL, 0, '2019-04-10 11:41:48'),
(45, 72, 'subscribe_user', 68, NULL, 0, '2019-04-10 11:43:42'),
(46, 72, 'subscribe_user', 69, NULL, 0, '2019-04-10 11:43:43'),
(47, 72, 'subscribe_user', 67, NULL, 0, '2019-04-10 11:43:45'),
(48, 72, 'subscribe_user', 70, NULL, 0, '2019-04-10 11:43:46'),
(49, 72, 'subscribe_user', 63, NULL, 1, '2019-04-10 11:43:49'),
(50, 63, 'subscribe_user', 69, NULL, 0, '2019-04-10 12:01:11'),
(51, 63, 'add_comment', 68, 150, 0, '2019-04-10 12:22:52'),
(52, 63, 'add_comment', 68, 151, 0, '2019-04-10 12:23:05'),
(53, 63, 'add_comment', 68, 152, 0, '2019-04-10 12:23:19'),
(54, 63, 'add_comment', 68, 153, 0, '2019-04-10 12:23:31'),
(55, 63, 'add_comment', 69, 154, 0, '2019-04-10 12:23:40'),
(56, 63, 'add_comment', 71, 155, 0, '2019-04-10 12:23:51'),
(57, 63, 'add_comment', 71, 156, 0, '2019-04-10 12:24:02'),
(58, 63, 'add_comment', 73, 157, 0, '2019-04-10 12:24:24'),
(59, 63, 'add_comment', 72, 158, 0, '2019-04-10 12:24:47'),
(60, 68, 'add_comment', 67, 159, 0, '2019-04-10 12:29:53'),
(61, 68, 'add_comment', 67, 160, 0, '2019-04-10 12:30:00'),
(62, 68, 'add_comment', 67, 161, 0, '2019-04-10 12:30:06'),
(63, 68, 'add_comment', 69, 162, 0, '2019-04-10 12:30:20'),
(64, 68, 'like_comment', 63, 152, 1, '2019-04-10 12:30:47'),
(65, 68, 'like_comment', 63, 151, 1, '2019-04-10 12:30:49'),
(66, 67, 'add_comment', 68, 163, 0, '2019-04-10 12:31:13'),
(67, 67, 'add_comment', 68, 164, 0, '2019-04-10 12:31:28'),
(68, 67, 'like_comment', 63, 151, 1, '2019-04-10 12:31:30'),
(69, 67, 'add_comment', 68, 165, 0, '2019-04-10 12:31:38'),
(70, 67, 'like_comment', 63, 152, 1, '2019-04-10 12:31:39'),
(71, 67, 'add_comment', 68, 166, 0, '2019-04-10 12:31:57'),
(72, 67, 'add_comment', 69, 167, 0, '2019-04-10 12:32:18'),
(73, 67, 'add_comment', 69, 168, 0, '2019-04-10 12:32:40'),
(74, 67, 'add_comment', 71, 169, 0, '2019-04-10 12:32:55'),
(75, 69, 'like_comment', 67, 163, 0, '2019-04-10 12:33:12'),
(76, 69, 'add_comment', 68, 170, 0, '2019-04-10 12:33:24'),
(77, 69, 'like_comment', 67, 164, 0, '2019-04-10 12:33:32'),
(78, 69, 'add_comment', 68, 171, 0, '2019-04-10 12:33:51'),
(79, 69, 'add_comment', 68, 172, 0, '2019-04-10 12:34:22'),
(80, 69, 'like_comment', 67, 166, 0, '2019-04-10 12:34:26'),
(81, 69, 'add_comment', 67, 173, 0, '2019-04-10 12:34:50'),
(82, 69, 'like_comment', 68, 159, 0, '2019-04-10 12:34:54'),
(83, 69, 'add_comment', 67, 174, 0, '2019-04-10 12:35:17'),
(84, 69, 'like_comment', 67, 169, 0, '2019-04-10 12:35:24'),
(85, 69, 'add_comment', 72, 175, 0, '2019-04-10 12:35:40'),
(86, 69, 'like_comment', 63, 158, 1, '2019-04-10 12:35:43'),
(87, 70, 'like_comment', 69, 170, 0, '2019-04-10 12:36:07'),
(88, 70, 'like_comment', 67, 163, 0, '2019-04-10 12:36:08'),
(89, 70, 'add_comment', 68, 176, 0, '2019-04-10 12:36:18'),
(90, 70, 'add_comment', 68, 177, 0, '2019-04-10 12:36:43'),
(91, 70, 'like_comment', 63, 151, 1, '2019-04-10 12:36:45'),
(92, 70, 'add_comment', 68, 178, 0, '2019-04-10 12:36:58'),
(93, 70, 'like_comment', 68, 160, 0, '2019-04-10 12:37:10'),
(94, 70, 'like_comment', 68, 162, 0, '2019-04-10 12:37:14'),
(95, 70, 'like_comment', 69, 175, 0, '2019-04-10 12:37:28'),
(96, 71, 'add_comment', 68, 179, 0, '2019-04-10 12:38:04'),
(97, 71, 'like_comment', 70, 176, 0, '2019-04-10 12:38:06'),
(98, 71, 'add_comment', 68, 180, 0, '2019-04-10 12:38:17'),
(99, 71, 'like_comment', 67, 166, 0, '2019-04-10 12:38:28'),
(100, 71, 'like_comment', 63, 153, 1, '2019-04-10 12:38:29'),
(101, 71, 'like_comment', 69, 173, 0, '2019-04-10 12:38:33'),
(102, 71, 'add_comment', 67, 181, 0, '2019-04-10 12:38:46'),
(103, 71, 'like_comment', 68, 161, 0, '2019-04-10 12:38:53'),
(104, 72, 'add_comment', 63, 182, 1, '2019-04-10 12:39:33'),
(105, 72, 'add_comment', 68, 183, 0, '2019-04-10 12:39:51'),
(106, 72, 'like_comment', 71, 179, 0, '2019-04-10 12:39:56'),
(107, 72, 'like_comment', 69, 170, 0, '2019-04-10 12:39:58'),
(108, 72, 'like_comment', 67, 163, 0, '2019-04-10 12:40:00'),
(109, 72, 'like_comment', 70, 177, 0, '2019-04-10 12:40:05'),
(110, 72, 'add_comment', 68, 184, 0, '2019-04-10 12:40:08'),
(111, 73, 'add_comment', 63, 185, 1, '2019-04-10 12:41:09'),
(112, 73, 'add_comment', 63, 186, 1, '2019-04-10 12:41:17'),
(113, 73, 'add_comment', 72, 187, 0, '2019-04-10 12:41:42'),
(114, 74, 'like_comment', 71, 179, 0, '2019-04-10 12:42:09'),
(115, 74, 'like_comment', 72, 183, 0, '2019-04-10 12:42:09'),
(116, 74, 'like_comment', 63, 154, 1, '2019-04-10 12:42:19'),
(117, 74, 'like_comment', 67, 167, 0, '2019-04-10 12:42:20'),
(118, 74, 'add_comment', 69, 188, 0, '2019-04-10 12:42:24'),
(119, 74, 'subscribe_user', 63, NULL, 1, '2019-04-10 12:42:39'),
(121, 63, 'like_comment', 73, 185, 0, '2019-04-10 12:52:50');
-- --------------------------------------------------------
--
-- Структура таблицы `comments`
--
CREATE TABLE `comments` (
`id` int(11) NOT NULL,
`parent_id_user` int(11) NOT NULL,
`parent_id_publication` int(11) NOT NULL,
`comment` text NOT NULL,
`likes` int(11) NOT NULL DEFAULT '0',
`pub_date` timestamp NOT NULL DEFAULT CURRENT_TIMESTAMP
) ENGINE=InnoDB DEFAULT CHARSET=utf8;
--
-- Дамп данных таблицы `comments`
--
INSERT INTO `comments` (`id`, `parent_id_user`, `parent_id_publication`, `comment`, `likes`, `pub_date`) VALUES
(150, 63, 325, 'прикольная киса, бро)', 0, '2019-04-10 09:22:52'),
(151, 63, 324, 'пиздатая дача', 3, '2019-04-10 09:23:05'),
(152, 63, 323, 'листочки заплакали?', 2, '2019-04-10 09:23:19'),
(153, 63, 321, 'чтоб я так жил', 1, '2019-04-10 09:23:31'),
(154, 63, 315, 'буль буль', 1, '2019-04-10 09:23:40'),
(155, 63, 310, 'круто', 0, '2019-04-10 09:23:51'),
(156, 63, 309, 'люблю космос', 0, '2019-04-10 09:24:02'),
(157, 63, 305, 'как всегда пиздат', 1, '2019-04-10 09:24:24'),
(158, 63, 300, 'night bro', 1, '2019-04-10 09:24:47'),
(159, 68, 319, 'good', 1, '2019-04-10 09:29:53'),
(160, 68, 318, 'nice cat', 1, '2019-04-10 09:30:00'),
(161, 68, 317, 'wow', 1, '2019-04-10 09:30:06'),
(162, 68, 315, 'nice fish', 1, '2019-04-10 09:30:20'),
(163, 67, 325, 'круто', 3, '2019-04-10 09:31:13'),
(164, 67, 324, 'полностью согласен', 1, '2019-04-10 09:31:28'),
(165, 67, 323, 'походу', 0, '2019-04-10 09:31:38'),
(166, 67, 321, 'я так и живу, лол', 3, '2019-04-10 09:31:57'),
(167, 67, 315, 'дайвер епта', 1, '2019-04-10 09:32:18'),
(168, 67, 313, 'красиво', 0, '2019-04-10 09:32:40'),
(169, 67, 309, 'очень красиво', 1, '2019-04-10 09:32:55'),
(170, 69, 325, 'очень мило', 2, '2019-04-10 09:33:24'),
(171, 69, 324, 'мальчики, я к вам!!!', 0, '2019-04-10 09:33:51'),
(172, 69, 321, 'раян, кому я к тебе. жди', 0, '2019-04-10 09:34:22'),
(173, 69, 320, 'крутой коктейль. угостишь?)', 1, '2019-04-10 09:34:50'),
(174, 69, 316, 'у гослинга скопипастил чтоли?', 0, '2019-04-10 09:35:17'),
(175, 69, 300, 'sex', 1, '2019-04-10 09:35:40'),
(176, 70, 325, 'ваще зверь', 1, '2019-04-10 09:36:18'),
(177, 70, 324, 'ого, так много зеленого', 1, '2019-04-10 09:36:43'),
(178, 70, 323, 'люблю зеленый цвет', 0, '2019-04-10 09:36:58'),
(179, 71, 325, 'крутая фотка', 2, '2019-04-10 09:38:04'),
(180, 71, 324, 'очень красиво', 0, '2019-04-10 09:38:17'),
(181, 71, 320, 'я угощу, приезжай киса', 0, '2019-04-10 09:38:46'),
(182, 72, 336, 'bad boy', 0, '2019-04-10 09:39:33'),
(183, 72, 325, 'nice boy', 1, '2019-04-10 09:39:51'),
(184, 72, 324, 'wow', 0, '2019-04-10 09:40:08'),
(185, 73, 337, 'man', 1, '2019-04-10 09:41:09'),
(186, 73, 336, 'nice', 0, '2019-04-10 09:41:17'),
(187, 73, 300, 'мой пездюк. как ты бро?', 0, '2019-04-10 09:41:42'),
(188, 74, 315, 'круто', 0, '2019-04-10 09:42:24');
-- --------------------------------------------------------
--
-- Структура таблицы `hashtags`
--
CREATE TABLE `hashtags` (
`id` int(11) NOT NULL,
`parent_id_publication` int(11) NOT NULL,
`hashtag` text NOT NULL
) ENGINE=InnoDB DEFAULT CHARSET=utf8;
--
-- Дамп данных таблицы `hashtags`
--
INSERT INTO `hashtags` (`id`, `parent_id_publication`, `hashtag`) VALUES
(11, 297, '#fruit,#summer,#juce'),
(12, 298, '#цветы,#отдых,#лето'),
(13, 300, '#sexy_niger'),
(14, 301, '#вот_так_вот'),
(15, 302, '#отдых,#summer'),
(16, 303, '#вот_так_вот'),
(17, 305, '#вот_так_вот');
-- --------------------------------------------------------
--
-- Структура таблицы `likes_comments`
--
CREATE TABLE `likes_comments` (
`id_user` int(11) NOT NULL,
`id_comment` int(11) NOT NULL
) ENGINE=InnoDB DEFAULT CHARSET=utf8;
--
-- Дамп данных таблицы `likes_comments`
--
INSERT INTO `likes_comments` (`id_user`, `id_comment`) VALUES
(67, 151),
(68, 151),
(70, 151),
(67, 152),
(68, 152),
(71, 153),
(74, 154),
(63, 157),
(69, 158),
(69, 159),
(70, 160),
(71, 161),
(70, 162),
(69, 163),
(70, 163),
(72, 163),
(69, 164),
(67, 166),
(69, 166),
(71, 166),
(74, 167),
(69, 169),
(70, 170),
(72, 170),
(71, 173),
(70, 175),
(71, 176),
(72, 177),
(72, 179),
(74, 179),
(74, 183),
(63, 185);
-- --------------------------------------------------------
--
-- Структура таблицы `likes_publications`
--
CREATE TABLE `likes_publications` (
`user_id` int(11) NOT NULL,
`publication_id` int(11) NOT NULL
) ENGINE=InnoDB DEFAULT CHARSET=utf8;
--
-- Дамп данных таблицы `likes_publications`
--
INSERT INTO `likes_publications` (`user_id`, `publication_id`) VALUES
(69, 297),
(73, 297),
(69, 298),
(70, 298),
(73, 298),
(69, 299),
(69, 300),
(70, 300),
(71, 300),
(73, 300),
(63, 301),
(63, 303),
(68, 307),
(69, 307),
(68, 308),
(70, 308),
(68, 309),
(69, 309),
(67, 310),
(74, 310),
(68, 311),
(70, 311),
(67, 312),
(68, 312),
(69, 312),
(63, 313),
(67, 313),
(68, 313),
(63, 314),
(68, 314),
(70, 314),
(68, 315),
(70, 315),
(74, 315),
(68, 316),
(69, 316),
(74, 316),
(68, 317),
(71, 317),
(74, 317),
(70, 318),
(68, 319),
(69, 319),
(71, 319),
(69, 320),
(70, 320),
(71, 320),
(63, 321),
(67, 321),
(69, 321),
(70, 321),
(71, 321),
(71, 322),
(63, 323),
(67, 323),
(70, 323),
(71, 323),
(72, 323),
(67, 324),
(70, 324),
(71, 324),
(72, 324),
(74, 324),
(63, 325),
(67, 325),
(69, 325),
(70, 325),
(71, 325),
(72, 325),
(74, 325),
(72, 334),
(72, 336),
(68, 337),
(72, 337),
(73, 337),
(68, 338),
(72, 338),
(73, 338);
-- --------------------------------------------------------
--
-- Структура таблицы `mails`
--
CREATE TABLE `mails` (
`id` int(11) NOT NULL,
`parent_id` int(11) NOT NULL,
`mail` varchar(200) NOT NULL,
`check_news` tinyint(1) NOT NULL DEFAULT '0'
) ENGINE=InnoDB DEFAULT CHARSET=utf8;
--
-- Дамп данных таблицы `mails`
--
INSERT INTO `mails` (`id`, `parent_id`, `mail`, `check_news`) VALUES
(29, 44, 'evdokimov99@mail.ua', 0),
(38, 53, 'vlad.kunchenko@gmail.com', 0),
(48, 63, 'eduard.evdokimov@inbox.ru', 0),
(49, 64, 'mike@mail.com', 0),
(50, 65, 'angela@mail.com', 0),
(51, 66, 'bob@mail.com', 0),
(52, 67, 'jackson@mail.com', 0),
(53, 68, 'gosling@mail.com', 0),
(54, 69, 'Emma@mail.com', 0),
(55, 70, 'Jake_Gyllenhaal@mail.com', 0),
(56, 71, 'russell_crowe@mail.com', 0),
(57, 72, 'scarlett_johansson@mail.com', 0),
(58, 73, 'alexander_nevski@mail.com', 0),
(59, 74, 'JamesMcAvoy@mail.com', 0);
-- --------------------------------------------------------
--
-- Структура таблицы `publications`
--
CREATE TABLE `publications` (
`id` int(11) NOT NULL,
`public_id` varchar(12) NOT NULL,
`parent_id` int(11) NOT NULL,
`img` varchar(100) NOT NULL,
`title` text,
`pub_date` timestamp NOT NULL DEFAULT CURRENT_TIMESTAMP,
`likes` int(11) NOT NULL DEFAULT '0'
) ENGINE=InnoDB DEFAULT CHARSET=utf8;
--
-- Дамп данных таблицы `publications`
--
INSERT INTO `publications` (`id`, `public_id`, `parent_id`, `img`, `title`, `pub_date`, `likes`) VALUES
(297, '5bb1ac9bd7f8', 72, 'dedf02d678c4f1484a176a1bef90970a.jpeg', 'fruit)))', '2019-04-10 08:44:35', 2),
(298, 'b336e75a8f0d', 72, 'c0b8e076b81508d2bc617391c48235fe.jpeg', 'perfect цветы', '2019-04-10 08:45:51', 3),
(299, 'de44e8a650d3', 72, 'e7ae78f3cd3ff8556cf143cc5fd091ff.jpeg', NULL, '2019-04-10 08:46:12', 1),
(300, '64111e09ff7d', 72, '8d59e53cf7f319edd1b05371ccc438fb.jpeg', NULL, '2019-04-10 08:46:48', 4),
(301, 'faabd87cd74c', 73, 'b6b9fa0bc2fc28d53728f86a47bbbc0d.jpeg', 'мой пездюк', '2019-04-10 08:49:43', 1),
(302, '7c5221ea8b0b', 73, '8831f0367c162091b9a7587059f2050b.jpeg', 'чил с киской', '2019-04-10 08:50:21', 0),
(303, '3e805efab849', 73, '10c8607f0d30f97ce1915769bf99a2f2.jpeg', 'мой пездюк 2. Возвращение легенды', '2019-04-10 08:51:03', 1),
(304, '4f50d7da0c6f', 73, 'b7e713cb7be4feed22b7cd20cff46436.jpeg', 'night best body', '2019-04-10 08:51:47', 0),
(305, '431f05f2d603', 73, '902d20bdddbea0bd28d4f4cd90d0f43b.jpeg', NULL, '2019-04-10 08:52:10', 0),
(306, '075c0ed828dd', 73, 'd1cc00d844e87aba74d6569800f6f561.jpeg', NULL, '2019-04-10 08:52:30', 0),
(307, '8d449534f165', 71, 'd3c013214606ed41f9a7b59dae9f1cee.jpeg', NULL, '2019-04-10 08:53:46', 2),
(308, '3cbd63c01692', 71, '2d90ea386646808e7295c20991f919da.jpeg', NULL, '2019-04-10 08:53:55', 2),
(309, 'dd5c6bf5fc3a', 71, '9420193395220477db3e786bdae2bcf9.jpeg', NULL, '2019-04-10 08:54:01', 2),
(310, 'b68bf92c3104', 71, 'f55e8b82eb7f9a18236590ab3e9a7e4d.jpeg', NULL, '2019-04-10 08:54:10', 2),
(311, '733e751d4bb9', 71, '45827201c289cc9f19aa6065745d9012.jpeg', NULL, '2019-04-10 08:57:07', 2),
(312, '586aca7ee5f7', 71, '132678f957b2da4788d30875349304be.jpeg', NULL, '2019-04-10 08:57:19', 3),
(313, 'f2f2319063ab', 69, 'aff600f6502d651a90d1c5b6d49eb5db.jpeg', NULL, '2019-04-10 08:57:52', 3),
(314, '2a24a139e431', 69, '091a8f82c9f047b02c6be28a4e54328d.jpeg', NULL, '2019-04-10 08:58:01', 3),
(315, '88a66e8aa786', 69, '0f4a529a0e22fc6b6478fb59279f4064.jpeg', 'ocean', '2019-04-10 08:58:19', 3),
(316, 'acfa2bce94f0', 67, '91f47c95b1c093c9be1e65e0251fc121.jpeg', NULL, '2019-04-10 08:59:17', 3),
(317, 'd7bdf52aea33', 67, '5e3558ba7c4660295cdfa20ac5784bb4.jpeg', NULL, '2019-04-10 08:59:24', 3),
(318, '58b22ab2f58c', 67, '7e4156b91791e60e820059214faf2ec0.jpeg', NULL, '2019-04-10 08:59:31', 1),
(319, 'c895d372ecf1', 67, '6b7fbf7242e80b808b751f9d9469e82a.jpeg', NULL, '2019-04-10 08:59:38', 3),
(320, 'd7f87af75c6b', 67, '804a77bdf04705a4a5c3d7cd39da6450.jpeg', NULL, '2019-04-10 08:59:46', 3),
(321, '069ac0973033', 68, '6cac93f3d7374e3c893b80c30b89a7f9.jpeg', NULL, '2019-04-10 09:00:13', 5),
(322, '387729a24fe5', 68, '88a8cfdfc66c2236b1a3c2a39b2d11c8.jpeg', NULL, '2019-04-10 09:00:21', 1),
(323, '3e20a8eac96b', 68, 'bd0ff22107e679c2477009c4c8675702.jpeg', NULL, '2019-04-10 09:00:26', 5),
(324, '9a88d10a33d1', 68, '4245fe94184143a1cfb91127e136d837.jpeg', NULL, '2019-04-10 09:00:32', 5),
(325, '121f7406e765', 68, '2bfaa57b056c8b786ddb2ed81c920397.jpeg', NULL, '2019-04-10 09:00:38', 7),
(326, '8262c135fa15', 63, 'b5befb4c7dbceac7851a751bf9250e0e.jpeg', NULL, '2019-04-10 09:25:47', 0),
(327, '6212ecdfe58e', 63, '61c638776011ea616a7129c0f33cc587.jpeg', NULL, '2019-04-10 09:27:24', 0),
(328, '0ccd973655c3', 63, 'c599f6e90de39fe307e0ce32d0c18fed.jpeg', NULL, '2019-04-10 09:27:27', 0),
(329, 'db9ab05d4e9f', 63, '7d69fa9023d2f6fdaaea688480700b78.jpeg', NULL, '2019-04-10 09:27:30', 0),
(330, 'd9ee6daba995', 63, '96c6f20232801e94e59a10821c372a92.jpeg', NULL, '2019-04-10 09:27:33', 0),
(331, 'ca2cfa24d1ab', 63, 'b4a54c60ffb040393a96a8a91e732c26.jpeg', NULL, '2019-04-10 09:27:39', 0),
(332, 'e85f628f9a28', 63, '5075ca6240a12c240d02b3c77e477666.jpeg', NULL, '2019-04-10 09:27:46', 0),
(333, '9017839a7c5a', 63, '2f22275a222aaf1e655efd09346eb031.jpeg', NULL, '2019-04-10 09:27:54', 0),
(334, '0564ab9996ca', 63, 'efea87f8b9f8049caff00dcf1c4b3d79.jpeg', NULL, '2019-04-10 09:28:01', 1),
(335, '14c3aa3d0a4c', 63, 'adc4b3996fb74890563b91a3c5e5c06a.jpeg', NULL, '2019-04-10 09:28:11', 0),
(336, '0ceaabd5d888', 63, '7e95b8f3da92b389f7f4c0165dc6d6f2.jpeg', NULL, '2019-04-10 09:28:29', 1),
(337, '22122b7e87e5', 63, '6db70345551395c341a50b0617c0b566.jpeg', NULL, '2019-04-10 09:28:33', 3),
(338, 'b4120ee702eb', 63, '7e42ea31321ff136dcccdb33314e9fa8.jpeg', NULL, '2019-04-10 09:28:37', 3);
-- --------------------------------------------------------
--
-- Структура таблицы `subscribers`
--
CREATE TABLE `subscribers` (
`id_subscriber` int(11) NOT NULL,
`sub_object` int(11) NOT NULL
) ENGINE=InnoDB DEFAULT CHARSET=utf8;
--
-- Дамп данных таблицы `subscribers`
--
INSERT INTO `subscribers` (`id_subscriber`, `sub_object`) VALUES
(63, 66),
(63, 68),
(63, 71),
(63, 72),
(63, 73),
(63, 53),
(71, 53),
(71, 72),
(71, 68),
(71, 67),
(71, 70),
(69, 68),
(69, 72),
(69, 67),
(69, 71),
(70, 68),
(70, 72),
(70, 67),
(70, 71),
(70, 69),
(67, 68),
(67, 72),
(67, 69),
(67, 71),
(73, 68),
(73, 72),
(73, 53),
(73, 64),
(73, 65),
(73, 70),
(73, 63),
(73, 44),
(68, 72),
(68, 71),
(68, 67),
(68, 69),
(68, 63),
(74, 72),
(74, 71),
(74, 67),
(74, 68),
(74, 69),
(74, 73),
(72, 68),
(72, 69),
(72, 67),
(72, 70),
(72, 63),
(63, 69),
(74, 63);
-- --------------------------------------------------------
--
-- Структура таблицы `users`
--
CREATE TABLE `users` (
`id` int(11) NOT NULL,
`login` varchar(150) NOT NULL,
`count_publications` int(11) NOT NULL DEFAULT '0',
`count_subscribers` int(11) NOT NULL DEFAULT '0',
`count_subscriptions` int(11) NOT NULL DEFAULT '0',
`name` varchar(150) DEFAULT NULL,
`password` varchar(255) NOT NULL,
`web_cyte` varchar(100) DEFAULT NULL,
`about` text,
`avatar` varchar(200) DEFAULT NULL,
`date_register` timestamp NOT NULL DEFAULT CURRENT_TIMESTAMP,
`confirmed` text NOT NULL,
`code_restore_pass` varchar(150) DEFAULT NULL
) ENGINE=InnoDB DEFAULT CHARSET=utf8;
--
-- Дамп данных таблицы `users`
--
INSERT INTO `users` (`id`, `login`, `count_publications`, `count_subscribers`, `count_subscriptions`, `name`, `password`, `web_cyte`, `about`, `avatar`, `date_register`, `confirmed`, `code_restore_pass`) VALUES
(44, '533215137', 0, 1, 0, 'Леха Пидоркин', '$2y$10$MMB2YrTYp6nRbaHv1uwC3O4SiUrBMXt7XNYenNi/U1p8eA3XbxccG', NULL, NULL, 'no_image_user.png', '2019-02-24 17:06:47', '1', NULL),
(53, '135105988', 0, 3, 0, 'Влад Кунченко', '$2y$10$z7CJIEA5dBibkI737zHwTOUETLjVpPqT0SAyImf5bGknnZt8it8Rq', NULL, NULL, '417957bab44cf61c353a77053910c95b.jpg', '2019-03-27 09:24:30', '1', NULL),
(63, 'podpishick123', 13, 4, 7, 'Эдуард Евдокимов', '$2y$10$jPEMO0X3of6Ie/zb8A6lWuHbGuNA.IQQyINBmpl06GPOm9yMgwOie', 'www.google.com', 'программер с детства', 'no_image_user.png', '2019-04-10 08:01:47', '1', NULL),
(64, 'mike_speed', 0, 1, 0, 'mike_LA', '$2y$10$e9.4fuz8NiwskWalsUYsrOxa/57TYb2HZBAkUooBDWnpXB6UzUlpK', NULL, NULL, 'no_image_user.png', '2019-04-10 08:02:52', '1', NULL),
(65, 'good_angela', 0, 1, 0, NULL, '$2y$10$dwZIACIwEupd5mGuTKceYeZ2SuZPKc72dquqPp7dmtGPg7aPtGQN2', NULL, NULL, 'no_image_user.png', '2019-04-10 08:08:57', '1', NULL),
(66, 'bob', 0, 1, 0, NULL, '$2y$10$9mluN39Ly565JPW3SjgWcufjHUNrDMoQgdfcSv2a2CnpPVJDed6W2', NULL, NULL, 'no_image_user.png', '2019-04-10 08:10:08', '1', NULL),
(67, 'samuel_l_jackson', 5, 6, 4, 'черный сем', '$2y$10$Af49rNjCCwF7vML9Kq0M4ud3pJ4uroG3dLVMfErlRmbQe5Ymh8rga', '', '', '336c2326c6bf73d1f6a0f68ba3258d05.jpeg', '2019-04-10 08:12:07', '1', NULL),
(68, 'Ryan_Gosling', 5, 8, 5, '', '$2y$10$A4Tm4N9VB/m.dVmIdt2T/O6wewzLS7HtmCfgij/sUkjijtOHMcOr.', '', '', '248281438e5b9364e1e782bfc4440f28.jpeg', '2019-04-10 08:16:00', '1', NULL),
(69, 'Emma_Stone', 3, 6, 4, '', '$2y$10$YEsGCkWfbZRA/NBsvLQtb.6Wmchr4g4LWK3fPlpMskelgedCadOMC', '', '', '9089df430e2f02e6b443e6226f0c569c.jpeg', '2019-04-10 08:17:23', '1', NULL),
(70, 'Jake_Gyllenhaal', 0, 3, 5, 'Тот, что снимался в "Левша"', '$2y$10$0auJKifvypxMrTwAik8hl.21C9rzd3zxh5vkbkVRhZ8XRYhPZyQzu', '', '', 'e53ba04885b074370f3d4827b81d2160.jpeg', '2019-04-10 08:19:14', '1', NULL),
(71, 'Russell_Crowe', 6, 6, 5, 'Поехавший математик', '$2y$10$pjC7rPvMU5glNcHbW35th.updJoj9E/gQnayIf7s4NCL.8HcSCBpO', '', '', '5111b34886ee6a047ec356143535169a.jpeg', '2019-04-10 08:21:43', '1', NULL),
(72, 'scarlett_johansson', 4, 8, 5, 'люблю ее ехансон)))', '$2y$10$cW9UJCLKQ3QTdSBSi5qbG.XYcf32wa2xPH8kUXUm5W.c14JpR6jtC', '', '', '67ad99ebdb57337f9cc0fee7b8734d90.jpeg', '2019-04-10 08:23:27', '1', NULL),
(73, 'alexander_nevski', 6, 2, 8, 'best body builder in the world', '$2y$10$xVtv3H.QT9NTURonYmF3cuAOr8dAKEy8pA9P9k7Dyx69YyQAIyrg6', '', '', '332b6b4feb64be512ad5a04f1b612d77.jpeg', '2019-04-10 08:26:46', '1', NULL),
(74, 'JamesMcAvoy', 0, 0, 7, '', '$2y$10$rz4qwafzgnDp8h6b1eM5Xu1PESO4kc.SCCX8eoapNxHssZxl9szTS', '', '', 'd0a2373ba36cb2fee52789b7b3d8854f.jpeg', '2019-04-10 08:41:07', '1', NULL);
--
-- Индексы сохранённых таблиц
--
--
-- Индексы таблицы `action_users`
--
ALTER TABLE `action_users`
ADD PRIMARY KEY (`id`),
ADD KEY `action_user` (`object`),
ADD KEY `action_object` (`action_user`) USING BTREE;
--
-- Индексы таблицы `comments`
--
ALTER TABLE `comments`
ADD PRIMARY KEY (`id`),
ADD KEY `parent_id_user` (`parent_id_user`),
ADD KEY `parent_id_photo` (`parent_id_publication`);
--
-- Индексы таблицы `hashtags`
--
ALTER TABLE `hashtags`
ADD PRIMARY KEY (`id`),
ADD KEY `parent_id_publication` (`parent_id_publication`);
--
-- Индексы таблицы `likes_comments`
--
ALTER TABLE `likes_comments`
ADD PRIMARY KEY (`id_user`,`id_comment`),
ADD KEY `id_comment` (`id_comment`);
--
-- Индексы таблицы `likes_publications`
--
ALTER TABLE `likes_publications`
ADD PRIMARY KEY (`user_id`,`publication_id`),
ADD KEY `publication_id` (`publication_id`);
--
-- Индексы таблицы `mails`
--
ALTER TABLE `mails`
ADD PRIMARY KEY (`id`),
ADD UNIQUE KEY `mail` (`mail`),
ADD KEY `parent_id` (`parent_id`);
--
-- Индексы таблицы `publications`
--
ALTER TABLE `publications`
ADD PRIMARY KEY (`id`),
ADD UNIQUE KEY `public_id` (`public_id`),
ADD KEY `parent_id` (`parent_id`) USING BTREE;
--
-- Индексы таблицы `subscribers`
--
ALTER TABLE `subscribers`
ADD KEY `sub_object` (`sub_object`),
ADD KEY `subscribers_ibfk_1` (`id_subscriber`);
--
-- Индексы таблицы `users`
--
ALTER TABLE `users`
ADD PRIMARY KEY (`id`),
ADD UNIQUE KEY `login` (`login`);
--
-- AUTO_INCREMENT для сохранённых таблиц
--
--
-- AUTO_INCREMENT для таблицы `action_users`
--
ALTER TABLE `action_users`
MODIFY `id` int(11) NOT NULL AUTO_INCREMENT, AUTO_INCREMENT=122;
--
-- AUTO_INCREMENT для таблицы `comments`
--
ALTER TABLE `comments`
MODIFY `id` int(11) NOT NULL AUTO_INCREMENT, AUTO_INCREMENT=189;
--
-- AUTO_INCREMENT для таблицы `hashtags`
--
ALTER TABLE `hashtags`
MODIFY `id` int(11) NOT NULL AUTO_INCREMENT, AUTO_INCREMENT=18;
--
-- AUTO_INCREMENT для таблицы `mails`
--
ALTER TABLE `mails`
MODIFY `id` int(11) NOT NULL AUTO_INCREMENT, AUTO_INCREMENT=60;
--
-- AUTO_INCREMENT для таблицы `publications`
--
ALTER TABLE `publications`
MODIFY `id` int(11) NOT NULL AUTO_INCREMENT, AUTO_INCREMENT=339;
--
-- AUTO_INCREMENT для таблицы `users`
--
ALTER TABLE `users`
MODIFY `id` int(11) NOT NULL AUTO_INCREMENT, AUTO_INCREMENT=75;
--
-- Ограничения внешнего ключа сохраненных таблиц
--
--
-- Ограничения внешнего ключа таблицы `action_users`
--
ALTER TABLE `action_users`
ADD CONSTRAINT `action_users_ibfk_1` FOREIGN KEY (`action_user`) REFERENCES `users` (`id`),
ADD CONSTRAINT `action_users_ibfk_2` FOREIGN KEY (`object`) REFERENCES `users` (`id`);
--
-- Ограничения внешнего ключа таблицы `comments`
--
ALTER TABLE `comments`
ADD CONSTRAINT `comments_ibfk_1` FOREIGN KEY (`parent_id_user`) REFERENCES `users` (`id`) ON DELETE CASCADE ON UPDATE CASCADE,
ADD CONSTRAINT `comments_ibfk_2` FOREIGN KEY (`parent_id_publication`) REFERENCES `publications` (`id`) ON DELETE CASCADE ON UPDATE CASCADE;
--
-- Ограничения внешнего ключа таблицы `hashtags`
--
ALTER TABLE `hashtags`
ADD CONSTRAINT `hashtags_ibfk_1` FOREIGN KEY (`parent_id_publication`) REFERENCES `publications` (`id`) ON DELETE CASCADE ON UPDATE CASCADE;
--
-- Ограничения внешнего ключа таблицы `likes_comments`
--
ALTER TABLE `likes_comments`
ADD CONSTRAINT `likes_comments_ibfk_1` FOREIGN KEY (`id_user`) REFERENCES `users` (`id`) ON DELETE CASCADE ON UPDATE CASCADE,
ADD CONSTRAINT `likes_comments_ibfk_2` FOREIGN KEY (`id_comment`) REFERENCES `comments` (`id`) ON DELETE CASCADE ON UPDATE CASCADE;
--
-- Ограничения внешнего ключа таблицы `likes_publications`
--
ALTER TABLE `likes_publications`
ADD CONSTRAINT `likes_publications_ibfk_1` FOREIGN KEY (`user_id`) REFERENCES `users` (`id`) ON DELETE CASCADE ON UPDATE CASCADE,
ADD CONSTRAINT `likes_publications_ibfk_2` FOREIGN KEY (`publication_id`) REFERENCES `publications` (`id`) ON DELETE CASCADE ON UPDATE CASCADE;
--
-- Ограничения внешнего ключа таблицы `mails`
--
ALTER TABLE `mails`
ADD CONSTRAINT `mails_ibfk_1` FOREIGN KEY (`parent_id`) REFERENCES `users` (`id`) ON DELETE CASCADE ON UPDATE CASCADE;
--
-- Ограничения внешнего ключа таблицы `publications`
--
ALTER TABLE `publications`
ADD CONSTRAINT `publications_ibfk_1` FOREIGN KEY (`parent_id`) REFERENCES `users` (`id`) ON DELETE CASCADE ON UPDATE CASCADE;
--
-- Ограничения внешнего ключа таблицы `subscribers`
--
ALTER TABLE `subscribers`
ADD CONSTRAINT `subscribers_ibfk_1` FOREIGN KEY (`id_subscriber`) REFERENCES `users` (`id`) ON DELETE CASCADE ON UPDATE CASCADE,
ADD CONSTRAINT `subscribers_ibfk_2` FOREIGN KEY (`sub_object`) REFERENCES `users` (`id`) ON DELETE CASCADE ON UPDATE CASCADE;
COMMIT;
/*!40101 SET CHARACTER_SET_CLIENT=@OLD_CHARACTER_SET_CLIENT */;
/*!40101 SET CHARACTER_SET_RESULTS=@OLD_CHARACTER_SET_RESULTS */;
/*!40101 SET COLLATION_CONNECTION=@OLD_COLLATION_CONNECTION */;
|
select top 15 * from family order by familyid desc
select top 6 * from person order by personid desc
select top 6 * from property order by propertyid desc
select * from medium
select top 6 * from Questionnaire
select * from occupation
select * from Daycare
select * from SampleType
select * from ConstructionType
select * from Country
select * from units
select * from MediumSampleResults
Select * from SampleLevelCategory
select * from AccessAgreement
alter database [WebSiteAdmin-Dev] set auto_close off
sp_who2
alter table Family alter column primaryLanguageID tinyint null
select * from dm_exec_sql_text |
CREATE TABLE `workplace-schema`.`assets` (
`id` INT NOT NULL AUTO_INCREMENT,
`building` VARCHAR(200) NOT NULL,
`floor` VARCHAR(3) NOT NULL,
`bay` VARCHAR(100) NOT NULL,
`name` VARCHAR(50) NOT NULL,
`type` VARCHAR(45) NOT NULL,
`isbookable` BIT NOT NULL DEFAULT 0,
PRIMARY KEY (`id`));
INSERT INTO `workplace-schema`.`assets` (
`building`, `floor`, `bay`, `name`, `type`, `isbookable`
)
VALUES (
'Prestige Dynasty', '2', 'Purple', 'BLR-Prestige-2F-D1', 'Desk', b'1'
); |
# insert into `t_role`(`id`,`name`) values (1,'ROLE_ADMIN'),(2,'ROLE_USER');
# insert into `t_user`(`id`,`password`,`username`) values (1,'root','root'),(2,'sang','sang');
# insert into `t_user_roles`(`t_user_id`,`roles_id`) values (1,1),(2,2); |
-- Ids that should be in the sourcing index
SELECT e.id
FROM example e;
|
Create Procedure sp_List_FavoriteReports
As
-- In coding while loading reports name into tree viewer
-- ['C' + reportID] is the key for that node.
-- the report name list only with 30 char in popup menu
Select Top 15 'C' + Cast([ID] as varchar),
Case When Len(Node) > 30 Then Left(Node,30) + '...' Else Node End
from ReportData RD, FavoriteReports FR
Where FR.ReportID = [ID] And FR.Active = 1 And RD.Action = 1 And RD.Inactive = 0
|
ALTER TABLE adquiriente ADD consecutivo int4;
|
create table geo_building (
id serial,
guid text,
constraint pk_geobuilding_id primary key (id)
);
select AddGeometryColumn ('public', 'geo_building', 'geom', 27700, 'MULTIPOLYGON', 3);
|
--将用户按照创建订单时间降序排序,获取用户最早的下单时间,并且位于2017年10月1日至11月30日之间
use bnb_hive_db;
drop table if exists tmp_zc_uid_createdtime;
create table tmp_zc_uid_createdtime as
select uid,orderid,createdtime from
(select uid,orderid,min(createdtime) over(partition by uid order by createdtime desc) as createdtime from ods_htl_bnborderdb.order_header_v2 where d = '2018-06-20') a
where createdtime >= '2017-10-01'
and createdtime <= '2018-11-30'
--计算首单用户在下单时及接下来半年内的累积消费
select sum(b.payamount)/sum(distinct a.uid) from
(select uid,orderid,createdtime from tmp_zc_uid_createdtime) a
join (select orderid,payamount ods_htl_bnborderdb.order_pay
where reverseflag = 1
and payamounttype = 1
and paychannel = 10
and statusid = 12
and substr(createdtime,1,10) >= '2017-10-01'
and substr(createdtime,1,10) <= '2018-05-31') b
on a.orderid = b.orderid |
--Criação Tabela Venda
create table venda (
codigo SERIAL PRIMARY KEY
data_criacao DATE,
valor_frete DECIMAL(10,2),
valor_desconto DECIMAL(10,2),
valor_total DECIMAL(10,2),
status VARCHAR(30),
observacao VARCHAR(200),
data_hora_entrega DATE,
codigo_cliente BIGINT,
codigo_usuario BIGINT,
FOREIGN KEY (codigo_cliente) REFERENCES cliente (codigo),
FOREIGN KEY (codigo_usuario) REFERENCES usuario (codigo)
)
|
drop database if exists md;
create database if not exists md collate 'utf8_general_ci';
use md;
set names utf8;
#用户
create table if not exists md_user(
id int primary key auto_increment,
username varchar(32) default '' comment '帐号',
password varchar(128) default '' comment 'md5加密密码',
logintime datetime default now() comment '最后登录的时间',
regtime datetime default now() comment '注册的时间',
lastloginip varchar(16) default '' comment '最后登录的ip',
nickname varchar(32) default '' comment '昵称',
names varchar(32) default '' comment '名字',
qq varchar(16) not null comment 'qq号',
province_id int not null comment '理发店所在的省份',
city_id int not null comment '理发店所在的市',
district_id int not null comment '理发店所在的区',
street_id int not null comment '理发店所在的街道',
postalcode int not null comment '邮政编码',
telephonenum varchar(16) not null comment '用户手机号码',
image_id int not null comment '头像图片储存地址 相对于 upload/',
company_id int comment '所属公司id'
)engine=MyISAM comment '用户表';
insert into md_user(username,password) values('123','202cb962ac59075b964b07152d234b70');
create table if not exists md_online(
id int primary key auto_increment,
mac varchar(32) not null comment 'mac地址',
client_id varchar(32) not null comment 'client_id',
start_time datetime not null comment '上线时间'
)comment '在线终端表';
-- ----------------------------
-- Table structure for think_auth_group
-- ----------------------------
CREATE TABLE if not exists md_auth_group (
`id` mediumint(8) unsigned primary key NOT NULL AUTO_INCREMENT,
`title` char(100) NOT NULL DEFAULT '' comment '用户组中文名',
`status` tinyint(1) NOT NULL DEFAULT '1' comment '状态 1为正常 0为禁用',
`rules` char(80) NOT NULL DEFAULT '' comment '用户组拥有的规则id,多个规则","隔开'
) ENGINE=MyISAM AUTO_INCREMENT=2 COMMENT='用户组表';
-- ----------------------------
-- Records of think_auth_group
-- ----------------------------
INSERT INTO `md_auth_group` VALUES ('1', '管理组', '1', '1,2,3,4,5,6,7,8,9,10,11,12,13,14,15');
INSERT INTO `md_auth_group` VALUES ('2', '用户组', '1', '1,5');
-- ----------------------------
-- Table structure for think_auth_group_access
-- ----------------------------
CREATE TABLE `md_auth_group_access` (
`uid` mediumint(8) unsigned NOT NULL COMMENT '用户id',
`group_id` mediumint(8) unsigned NOT NULL COMMENT '用户组id',
UNIQUE KEY `uid_group_id` (`uid`,`group_id`),
KEY `uid` (`uid`),
KEY `group_id` (`group_id`)
) ENGINE=MyISAM DEFAULT CHARSET=utf8 COMMENT='用户组明细表';
-- ----------------------------
-- Records of think_auth_group_access
-- ----------------------------
INSERT INTO `md_auth_group_access` VALUES ('1', '1');
-- ----------------------------
-- Table structure for think_auth_rule
-- ----------------------------
CREATE TABLE `md_auth_rule` (
`id` mediumint(8) unsigned NOT NULL AUTO_INCREMENT,
`name` char(80) NOT NULL DEFAULT '' COMMENT '规则唯一标识',
`title` char(20) NOT NULL DEFAULT '' COMMENT '规则中文名称',
`status` tinyint(1) NOT NULL DEFAULT '1' COMMENT '状态：为1正常，为0禁用',
`type` char(80) NOT NULL,
`condition` char(100) NOT NULL DEFAULT '' COMMENT '规则表达式，为空表示存在就验证，不为空表示按照条件验证',
PRIMARY KEY (`id`),
UNIQUE KEY `name` (`name`)
) ENGINE=MyISAM AUTO_INCREMENT=5 DEFAULT CHARSET=utf8 COMMENT='规则表';
-- ----------------------------
-- Records of think_auth_rule
-- ----------------------------
INSERT INTO `md_auth_rule` VALUES ('1', 'Index/index', '首页', '1', 'Admin', '');
INSERT INTO `md_auth_rule` VALUES ('2', 'Index/addAdvert', '新广告', '1', 'Admin', '');
INSERT INTO `md_auth_rule` VALUES ('3', 'Index/getAdvert', '广告列表', '1', 'Admin', '');
INSERT INTO `md_auth_rule` VALUES ('4', 'Index/addUser', '添加用户', '1', 'Admin', '');
INSERT INTO `md_auth_rule` VALUES ('5', 'Index/getUser', '用户列表', '1', 'Admin', '');
INSERT INTO `md_auth_rule` VALUES ('6', 'Index/getAuth', '权限查询', '1', 'Admin', '');
INSERT INTO `md_auth_rule` VALUES ('7', 'Index/addFile', '素材上传', '1', 'Admin', '');
INSERT INTO `md_auth_rule` VALUES ('8', 'Index/getFile', '查询素材', '1', 'Admin', '');
INSERT INTO `md_auth_rule` VALUES ('9', 'Index/addCompany', '添加广告主', '1', 'Admin', '');
INSERT INTO `md_auth_rule` VALUES ('10', 'Index/getCompany', '查询广告主', '1', 'Admin', '');
INSERT INTO `md_auth_rule` VALUES ('11', 'Index/addBarbershop', '添加店铺', '1', 'Admin', '');
INSERT INTO `md_auth_rule` VALUES ('12', 'Index/getbarbershop', '查询店铺', '1', 'Admin', '');
INSERT INTO `md_auth_rule` VALUES ('13', 'Index/addProduct', '添加终端', '1', 'Admin', '');
INSERT INTO `md_auth_rule` VALUES ('14', 'Index/getProduct', '查询终端', '1', 'Admin', '');
INSERT INTO `md_auth_rule` VALUES ('15', 'Index/addPlace', '添加地区', '1', 'Admin', '');
-- INSERT INTO `md_auth_rule` VALUES ('1', 'User/index', '用户首页', '1', 'Admin', '');
-- INSERT INTO `md_auth_rule` VALUES ('2', 'User/addUser', '添加用户', '1', 'Admin', '');
-- INSERT INTO `md_auth_rule` VALUES ('3', 'User/addUserGroupByUserId', '加入用户组', '1', 'Admin', '');
-- INSERT INTO `md_auth_rule` VALUES ('4', 'User/addUserInfo', '编辑用户信息', '1', 'Admin', '');
-- INSERT INTO `md_auth_rule` VALUES ('5', 'User/login', '用户登录', '1', 'Admin', '');
-- INSERT INTO `md_auth_rule` VALUES ('6', 'Advert/addAdvert', '广告上传', '1', 'Admin', '');
-- INSERT INTO `md_auth_rule` VALUES ('7', 'Advert/getAdvert', '广告查询', '1', 'Admin', '');
-- INSERT INTO `md_auth_rule` VALUES ('8', 'Advert/getCompany', '广告主查询', '1', 'Admin', '');
-- INSERT INTO `md_auth_rule` VALUES ('9', 'Advert/updateAdvert', '广告审核', '1', 'Admin', '');
-- INSERT INTO `md_auth_rule` VALUES ('10', 'Advert/delAdvert', '广告删除', '1', 'Admin', '');
-- INSERT INTO `md_auth_rule` VALUES ('11', 'User/getUser', '用户查询', '1', 'Admin', '');
-- INSERT INTO `md_auth_rule` VALUES ('12', 'User/getAllUser', '用户查询', '1', 'Admin', '');
-- INSERT INTO `md_auth_rule` VALUES ('13', 'User/delUser', '用户删除', '1', 'Admin', '');
-- INSERT INTO `md_auth_rule` VALUES ('15', 'Advert/saveAdvert', '广告修改', '1', 'Admin', '');
-- INSERT INTO `md_auth_rule` VALUES ('16', 'File/addImg', '图片上传', '1', 'Admin', '');
-- INSERT INTO `md_auth_rule` VALUES ('17', 'File/addVideo', '视频上传', '1', 'Admin', '');
-- INSERT INTO `md_auth_rule` VALUES ('18', 'File/getImg', '查询图片', '1', 'Admin', '');
-- INSERT INTO `md_auth_rule` VALUES ('19', 'File/getVideo', '查询视频', '1', 'Admin', '');
-- INSERT INTO `md_auth_rule` VALUES ('20', 'File/updateFile', '文件编辑', '1', 'Admin', '');
-- INSERT INTO `md_auth_rule` VALUES ('21', 'File/delFile', '文件删除', '1', 'Admin', '');
-- INSERT INTO `md_auth_rule` VALUES ('22', 'Company/addCom', '广告主新增', '1', 'Admin', '');
-- INSERT INTO `md_auth_rule` VALUES ('23', 'Company/getName', '查询广告主名字', '1', 'Admin', '');
-- INSERT INTO `md_auth_rule` VALUES ('24', 'Company/updateCompany', '广告主修改', '1', 'Admin', '');
-- INSERT INTO `md_auth_rule` VALUES ('25', 'Barbershop/addBarbershop', '添加店铺', '1', 'Admin', '');
-- INSERT INTO `md_auth_rule` VALUES ('26', 'Barbershop/queryBarbershop', '查询店铺', '1', 'Admin', '');
-- INSERT INTO `md_auth_rule` VALUES ('27', 'Barbershop/updateBarbershop', '店铺修改', '1', 'Admin', '');
-- INSERT INTO `md_auth_rule` VALUES ('28', 'Product/addProduct', '添加终端', '1', 'Admin', '');
-- INSERT INTO `md_auth_rule` VALUES ('29', 'Product/getProduct', '查询终端', '1', 'Admin', '');
-- INSERT INTO `md_auth_rule` VALUES ('30', 'Product/updateProduct', '编辑终端', '1', 'Admin', '');
-- INSERT INTO `md_auth_rule` VALUES ('31', 'Product/delProduct', '删除终端', '1', 'Admin', '');
-- INSERT INTO `md_auth_rule` VALUES ('32', 'Area/queryArea', '查询区域', '1', 'Admin', '');
-- INSERT INTO `md_auth_rule` VALUES ('33', 'Area/updatePlace', '修改地区', '1', 'Admin', '');
#广告表
create table if not exists md_advert(
id int primary key auto_increment,
ad_name varchar(32) default '' comment '广告的名称',
ad_company_id int comment '广告投放主id',
ad_area_id int comment '展示区域id',
ad_province_id int not null comment '理发店所在的省份',
ad_city_id int not null comment '理发店所在的市',
ad_district_id int not null comment '理发店所在的区',
ad_street_id int not null comment '理发店所在的街道',
barbershop_id int not null comment '理发店名称id',
img_id int comment '图片id',
video_id int comment '视频id',
ad_text text comment '广告描述',
ad_putnum int not null comment '投放终端数量',
ad_time datetime not null comment '投放时间',
ad_status enum('未上架','已上架','已下架') default '未上架', #上下架情况
ad_examine enum('通过','驳回','冻结','未审核') default '未审核', #审核状态
ad_pay enum('已付费','未付费','免费') default '未付费' #付费情况
)ENGINE=MyISAM comment '广告表';
#insert into md_advertisement values(1,1,'王老吉','mp4','四川联广','主页','四川',1000,now(),'已上架','通过','已付费');
-- insert into md_advert(ad_url) values("a.jpg"),("b.jpg"),("c.jpg");
#广告投放主
create table if not exists md_company(
id int primary key auto_increment,
user_id int not null comment '维护者id',
com_name varchar(32) not null comment '广告主名称',
province_id int not null comment '理发店所在的省份',
city_id int not null comment '理发店所在的市',
district_id int not null comment '理发店所在的区',
street_id int not null comment '理发店所在的街道',
barbershop_id int not null comment '理发店名称id'
)ENGINE=MyISAM comment '广告主表';
insert into md_company(com_name,province_id) values('哈哈',1),("呵呵",1);
#图片素材表
create table if not exists md_file_img(
id int primary key auto_increment,
big_img varchar(64) not null comment '原图',
small_img varchar(64) not null comment '缩略图',
img_name varchar(128) not null comment '文件名',
img_size varchar(16) not null comment '文件大小',
user_id int not null comment '上传用户id',
status enum('已上线','未上线') default '未上线' comment '文件状态'
)ENGINE=MyISAM COMMENT '图片素材表';
#视频素材表
create table if not exists md_file_video(
id int primary key auto_increment,
video_url varchar(64) not null comment '视频地址',
video_name varchar(64) not null comment '视频名称',
video_size varchar(16) not null comment '文件大小',
user_id int not null comment '上传用户id',
status enum('已上线','未上线') default '未上线' comment '文件状态'
)ENGINE=MyISAM COMMENT '视频素材表';
#理发店
create table if not exists md_barbershop(
id int primary key auto_increment,
user_id int not null comment '店主id',
barbershop_name varchar(128) default '' comment '理发店名称',
barbershop_province int not null comment '理发店所在的省份',
barbershop_city int not null comment '理发店所在的市',
barbershop_district int not null comment '理发店所在的区',
barbershop_street int not null comment '理发店所在的街道',
barbershop_cash float(8,2) default 0 comment '余额',
babershop_qrcode varchar(32) default '' comment '店铺二维码存放路径'
)ENGINE=MyISAM comment '理发店';
-- insert into md_barbershop values(1,1,'美美美发','凯越路一号',1000,'www.baidu.com/image');
#视频
create table if not exists md_video(
id int primary key auto_increment,
user_id int not null comment '上传用户id',
video_image varchar(128) default '' comment '视频预览图地址',
video_url varchar(128) default '' comment '视频地址 相对于 upload/',
video_name varchar(12) default '' comment '视频名称',
video_size varchar(12) default '' comment '视频大小',
video_area varchar(12) default '' comment '播放区域',
video_type enum('视频教程','娱乐视频','电影预告片') not null comment '视频分类',
video_productnum int not null comment '投放终端数量',
video_time datetime default now() not null comment '传时间',
video_status enum('上线','未上线') default '未上线' comment '线状态 默认未上线'
)ENGINE=MyISAM comment '视频表';
insert into md_video values(1,1,'www.imgage.com','wfewrwerewre','动物世界','400MB','四川','娱乐视频',1000,now(),'上线');
#终端
create table if not exists md_product(
id int primary key auto_increment,
province_id int not null comment '理发店所在的省份',
city_id int not null comment '理发店所在的市',
district_id int not null comment '理发店所在的区',
street_id int not null comment '理发店所在的街道',
barbershop_id int not null comment '终端所在店铺id',
product_type enum('单面机','双面机','挂式机') not null comment '机型',
product_maccode varchar(24) default '' comment 'mac码',
product_batch varchar(32) default '' comment '终端编号',
product_status enum('0','1') default '0' comment '运行状态:1为正在线',
product_fix enum('0','1') default '1' comment '报修状态: 0为报修' ,
last_time datetime default now() comment '最后登录时间'
)ENGINE=MyISAM comment '终端表';
-- insert into md_product values(1,1,'双面机','11.11.11.11.1',4325346456544,1,1);
create table if not exists `md_where` (
`id` int not null primary key auto_increment,
`where_name` varchar(50) not null comment '地区名字',
`parentid` int default '0' comment '所属上级id,最高级为0',
`parentid_list` varchar(20) default '0' comment '分类的层级关系，从最高级到自己，请用逗号隔开',
`depth` varchar(10) default null comment '深度，从1递增',
`state` varchar(10) default '1' comment '状态：0禁用，1启用',
`priority` varchar(10) default '0'comment '优先级，越大，同级显示的时候越靠前'
)ENGINE=MyISAM comment '地区';
insert into `md_where` values(1,'四川省',0,'1','1','1','0');
create table if not exists`md_province`(
`id` int not null primary key auto_increment,
`province_name` varchar(64 ) not null comment '省（级）名称'
)ENGINE=MyISAM comment '省';
insert into `md_province` values(1,'四川');
create table if not exists`md_city`(
`id` int not null primary key auto_increment,
`city_name` varchar(64) not null comment '市（级）名称',
province_id int not null
)ENGINE=MyISAM comment '市';
insert into `md_city` values(1,'成都',1);
insert into `md_city` values(2,'绵阳',1);
insert into `md_city` values(3,'德阳',1);
insert into `md_city` values(4,'南充',1);
create table if not exists`md_district`(
`id` int not null primary key auto_increment,
`district_name` varchar(64) not null comment '区/县（级）名称',
`city_id` int not null
)ENGINE=MyISAM comment '区/县';
insert into `md_district` values(1,'涪城区',2);
insert into `md_district` values(2,'高新区',2);
insert into `md_district` values(3,'游仙区',2);
insert into `md_district` values(4,'三台县',2);
insert into `md_district` values(5,'江油市',2);
create table if not exists`md_street`(
`id` int not null primary key auto_increment,
`street_name` varchar(64) not null comment '街道/村（级）名称',
`district_id` int not null
)ENGINE=MyISAM comment '街道/村';
insert into `md_street` values(1,'石桥铺村',2);
insert into `md_street` values(2,'凯越路一号',3);
insert into `md_street` values(3,'长虹大道',1);
create table if not exists`md_place`(
`id` int not null primary key auto_increment,
`place_name` varchar(64) not null comment '具体地址',
`street_id` int not null
)ENGINE=MyISAM comment '具体地址';
insert into `md_place` values(1,'万豪尊品二期',1);
insert into `md_place` values(2,'四川联广科技',2);
insert into `md_place` values(3,'涪城区人民政府',3);
insert into `md_place` values(4,'繁华似锦',1);
#页面广告区域
create table if not exists md_area(
id int primary key auto_increment,
area varchar(32) not null comment '区域名称'
);
insert into md_area values(1,'一级页面');
insert into md_area values(2,'二级页面左侧边栏');
insert into md_area values(3,'二级页面顶部');
|
col capture_name format a20
col queue_name format a20
SELECT CAPTURE_NAME, FIRST_SCN, APPLIED_SCN, REQUIRED_CHECKPOINT_SCN
FROM DBA_CAPTURE
order by capture_name;
|
INSERT INTO bears (name,age,gender,color,temperament,alive) VALUES
('Mr. Chocolate','M',31,'brown','happy',1),
('Rowdy','M',15,'brown','happy',1),
('Tabitha','F',8,'black','happy',1),
('Sergeant Brown','M',31,'white','angry',1),
('Melissa','F',31,'brown','happy',0),
('Grinch','M',31,'brown','happy',1),
('Wendy','F',31,'brown','happy',1),
(NULL,'M',31,'brown','happy',0); |
SELECT wd.DepositGroup,
mwc.MagicWandCreator AS [MagicWandCreator],
MIN(wd.DepositCharge) AS [MinDepositCharge]
FROM WizzardDeposits wd
JOIN WizzardDeposits mwc ON mwc.MagicWandCreator = wd.MagicWandCreator
GROUP BY wd.DepositGroup, mwc.MagicWandCreator
ORDER BY mwc.MagicWandCreator, wd.DepositGroup |
use movies
/* 1. Напишете заявка, която
извежда имената на
актрисите, които са
също и продуценти с
нетна стойност, поголяма от 10 милиона.*/
select name from moviestar
where name in (select name from movieexec where NETWORTH > 10000000)
/*2. Напишете заявка, която
извежда имената на
тези филмови звезди,
които не са продуценти */
select name from moviestar
where name not in (select name from MOVIEEXEC)
use pc
/*1. Напишете заявка, която извежда
производителите на персонални компютри с
честота на процесора поне 500 MHz.*/
select distinct maker from product
join pc on product.model = pc.model
where pc.speed >= 500
/*2. Напишете заявка, която извежда лаптопите,
чиято честота на CPU е по-ниска от
честотата на който и да е персонален
компютър.*/
select * from laptop
where speed > any(select speed from pc)
/*3. Напишете заявка, която извежда модела на
продукта (PC, лаптоп или принтер) с найвисока цена. */
select model
from (select model, price from pc
union all
select model, price from printer
union all
select model, price from laptop) allproducts
where price >= all (select price from pc
union all
select price from printer
union all
select price from laptop)
/*4. Напишете заявка, която извежда
производителите на цветните принтери с
най-ниска цена */
select * from printer
where color = 'y' and price <= all(select price from printer where color = 'y')
/* 5. Напишете заявка, която извежда
производителите на тези персонални
компютри с най-малко RAM памет, които
имат най-бързи процесори.*/
select distinct maker from product
where model in (select model from pc pc1
where pc1.ram <= all(select ram from pc)
and pc1.speed >= all(select speed from pc pc2 where pc2.ram = pc1.ram))
use ships
/* 1. Напишете заявка, която извежда
страните, чиито класове кораби са с
най-голям брой оръдия*/
select distinct country from classes
where numguns >= all(select numguns from classes)
/*2. Напишете заявка, която извежда
имената на корабите с 16-инчови
оръдия (bore). */
select name from ships
where name in (select name from ships
join classes on ships.class = classes.class
where bore = 16)
/* 3. Напишете заявка, която извежда
имената на битките, в които са
участвали кораби от клас ‘Kongo’.*/
select battle from outcomes
where ship in (select name from ships
where class = 'Kongo')
/* 4. Напишете заявка, която извежда
имената на корабите, чиито брой
оръдия е най-голям в сравнение с
корабите със същия калибър оръдия
(bore).*/
select name from ships
where name in (select name from ships
join classes p1 on ships.class = p1.class
where p1.numguns >= all(select numguns from classes p2 where p1.bore = p2.bore)) |
-- phpMyAdmin SQL Dump
-- version 4.9.2
-- https://www.phpmyadmin.net/
--
-- Host: 127.0.0.1
-- Generation Time: Sep 18, 2020 at 07:41 AM
-- Server version: 10.4.10-MariaDB
-- PHP Version: 7.1.33
SET SQL_MODE = "NO_AUTO_VALUE_ON_ZERO";
SET AUTOCOMMIT = 0;
START TRANSACTION;
SET time_zone = "+00:00";
/*!40101 SET @OLD_CHARACTER_SET_CLIENT=@@CHARACTER_SET_CLIENT */;
/*!40101 SET @OLD_CHARACTER_SET_RESULTS=@@CHARACTER_SET_RESULTS */;
/*!40101 SET @OLD_COLLATION_CONNECTION=@@COLLATION_CONNECTION */;
/*!40101 SET NAMES utf8mb4 */;
--
-- Database: `emails`
--
-- --------------------------------------------------------
--
-- Table structure for table `email`
--
drop database if exists emails;
create database emails;
CREATE TABLE `email` (
`Email` varchar(150) NOT NULL
) ENGINE=InnoDB DEFAULT CHARSET=utf8mb4;
--
-- Dumping data for table `email`
--
INSERT INTO `email` (`Email`) VALUES
('seneshathilakarthne@gmail.com'),
('cmaduwanthi123@gmail.com'),
('cmaduwanthi123@gmail.com'),
('seneshathilakarthne@gmail.com'),
('seneshathilakarthne@gmail.com'),
('lahirusandeepa22@gmail.com');
COMMIT;
/*!40101 SET CHARACTER_SET_CLIENT=@OLD_CHARACTER_SET_CLIENT */;
/*!40101 SET CHARACTER_SET_RESULTS=@OLD_CHARACTER_SET_RESULTS */;
/*!40101 SET COLLATION_CONNECTION=@OLD_COLLATION_CONNECTION */;
|
-- Type,Count
SELECT
type,
COUNT(*) count
FROM (
SELECT
REGEXP_EXTRACT(line, r'(nagios_command|nagios_contact|nagios_contactground|nagios_host|nagios_hostdependency|nagios_hostescalation|nagios_hostextinfo|nagios_hostground|nagios_service|nagios_servicedependency|nagios_serviceescalation|nagios_serviceextinfo|nagios_servicegroup|nagios_timeperiod)\s?{') type,
id
FROM (
SELECT
SPLIT(content, '\n') line,
id
FROM
[puppet.puppet_content]
)
GROUP BY
type,
id )
WHERE
type IS NOT NULL
GROUP BY
1
ORDER BY
count DESC
|
/*
SQLyog Ultimate - MySQL GUI v8.2
MySQL - 5.5.27 : Database - asset
*********************************************************************
*/
/*!40101 SET NAMES utf8 */;
/*!40101 SET SQL_MODE=''*/;
/*!40014 SET @OLD_UNIQUE_CHECKS=@@UNIQUE_CHECKS, UNIQUE_CHECKS=0 */;
/*!40014 SET @OLD_FOREIGN_KEY_CHECKS=@@FOREIGN_KEY_CHECKS, FOREIGN_KEY_CHECKS=0 */;
/*!40101 SET @OLD_SQL_MODE=@@SQL_MODE, SQL_MODE='NO_AUTO_VALUE_ON_ZERO' */;
/*!40111 SET @OLD_SQL_NOTES=@@SQL_NOTES, SQL_NOTES=0 */;
CREATE DATABASE /*!32312 IF NOT EXISTS*/`asset` /*!40100 DEFAULT CHARACTER SET utf8 */;
USE `asset`;
/*Table structure for table `asset_incom` */
DROP TABLE IF EXISTS `asset_incom`;
CREATE TABLE `asset_incom` (
`id` int(11) NOT NULL,
`psn_code` int(11) DEFAULT NULL,
`current_month_date` date DEFAULT NULL,
`json_data` text,
`daily_incom` decimal(18,2) DEFAULT NULL,
`daily_pay` decimal(18,2) DEFAULT NULL,
`non_daily_incom` decimal(18,2) DEFAULT NULL,
`non_daily_pay` decimal(18,2) DEFAULT NULL,
`add_profit` decimal(18,2) DEFAULT NULL,
`tag_status` varchar(1) DEFAULT NULL,
`create_date` datetime DEFAULT NULL,
PRIMARY KEY (`id`),
KEY `FK_Reference_11` (`psn_code`),
CONSTRAINT `FK_Reference_11` FOREIGN KEY (`psn_code`) REFERENCES `person` (`psn_code`)
) ENGINE=InnoDB DEFAULT CHARSET=utf8;
/*Data for the table `asset_incom` */
/*Table structure for table `asset_out` */
DROP TABLE IF EXISTS `asset_out`;
CREATE TABLE `asset_out` (
`id` int(11) NOT NULL,
`psn_code` int(11) DEFAULT NULL,
`current_month_date` date DEFAULT NULL,
`json_data` text,
`original_capital` decimal(18,2) DEFAULT NULL,
`income_surplus` decimal(18,2) DEFAULT NULL,
`ratained_profit` decimal(18,2) DEFAULT NULL,
`tag_status` char(1) DEFAULT NULL,
`create_date` datetime DEFAULT NULL,
PRIMARY KEY (`id`),
KEY `FK_Reference_12` (`psn_code`),
CONSTRAINT `FK_Reference_12` FOREIGN KEY (`psn_code`) REFERENCES `person` (`psn_code`)
) ENGINE=InnoDB DEFAULT CHARSET=utf8;
/*Data for the table `asset_out` */
/*Table structure for table `const_category` */
DROP TABLE IF EXISTS `const_category`;
CREATE TABLE `const_category` (
`category` varchar(10) NOT NULL COMMENT '类型编码',
`cdescription` varchar(50) NOT NULL COMMENT '中文名称',
`edescription` varchar(50) DEFAULT NULL COMMENT '英文名称',
`query_sql` varchar(2000) DEFAULT NULL COMMENT '特殊情况下数据来源于动态的sql语句，则在此编写数据来源规则',
PRIMARY KEY (`category`)
) ENGINE=InnoDB DEFAULT CHARSET=utf8;
/*Data for the table `const_category` */
/*Table structure for table `const_dictionary` */
DROP TABLE IF EXISTS `const_dictionary`;
CREATE TABLE `const_dictionary` (
`category` varchar(30) NOT NULL COMMENT '代码种类',
`cost_code` varchar(30) NOT NULL COMMENT '代码值',
`en_us_caption` varchar(200) DEFAULT NULL COMMENT '英文描述',
`zh_tw_caption` varchar(200) DEFAULT NULL COMMENT '繁体中文描述',
`zh_cn_caption` varchar(200) DEFAULT NULL COMMENT '简体中文描述',
`seq_no` decimal(38,0) DEFAULT NULL COMMENT '排序使用，优先级为本字段，其次为code字段',
`level_no` varchar(10) DEFAULT NULL COMMENT '等级，职称需用',
`const_type` varchar(6) DEFAULT NULL COMMENT '判断属性类型',
PRIMARY KEY (`category`,`cost_code`)
) ENGINE=InnoDB DEFAULT CHARSET=utf8;
/*Data for the table `const_dictionary` */
/*Table structure for table `currency_fund` */
DROP TABLE IF EXISTS `currency_fund`;
CREATE TABLE `currency_fund` (
`id` int(11) NOT NULL,
`psn_code` int(11) DEFAULT NULL,
`current_month_date` date DEFAULT NULL,
`opening_balance` decimal(18,2) DEFAULT NULL,
`period_incom` decimal(18,2) DEFAULT NULL,
`period_pay` decimal(18,2) DEFAULT NULL,
`ending_balance` decimal(18,2) DEFAULT NULL,
`tag_status` char(1) DEFAULT NULL,
`create_date` datetime DEFAULT NULL,
PRIMARY KEY (`id`),
KEY `FK_Reference_9` (`psn_code`),
CONSTRAINT `FK_Reference_9` FOREIGN KEY (`psn_code`) REFERENCES `person` (`psn_code`)
) ENGINE=InnoDB DEFAULT CHARSET=utf8;
/*Data for the table `currency_fund` */
/*Table structure for table `fixed_asset` */
DROP TABLE IF EXISTS `fixed_asset`;
CREATE TABLE `fixed_asset` (
`id` int(11) NOT NULL,
`current_month_date` date DEFAULT NULL,
`asset_name` varchar(200) NOT NULL,
`psn_code` int(11) DEFAULT NULL,
`asset_money` decimal(18,2) DEFAULT NULL,
`asset_remark` text,
`tag_status` char(1) DEFAULT NULL,
`create_date` datetime DEFAULT NULL,
PRIMARY KEY (`id`,`asset_name`),
KEY `FK_Reference_5` (`psn_code`),
CONSTRAINT `FK_Reference_5` FOREIGN KEY (`psn_code`) REFERENCES `person` (`psn_code`)
) ENGINE=InnoDB DEFAULT CHARSET=utf8;
/*Data for the table `fixed_asset` */
/*Table structure for table `fund_change` */
DROP TABLE IF EXISTS `fund_change`;
CREATE TABLE `fund_change` (
`id` int(11) NOT NULL,
`psn_code` int(11) DEFAULT NULL,
`current_month_date` date DEFAULT NULL,
`consume_date` date DEFAULT NULL,
`item` varchar(500) DEFAULT NULL,
`money` decimal(18,2) DEFAULT NULL,
`profit_loss_sort` varchar(100) DEFAULT NULL,
`pay_mode` varchar(100) DEFAULT NULL,
`pay_money` decimal(18,2) DEFAULT NULL,
`incom_mode` varchar(100) DEFAULT NULL,
`incom_money` decimal(18,2) DEFAULT NULL,
`create_date` datetime DEFAULT NULL,
`tag_status` char(1) DEFAULT NULL,
PRIMARY KEY (`id`),
KEY `FK_Reference_10` (`psn_code`),
CONSTRAINT `FK_Reference_10` FOREIGN KEY (`psn_code`) REFERENCES `person` (`psn_code`)
) ENGINE=InnoDB DEFAULT CHARSET=utf8;
/*Data for the table `fund_change` */
/*Table structure for table `invest_bank` */
DROP TABLE IF EXISTS `invest_bank`;
CREATE TABLE `invest_bank` (
`id` int(11) NOT NULL,
`psn_code` int(11) DEFAULT NULL,
`invest_code` int(11) DEFAULT NULL,
`current_month_date` date DEFAULT NULL,
`invest_name` varchar(200) DEFAULT NULL,
`invest_date` date DEFAULT NULL,
`invest_type` varchar(20) DEFAULT NULL,
`invest_money` decimal(18,2) DEFAULT NULL,
`invest_profit` decimal(18,2) DEFAULT NULL,
`invest_profit_date` date DEFAULT NULL,
`annualized_rate_return` varchar(50) DEFAULT NULL,
`tag_status` char(1) DEFAULT NULL,
`create_date` datetime DEFAULT NULL,
PRIMARY KEY (`id`),
KEY `FK_Reference_4` (`psn_code`),
CONSTRAINT `FK_Reference_4` FOREIGN KEY (`psn_code`) REFERENCES `person` (`psn_code`)
) ENGINE=InnoDB DEFAULT CHARSET=utf8;
/*Data for the table `invest_bank` */
/*Table structure for table `pay_collection` */
DROP TABLE IF EXISTS `pay_collection`;
CREATE TABLE `pay_collection` (
`id` int(11) NOT NULL,
`psn_code` int(11) DEFAULT NULL,
`current_month_date` date DEFAULT NULL,
`receipt_item` varchar(500) DEFAULT NULL,
`receipt_date` date DEFAULT NULL,
`person` varchar(200) DEFAULT NULL,
`receipt_pay` decimal(18,2) DEFAULT NULL,
`tag_status` char(1) DEFAULT NULL,
`create_date` datetime DEFAULT NULL,
PRIMARY KEY (`id`),
KEY `FK_Reference_6` (`psn_code`),
CONSTRAINT `FK_Reference_6` FOREIGN KEY (`psn_code`) REFERENCES `person` (`psn_code`)
) ENGINE=InnoDB DEFAULT CHARSET=utf8;
/*Data for the table `pay_collection` */
/*Table structure for table `person` */
DROP TABLE IF EXISTS `person`;
CREATE TABLE `person` (
`psn_code` int(11) NOT NULL,
`cname` varchar(100) DEFAULT NULL,
`fname` varchar(100) DEFAULT NULL,
`lname` varchar(100) DEFAULT NULL,
`gender` varchar(1) DEFAULT NULL,
`title_no` varchar(100) DEFAULT NULL,
`org_code` decimal(18,0) DEFAULT NULL,
`org_ename` varchar(300) DEFAULT NULL,
`org_cname` varchar(600) DEFAULT NULL,
`pos_in_org` varchar(2000) DEFAULT NULL,
`dept` varchar(200) DEFAULT NULL,
`eaddress` varchar(1000) DEFAULT NULL,
`caddress` varchar(1000) DEFAULT NULL,
`tel` varchar(100) DEFAULT NULL,
`fax` varchar(100) DEFAULT NULL,
`email` varchar(300) DEFAULT NULL,
`http` varchar(400) DEFAULT NULL,
`highest_degree` varchar(400) DEFAULT NULL,
`tag_status` char(1) DEFAULT NULL,
`create_date` datetime DEFAULT NULL,
`update_time` datetime DEFAULT NULL,
`remark` text,
PRIMARY KEY (`psn_code`)
) ENGINE=InnoDB DEFAULT CHARSET=utf8;
/*Data for the table `person` */
/*Table structure for table `personal_loan` */
DROP TABLE IF EXISTS `personal_loan`;
CREATE TABLE `personal_loan` (
`id` int(11) NOT NULL,
`psn_code` int(11) DEFAULT NULL,
`current_month_date` date DEFAULT NULL,
`lend_person` varchar(100) DEFAULT NULL,
`lend_date` date DEFAULT NULL,
`lend_money` decimal(18,2) DEFAULT NULL,
`accumulate_profit` decimal(18,2) DEFAULT NULL,
`going` varchar(500) DEFAULT NULL,
`remark` text,
`create_date` datetime DEFAULT NULL,
`tag_status` char(1) DEFAULT NULL,
PRIMARY KEY (`id`),
KEY `FK_Reference_7` (`psn_code`),
CONSTRAINT `FK_Reference_7` FOREIGN KEY (`psn_code`) REFERENCES `person` (`psn_code`)
) ENGINE=InnoDB DEFAULT CHARSET=utf8;
/*Data for the table `personal_loan` */
/*Table structure for table `sys_authoritie` */
DROP TABLE IF EXISTS `sys_authoritie`;
CREATE TABLE `sys_authoritie` (
`AUTHORITY_ID` decimal(8,0) NOT NULL COMMENT '自动序列',
`NAME` varchar(400) DEFAULT NULL COMMENT '权限代码名',
`DISPLAY_NAME` varchar(400) DEFAULT NULL COMMENT '权限描述',
`PARENT_ID` decimal(8,0) DEFAULT NULL COMMENT ' 上级id',
PRIMARY KEY (`AUTHORITY_ID`)
) ENGINE=InnoDB DEFAULT CHARSET=utf8 COMMENT='权限表';
/*Data for the table `sys_authoritie` */
/*Table structure for table `sys_log` */
DROP TABLE IF EXISTS `sys_log`;
CREATE TABLE `sys_log` (
`log_code` decimal(18,0) NOT NULL,
`psn_code` decimal(18,0) DEFAULT NULL,
`log_type` varchar(40) DEFAULT NULL,
`key_code` varchar(200) DEFAULT NULL,
`create_date` datetime DEFAULT NULL,
`log_action` varchar(2000) DEFAULT NULL,
`log_detail` text,
`client_ip` varchar(30) DEFAULT NULL,
`server_ip` varchar(300) DEFAULT NULL,
`exception` text,
`user_agent` varchar(1000) DEFAULT NULL,
PRIMARY KEY (`log_code`)
) ENGINE=InnoDB DEFAULT CHARSET=utf8;
/*Data for the table `sys_log` */
/*Table structure for table `sys_resource` */
DROP TABLE IF EXISTS `sys_resource`;
CREATE TABLE `sys_resource` (
`RESOURCE_ID` decimal(18,0) NOT NULL COMMENT '主键',
`RESOURCE_TYPE` varchar(20) NOT NULL COMMENT '菜单、还是页面menu、url',
`VALUE` varchar(255) DEFAULT NULL COMMENT 'URL',
`ORDER_NUM` decimal(4,0) DEFAULT NULL COMMENT '顺序(权限控制按顺序匹配URL)',
`PARENT_ID` decimal(18,0) DEFAULT NULL COMMENT '父菜单',
`TARGET` varchar(20) DEFAULT NULL COMMENT '显示窗名称(mainFrame , _blank,_parent)',
`ZH_CN_NAME` varchar(200) DEFAULT NULL COMMENT '菜单名，简体中文',
`STATUS` decimal(1,0) NOT NULL DEFAULT '1' COMMENT '是否启用状态',
`LAVELS` decimal(1,0) DEFAULT '0' COMMENT '层次，用于菜单等级',
`REMARK` varchar(400) DEFAULT NULL COMMENT '备注',
`IMG_URL` varchar(50) DEFAULT NULL COMMENT '快捷菜单图片的url',
`TOTAL_SQL` varchar(4000) DEFAULT NULL COMMENT '快捷菜单图片上的统计数',
`NAV_IMG_URL` varchar(200) DEFAULT NULL COMMENT 'Nav 菜单图片的url',
`NAV_ENABLED` decimal(1,0) DEFAULT '0' COMMENT 'Nav enable',
`OLD_TOTAL_SQL` varchar(4000) DEFAULT NULL COMMENT '快捷菜单图片上的统计数(查询老系统)',
`ZH_TW_NAME` varchar(200) DEFAULT NULL COMMENT '菜单名，中文繁体',
`EN_US_NAME` varchar(200) DEFAULT NULL COMMENT '菜单名，英文',
`FLAG_LAN` char(2) DEFAULT '01' COMMENT '内网标示 (01：外网，10：内网，11：内外网)',
`STMS_MENU_ID` decimal(38,0) DEFAULT NULL COMMENT '关联stms系统sys_menu.menu_id',
`CLASS_NAME` varchar(50) DEFAULT NULL COMMENT '快捷通道的class名字',
PRIMARY KEY (`RESOURCE_ID`)
) ENGINE=InnoDB DEFAULT CHARSET=utf8 COMMENT='web资源表';
/*Data for the table `sys_resource` */
insert into `sys_resource`(`RESOURCE_ID`,`RESOURCE_TYPE`,`VALUE`,`ORDER_NUM`,`PARENT_ID`,`TARGET`,`ZH_CN_NAME`,`STATUS`,`LAVELS`,`REMARK`,`IMG_URL`,`TOTAL_SQL`,`NAV_IMG_URL`,`NAV_ENABLED`,`OLD_TOTAL_SQL`,`ZH_TW_NAME`,`EN_US_NAME`,`FLAG_LAN`,`STMS_MENU_ID`,`CLASS_NAME`) values ('1000','sysmenu','/assets/menulist',NULL,'0',NULL,'菜单管理','1','0','菜单管理',NULL,NULL,NULL,'0',NULL,NULL,NULL,'01',NULL,NULL),('1010','sysmenu','/assets/userlist',NULL,'0',NULL,'用户管理','1','0','用户管理',NULL,NULL,NULL,'0',NULL,NULL,NULL,'01',NULL,NULL),('1011','sysmenu','/assets/constCategory',NULL,'0',NULL,'数据字典类别','0',NULL,'数字字典类别',NULL,NULL,NULL,'0',NULL,NULL,NULL,NULL,NULL,NULL),('1012','sysmenu','/assets/constDictionary',NULL,'0',NULL,'数据字典信息','1',NULL,'数据字典，存储一些基本数据信息',NULL,NULL,NULL,'0',NULL,NULL,NULL,NULL,NULL,NULL);
/*Table structure for table `sys_resource_authoritie` */
DROP TABLE IF EXISTS `sys_resource_authoritie`;
CREATE TABLE `sys_resource_authoritie` (
`AUTHORITY_ID` decimal(9,0) NOT NULL COMMENT '权限表主键',
`RESOURCE_ID` decimal(9,0) NOT NULL COMMENT '资源表主键',
PRIMARY KEY (`AUTHORITY_ID`,`RESOURCE_ID`)
) ENGINE=InnoDB DEFAULT CHARSET=utf8 COMMENT='资源功能集关联表';
/*Data for the table `sys_resource_authoritie` */
/*Table structure for table `sys_role` */
DROP TABLE IF EXISTS `sys_role`;
CREATE TABLE `sys_role` (
`ROLE_ID` decimal(3,0) NOT NULL COMMENT '角色标识',
`NAME` varchar(120) DEFAULT NULL COMMENT '角色名称',
`PARENT_ID` decimal(3,0) DEFAULT NULL COMMENT '父角色标识',
`DESCRIPTION` varchar(200) DEFAULT NULL COMMENT '简要描述角色',
`STATE` decimal(1,0) NOT NULL DEFAULT '1' COMMENT '描述角色状态：0无效 1有效',
`TYPE` decimal(1,0) NOT NULL DEFAULT '1' COMMENT '角色类型 , 1授予 ，2下发 ，3授予下发',
`MANAGE_ROLES` varchar(400) DEFAULT NULL COMMENT '管理的角色，角色ID之间以逗号分隔',
`CLASS_NAME` varchar(400) DEFAULT 'reg_peo' COMMENT '角色样式图标',
PRIMARY KEY (`ROLE_ID`)
) ENGINE=InnoDB DEFAULT CHARSET=utf8 COMMENT='角色数据表';
/*Data for the table `sys_role` */
/*Table structure for table `sys_role_authoritie` */
DROP TABLE IF EXISTS `sys_role_authoritie`;
CREATE TABLE `sys_role_authoritie` (
`ROLE_ID` decimal(3,0) NOT NULL COMMENT '角色ID',
`AUTHORITY_ID` decimal(8,0) NOT NULL COMMENT '资源集ID',
`TYPE` decimal(1,0) NOT NULL DEFAULT '0' COMMENT '类型',
PRIMARY KEY (`ROLE_ID`,`AUTHORITY_ID`)
) ENGINE=InnoDB DEFAULT CHARSET=utf8 COMMENT='角色权限表';
/*Data for the table `sys_role_authoritie` */
/*Table structure for table `sys_user` */
DROP TABLE IF EXISTS `sys_user`;
CREATE TABLE `sys_user` (
`USERID` decimal(18,0) NOT NULL COMMENT '关键字，同psn_code',
`LOGIN_NAME` varchar(400) NOT NULL COMMENT '登录名',
`PASSWORD` varchar(300) NOT NULL COMMENT '密码',
`ENABLED` decimal(1,0) NOT NULL DEFAULT '1' COMMENT '帐号状态 0 禁用,1正常,2-删除用户',
`TOKEN_CHANGED` decimal(1,0) DEFAULT '0' COMMENT '标记是否已确认忘记密码邮件 0-未做忘记密码操作 1-未确认邮件 2-已确认邮件',
`NODE_ID` decimal(2,0) NOT NULL DEFAULT '1' COMMENT '用户数据存储区域位置（未使用）',
`EMAIL` varchar(400) DEFAULT NULL COMMENT '首选通信邮件地址(默认同登录名)',
`MOBILE` decimal(30,0) DEFAULT NULL COMMENT '手机号码登录',
`UKEYSN` varchar(80) DEFAULT NULL COMMENT 'ukey序列号',
`UKEYPWD` varchar(128) DEFAULT NULL COMMENT 'ukey的pin密码,与用户表密码一致',
`ISUKEY` char(1) DEFAULT NULL COMMENT '是否对此用户启用(1启用 ,null 不启用,启用的在外网不能登陆)',
`ISINTERNAL` char(1) DEFAULT NULL COMMENT '是否基金委内用户(1是 ,0不是，是基金委用户的，不允许在外网登录)',
`PLAIN_PWD` varchar(128) DEFAULT NULL COMMENT '不知道',
`ADD_USER_ID` decimal(18,0) DEFAULT NULL COMMENT '邀请专家,添加人id',
`AUTH_LOGIN_IP` varchar(200) DEFAULT NULL COMMENT '登录的ip范围控制',
`LAST_ACCESS_IP` varchar(100) DEFAULT NULL COMMENT '最后一次登录的ip地址',
`LOCALE` varchar(10) DEFAULT NULL COMMENT '不知道',
`PASSWORD_UPDATE_TIME` date DEFAULT NULL COMMENT '密码更新时间',
`LAST_LOGIN_TIME` datetime DEFAULT NULL COMMENT '最后登录时间',
PRIMARY KEY (`USERID`)
) ENGINE=InnoDB DEFAULT CHARSET=utf8 COMMENT='能够登录的 人员信息表';
/*Data for the table `sys_user` */
insert into `sys_user`(`USERID`,`LOGIN_NAME`,`PASSWORD`,`ENABLED`,`TOKEN_CHANGED`,`NODE_ID`,`EMAIL`,`MOBILE`,`UKEYSN`,`UKEYPWD`,`ISUKEY`,`ISINTERNAL`,`PLAIN_PWD`,`ADD_USER_ID`,`AUTH_LOGIN_IP`,`LAST_ACCESS_IP`,`LOCALE`,`PASSWORD_UPDATE_TIME`,`LAST_LOGIN_TIME`) values ('1','sa','202cb962ac59075b964b07152d234b70','1','0','1',NULL,NULL,NULL,NULL,NULL,NULL,NULL,NULL,NULL,NULL,NULL,NULL,NULL);
/*Table structure for table `sys_user_role` */
DROP TABLE IF EXISTS `sys_user_role`;
CREATE TABLE `sys_user_role` (
`USER_ID` decimal(18,0) NOT NULL COMMENT '用户ID',
`ROLE_ID` decimal(3,0) NOT NULL COMMENT '角色ID',
`INS_ID` decimal(9,0) NOT NULL DEFAULT '0' COMMENT '单位ID',
PRIMARY KEY (`USER_ID`,`ROLE_ID`,`INS_ID`)
) ENGINE=InnoDB DEFAULT CHARSET=utf8 COMMENT='用户角色表';
/*Data for the table `sys_user_role` */
/*Table structure for table `user_const_dic` */
DROP TABLE IF EXISTS `user_const_dic`;
CREATE TABLE `user_const_dic` (
`category` varchar(30) DEFAULT NULL,
`psn_code` decimal(18,0) DEFAULT NULL,
`cost_code` varchar(500) DEFAULT NULL
) ENGINE=InnoDB DEFAULT CHARSET=utf8;
/*Data for the table `user_const_dic` */
/*!40101 SET SQL_MODE=@OLD_SQL_MODE */;
/*!40014 SET FOREIGN_KEY_CHECKS=@OLD_FOREIGN_KEY_CHECKS */;
/*!40014 SET UNIQUE_CHECKS=@OLD_UNIQUE_CHECKS */;
/*!40111 SET SQL_NOTES=@OLD_SQL_NOTES */;
|
SET @OLD_UNIQUE_CHECKS=@@UNIQUE_CHECKS, UNIQUE_CHECKS=0;
SET @OLD_FOREIGN_KEY_CHECKS=@@FOREIGN_KEY_CHECKS, FOREIGN_KEY_CHECKS=0;
SET @OLD_SQL_MODE=@@SQL_MODE, SQL_MODE='TRADITIONAL,ALLOW_INVALID_DATES';
CREATE SCHEMA IF NOT EXISTS `mydb` DEFAULT CHARACTER SET utf8 COLLATE utf8_general_ci ;
USE `mydb` ;
-- -----------------------------------------------------
-- Table `mydb`.`estado`
-- -----------------------------------------------------
DROP TABLE IF EXISTS `mydb`.`estado` ;
CREATE TABLE IF NOT EXISTS `mydb`.`estado` (
`idestado` INT NOT NULL AUTO_INCREMENT,
`nombre` VARCHAR(45) NOT NULL,
PRIMARY KEY (`idestado`))
ENGINE = InnoDB;
-- -----------------------------------------------------
-- Table `mydb`.`tipo_certificado`
-- -----------------------------------------------------
DROP TABLE IF EXISTS `mydb`.`tipo_certificado` ;
CREATE TABLE IF NOT EXISTS `mydb`.`tipo_certificado` (
`idtipo_certificado` INT NOT NULL AUTO_INCREMENT,
`nombre` VARCHAR(45) NOT NULL,
PRIMARY KEY (`idtipo_certificado`))
ENGINE = InnoDB;
-- -----------------------------------------------------
-- Table `mydb`.`certificado`
-- -----------------------------------------------------
DROP TABLE IF EXISTS `mydb`.`certificado` ;
CREATE TABLE IF NOT EXISTS `mydb`.`certificado` (
`idcertificado` INT NOT NULL AUTO_INCREMENT,
`correlativo` VARCHAR(32) NOT NULL,
`verificador` VARCHAR(32) NOT NULL,
`tipo` INT NULL,
`valido` TINYINT(1) NOT NULL,
`contenido` VARCHAR(10000) NULL,
PRIMARY KEY (`idcertificado`, `correlativo`, `verificador`),
INDEX `fk_certificado_1_idx` (`tipo` ASC),
CONSTRAINT `fk_certificado_1`
FOREIGN KEY (`tipo`)
REFERENCES `mydb`.`tipo_certificado` (`idtipo_certificado`)
ON DELETE NO ACTION
ON UPDATE NO ACTION)
ENGINE = InnoDB;
-- -----------------------------------------------------
-- Table `mydb`.`ciudadano`
-- -----------------------------------------------------
DROP TABLE IF EXISTS `mydb`.`ciudadano` ;
CREATE TABLE IF NOT EXISTS `mydb`.`ciudadano` (
`idciudadano` INT NOT NULL AUTO_INCREMENT,
`predpi` INT NOT NULL,
`DPI` VARCHAR(20) NULL,
`primer_nombre` VARCHAR(45) NULL,
`segundo_nombre` VARCHAR(45) NULL,
`primer_apellido` VARCHAR(45) NULL,
`segundo_apellido` VARCHAR(45) NULL,
`fecha_nac` DATE NULL,
`genero` VARCHAR(1) NULL,
`pais` VARCHAR(45) NULL,
`departamento` VARCHAR(45) NULL,
`municipio` VARCHAR(45) NULL,
`estado` INT NULL,
`padre` INT NULL,
`madre` INT NULL,
PRIMARY KEY (`idciudadano`),
UNIQUE INDEX `DPI_UNIQUE` (`DPI` ASC),
INDEX `fk_ciudadano_1_idx` (`estado` ASC),
UNIQUE INDEX `pre-dpi_UNIQUE` (`predpi` ASC),
INDEX `fk_ciudadano_2_idx` (`padre` ASC),
INDEX `fk_ciudadano_3_idx` (`madre` ASC),
CONSTRAINT `fk_ciudadano_1`
FOREIGN KEY (`estado`)
REFERENCES `mydb`.`estado` (`idestado`)
ON DELETE NO ACTION
ON UPDATE NO ACTION,
CONSTRAINT `fk_ciudadano_4`
FOREIGN KEY (`predpi`)
REFERENCES `mydb`.`certificado` (`idcertificado`)
ON DELETE NO ACTION
ON UPDATE NO ACTION,
CONSTRAINT `fk_ciudadano_2`
FOREIGN KEY (`padre`)
REFERENCES `mydb`.`ciudadano` (`idciudadano`)
ON DELETE NO ACTION
ON UPDATE NO ACTION,
CONSTRAINT `fk_ciudadano_3`
FOREIGN KEY (`madre`)
REFERENCES `mydb`.`ciudadano` (`idciudadano`)
ON DELETE NO ACTION
ON UPDATE NO ACTION)
ENGINE = InnoDB;
-- -----------------------------------------------------
-- Table `mydb`.`matrimonio`
-- -----------------------------------------------------
DROP TABLE IF EXISTS `mydb`.`matrimonio` ;
CREATE TABLE IF NOT EXISTS `mydb`.`matrimonio` (
`esposo` INT NOT NULL,
`esposa` INT NOT NULL,
`certificado` INT NOT NULL,
PRIMARY KEY (`esposo`, `esposa`),
INDEX `fk_matrimonio_2_idx` (`esposa` ASC),
INDEX `fk_matrimonio_3_idx` (`certificado` ASC),
CONSTRAINT `fk_matrimonio_1`
FOREIGN KEY (`esposo`)
REFERENCES `mydb`.`ciudadano` (`idciudadano`)
ON DELETE CASCADE
ON UPDATE NO ACTION,
CONSTRAINT `fk_matrimonio_2`
FOREIGN KEY (`esposa`)
REFERENCES `mydb`.`ciudadano` (`idciudadano`)
ON DELETE CASCADE
ON UPDATE NO ACTION,
CONSTRAINT `fk_matrimonio_3`
FOREIGN KEY (`certificado`)
REFERENCES `mydb`.`certificado` (`idcertificado`)
ON DELETE NO ACTION
ON UPDATE NO ACTION)
ENGINE = InnoDB;
-- -----------------------------------------------------
-- Table `mydb`.`DPI1`
-- -----------------------------------------------------
DROP TABLE IF EXISTS `mydb`.`DPI1` ;
CREATE TABLE IF NOT EXISTS `mydb`.`DPI1` (
`inc` INT NOT NULL AUTO_INCREMENT,
PRIMARY KEY (`inc`))
ENGINE = InnoDB;
-- -----------------------------------------------------
-- Table `mydb`.`DPI2`
-- -----------------------------------------------------
DROP TABLE IF EXISTS `mydb`.`DPI2` ;
CREATE TABLE IF NOT EXISTS `mydb`.`DPI2` (
`inc` INT NOT NULL AUTO_INCREMENT,
PRIMARY KEY (`inc`))
ENGINE = InnoDB;
-- -----------------------------------------------------
-- Table `mydb`.`DPI3`
-- -----------------------------------------------------
DROP TABLE IF EXISTS `mydb`.`DPI3` ;
CREATE TABLE IF NOT EXISTS `mydb`.`DPI3` (
`inc` INT NOT NULL AUTO_INCREMENT,
PRIMARY KEY (`inc`))
ENGINE = InnoDB;
-- -----------------------------------------------------
-- Table `mydb`.`verificadores`
-- -----------------------------------------------------
DROP TABLE IF EXISTS `mydb`.`verificadores` ;
CREATE TABLE IF NOT EXISTS `mydb`.`verificadores` (
`inc` INT NOT NULL AUTO_INCREMENT,
PRIMARY KEY (`inc`))
ENGINE = InnoDB;
-- -----------------------------------------------------
-- Table `mydb`.`correlativos`
-- -----------------------------------------------------
DROP TABLE IF EXISTS `mydb`.`correlativos` ;
CREATE TABLE IF NOT EXISTS `mydb`.`correlativos` (
`inc` INT NOT NULL AUTO_INCREMENT,
PRIMARY KEY (`inc`))
ENGINE = InnoDB;
SET SQL_MODE=@OLD_SQL_MODE;
SET FOREIGN_KEY_CHECKS=@OLD_FOREIGN_KEY_CHECKS;
SET UNIQUE_CHECKS=@OLD_UNIQUE_CHECKS;
-- -----------------------------------------------------
-- Data for table `mydb`.`estado`
-- -----------------------------------------------------
START TRANSACTION;
USE `mydb`;
INSERT INTO `mydb`.`estado` (`idestado`, `nombre`) VALUES (1, 'DEFAULT');
INSERT INTO `mydb`.`estado` (`idestado`, `nombre`) VALUES (2, 'EN_QUIEBRA');
INSERT INTO `mydb`.`estado` (`idestado`, `nombre`) VALUES (3, 'MUERTO');
COMMIT;
-- -----------------------------------------------------
-- Data for table `mydb`.`tipo_certificado`
-- -----------------------------------------------------
START TRANSACTION;
USE `mydb`;
INSERT INTO `mydb`.`tipo_certificado` (`idtipo_certificado`, `nombre`) VALUES (NULL, 'NACIMIENTO');
INSERT INTO `mydb`.`tipo_certificado` (`idtipo_certificado`, `nombre`) VALUES (NULL, 'MATRIMONIO');
INSERT INTO `mydb`.`tipo_certificado` (`idtipo_certificado`, `nombre`) VALUES (NULL, 'DEFUNCION');
COMMIT;
-- -----------------------------------------------------
-- Data for table `mydb`.`DPI1`
-- -----------------------------------------------------
START TRANSACTION;
USE `mydb`;
INSERT INTO `mydb`.`DPI1` (`inc`) VALUES (null);
INSERT INTO `mydb`.`DPI1` (`inc`) VALUES (null);
INSERT INTO `mydb`.`DPI1` (`inc`) VALUES (null);
INSERT INTO `mydb`.`DPI1` (`inc`) VALUES (null);
INSERT INTO `mydb`.`DPI1` (`inc`) VALUES (null);
INSERT INTO `mydb`.`DPI1` (`inc`) VALUES (null);
INSERT INTO `mydb`.`DPI1` (`inc`) VALUES (null);
COMMIT;
-- -----------------------------------------------------
-- Data for table `mydb`.`DPI2`
-- -----------------------------------------------------
START TRANSACTION;
USE `mydb`;
INSERT INTO `mydb`.`DPI2` (`inc`) VALUES (null);
INSERT INTO `mydb`.`DPI2` (`inc`) VALUES (null);
INSERT INTO `mydb`.`DPI2` (`inc`) VALUES (null);
INSERT INTO `mydb`.`DPI2` (`inc`) VALUES (null);
COMMIT;
-- -----------------------------------------------------
-- Data for table `mydb`.`DPI3`
-- -----------------------------------------------------
START TRANSACTION;
USE `mydb`;
INSERT INTO `mydb`.`DPI3` (`inc`) VALUES (null);
COMMIT;
-- -----------------------------------------------------
-- Data for table `mydb`.`verificadores`
-- -----------------------------------------------------
START TRANSACTION;
USE `mydb`;
INSERT INTO `mydb`.`verificadores` (`inc`) VALUES (null);
INSERT INTO `mydb`.`verificadores` (`inc`) VALUES (null);
INSERT INTO `mydb`.`verificadores` (`inc`) VALUES (null);
INSERT INTO `mydb`.`verificadores` (`inc`) VALUES (null);
COMMIT;
|
--CREATE TABLE purchases (
--id uuid CONSTRAINT id_constraint PRIMARY KEY,
--client_name varchar(255),
--euros_spent integer,
--fidelity_points_earned integer,
--purchase_date timestamp,
--number_of_items integer);
-- • Find the three oldest client's name
select purchase_date,client_name from purchases
ORDER BY purchase_date ASC
LIMIT 3
-- • Find all clients that have not made a purchase in the last two months
select purchase_date,client_name from purchases where purchase_date > (current_date-60)
ORDER BY purchase_date,client_name ASC
-- • Find all clients that have not made a purchase in the last month but are big customer (have purchased more than 3 items in one purchase previously)
select purchase_date,client_name,number_of_items from purchases where purchase_date > (current_date-30) and number_of_items > 3
ORDER BY purchase_date,client_name ASC
-- • Find the best client (the one who spent the most money in one purchase)
select euros_spent, purchase_date,client_name,number_of_items from purchases
ORDER BY euros_spent DESC
-- • BONUS, find how much money our store made in the summer
select SUM (euros_spent) from purchases
where (purchase_date > '30/06/2017') and (purchase_date < '01/09/2017')
|
drop table recommendations;
create table recommendations
( RECNO number(3),
USERNO varchar2(25),
QUES varchar2(150),
A1 varchar2(30),
A2 varchar2(30),
A3 varchar2(30),
A4 varchar2(30),
CORRECTANS varchar2(30),
TOPICNO number(3),
primary key (RECNO)
); |
USE employees
SELECT emp_no, first_name, last_name, hire_date
FROM employees JOIN titles USING (emp_no)
WHERE title = 'Assistant Engineer'
AND hire_date < ANY (SELECT hire_date FROM
employees JOIN titles USING (emp_no)
WHERE title = 'Manager');
SELECT hire_date FROM
employees JOIN titles USING (emp_no)
WHERE title = 'Manager';
SELECT emp_no, first_name, last_name
FROM employees JOIN titles USING (emp_no)
WHERE title = 'Manager'
AND emp_no = ANY (SELECT emp_no FROM employees
JOIN titles USING (emp_no) WHERE
title <> 'Manager');
SELECT emp_no, first_name, last_name
FROM employees JOIN titles USING (emp_no)
WHERE title = 'Manager'
AND emp_no IN (SELECT emp_no FROM employees
JOIN titles USING (emp_no) WHERE
title <> 'Manager');
SELECT DISTINCT emp_no, first_name, last_name
FROM employees JOIN titles mgr USING (emp_no)
JOIN titles nonmgr USING (emp_no)
WHERE mgr.title = 'Manager'
AND nonmgr.title <> 'Manager';
|
-- modify column text default ''
-- add column vcs_rev_url text default ''
BEGIN TRANSACTION;
DROP INDEX i_project_name_project;
ALTER TABLE project RENAME TO project_orig;
CREATE TABLE project (
id INTEGER PRIMARY KEY AUTOINCREMENT,
name TEXT NOT NULL,
start_date TEXT DEFAULT '',
public INTEGER DEFAULT 1,
enable_feed INTEGER DEFAULT 1,
default_platform TEXT DEFAULT '',
default_arch TEXT DEFAULT '',
graph_start TEXT DEFAULT 'project',
allow_anon INTEGER DEFAULT 0,
max_reports INTEGER DEFAULT 100,
extra_css TEXT DEFAULT '',
vcs_rev_url TEXT DEFAULT ''
);
INSERT INTO project SELECT *, '' FROM project_orig;
CREATE UNIQUE INDEX i_project_name_project on project (name);
COMMIT;
-- modify column added text default ''
BEGIN TRANSACTION;
DROP INDEX i_project_smoke_report;
DROP INDEX i_developer_smoke_report;
ALTER TABLE smoke_report RENAME TO smoke_report_orig;
CREATE TABLE smoke_report (
id INTEGER PRIMARY KEY AUTOINCREMENT,
project INTEGER NOT NULL,
developer INTEGER NOT NULL,
added TEXT DEFAULT '',
architecture TEXT DEFAULT '',
platform TEXT DEFAULT '',
pass INTEGER DEFAULT 0,
fail INTEGER DEFAULT 0,
skip INTEGER DEFAULT 0,
todo INTEGER DEFAULT 0,
todo_pass INTEGER DEFAULT 0,
test_files INTEGER DEFAULT 0,
total INTEGER DEFAULT 0,
comments BLOB DEFAULT '',
invalid INTEGER DEFAULT 0,
invalid_reason BLOB DEFAULT '',
duration INTEGER DEFAULT 0,
purged INTEGER DEFAULT 0,
failed INTEGER DEFAULT 0,
revision TEXT DEFAULT '',
CONSTRAINT 'fk_smoke_report_project' FOREIGN KEY ('project') REFERENCES 'project' ('id') ON DELETE CASCADE,
CONSTRAINT 'fk_smoke_report_developer' FOREIGN KEY ('developer') REFERENCES 'developer' ('id') ON DELETE CASCADE
);
INSERT INTO smoke_report SELECT * FROM smoke_report_orig;
CREATE INDEX i_project_smoke_report ON smoke_report (project);
CREATE INDEX i_developer_smoke_report ON smoke_report (developer);
COMMIT;
|
CREATE PROCEDURE netIncome()
BEGIN
SELECT
YEAR(date) AS year,
QUARTER(date) AS quarter,
SUM(CAST(profit AS SIGNED)-CAST(loss AS SIGNED)) AS net_profit
FROM accounting
GROUP BY year, quarter;
END
|
-- 객실
CREATE TABLE PMS_ROOM (
ID BIGINT NOT NULL COMMENT 'ID', -- ID
ROOM_NUM VARCHAR(10) NOT NULL DEFAULT '' COMMENT '객실 번호', -- 객실 번호
ROOM_TYP_CD VARCHAR(20) NOT NULL COMMENT '객실 타입 CD', -- 객실 타입 CD
DND_YN VARCHAR(1) NOT NULL DEFAULT 'N' COMMENT 'DND 여부', -- DND 여부
EB_YN VARCHAR(1) NOT NULL DEFAULT 'N' COMMENT 'EB 여부', -- EB 여부
ROOM_STTUS_CD VARCHAR(20) NULL COMMENT '객실 상태 CD', -- 객실 상태 CD
CLN_STTUS_CD VARCHAR(20) NULL COMMENT '청소 상태 CD', -- 청소 상태 CD
SVC_STTUS_CD VARCHAR(20) NULL COMMENT '서비스 상태 CD', -- 서비스 상태 CD
CREATED_AT TIMESTAMP NULL COMMENT '등록일', -- 등록일
CREATED_BY VARCHAR(100) NULL COMMENT '등록자', -- 등록자
UPDATED_AT TIMESTAMP NULL COMMENT '변경일', -- 변경일
UPDATED_BY VARCHAR(100) NULL COMMENT '변경자' -- 변경자
);
-- 객실 유니크 인덱스
CREATE UNIQUE INDEX UIX_PMS_ROOM
ON PMS_ROOM ( -- 객실
ID ASC -- ID
);
-- 객실 유니크 인덱스2
CREATE UNIQUE INDEX UIX_PMS_ROOM2
ON PMS_ROOM ( -- 객실
ROOM_NUM ASC -- 객실 번호
);
ALTER TABLE PMS_ROOM
MODIFY COLUMN ID BIGINT NOT NULL AUTO_INCREMENT COMMENT 'ID'; |
create or replace view v1_hdcg050_zb as
(
select a.*,
(select de151 from hdjh004 b where a.czde397 = b.czde397) as lxtzsbh,
(select de151 from hdcg005 b where a.czde413 = b.czde413) as zbbh from hdcg050 a);
|
TRUNCATE TABLE `bank_holiday`;
TRUNCATE TABLE `holiday`;
TRUNCATE TABLE `note`;
TRUNCATE TABLE `sys_note`;
TRUNCATE TABLE `pattern`;
TRUNCATE TABLE `sys_pattern`;
TRUNCATE TABLE `settings`;
DELETE FROM `user` WHERE 1;
SET SQL_MODE = "NO_AUTO_VALUE_ON_ZERO";
SET time_zone = "+00:00";
# user must be created first due to foreign key constraints
--
-- Dumping data for table `user`
--
INSERT INTO `user` (`id`, `username`, `role`, `email`, `password`) VALUES
(1, 'dans', 'admin', 'dan@post.cz', 'daAyVm43mRrWw');
-- --------------------------------------------------------
--
-- Dumping data for table `holiday`
--
INSERT INTO `holiday` (`date`, `halfday`, `user_id`) VALUES
('2013-02-05', '1', 1),
('2014-02-03', '1', 1),
('2014-09-08', '1', 1),
('2014-09-09', '0', 1),
('2014-09-10', '0', 1),
('2014-09-11', '0', 1),
('2014-09-12', '0', 1),
('2014-09-13', '0', 1),
('2014-09-14', '0', 1),
('2014-09-15', '0', 1),
('2014-09-16', '0', 1),
('2014-09-17', '0', 1),
('2014-09-18', '0', 1);
-- --------------------------------------------------------
INSERT INTO `settings` (`id`, `value`) VALUES
('holiday.credits', 'i:33;'),
('holiday.yearStart', 's:5:"04-01";');
|
--1. Scrieti o interogare ce ar afisa: numele, prenumele, functia, localitatea angajatului, care a incheiat contractul de cea mai mare sumă
SELECT a.nume,
a.prenume,
a.functia,
p.pret*t.cantitatea AS contract,
o.localitatea
FROM produse p
JOIN tranzactii t ON p.cod_produs = t.cod_produs
JOIN angajati a ON a.cod_angajat = t.cod_vanzator
JOIN oficii o ON a.cod_oficiu = o.cod_oficiu
WHERE p.pret*t.cantitatea = (SELECT MAX(pret*cantitatea)
FROM produse
JOIN tranzactii ON produse.cod_produs = tranzactii.cod_produs);
--2. Scrieti o interogare ce ar afisa compania ce a incheiat contractul de cea mai mică sumă, precum si numele, prenumele reprezentatului ei.
SELECT c.compania,
a.nume,
a.prenume,
p.pret*t.cantitatea AS contract
FROM companii c
JOIN tranzactii t ON t.cod_client = c.cod_companie
JOIN angajati a ON a.cod_angajat = c.reprezentant_companie
JOIN produse p ON p.cod_produs = t.cod_produs
WHERE p.pret*t.cantitatea = (SELECT MIN(pret*cantitatea)
FROM produse
JOIN tranzactii ON produse.cod_produs = tranzactii.cod_produs);
--3. Scrieti o interogare ce ar afisa denumirea companiilor, ce participă la tranzactii si numărul de tranzactii realizate de companie
SELECT c.compania,
COUNT(t.cod_client) AS nr_tranzactii
FROM companii c
JOIN tranzactii t ON c.cod_companie = t.cod_client
GROUP BY c.compania;
|
#------------------------------------
###1
#a
select * from film f
where f.titre = 'Speed 2';
#b
select * from programme p
inner join film f on f.titre = p.titre and f.titre = 'Eyes wide shut'
and p.horaire > time('14:00:00');
#c
select distinct * from film f
where f.metteur_en_scene = f.acteur;
#d
select * from programme p
inner join film f on f.titre = p.titre
and (f.titre = 'Marion' or p.cinema = 'Diagonal Centre');
#e
select distinct p.titre from programme p
inner join film f on p.titre = f.titre and f.acteur = 'MF Pisier';
#f
select distinct f.metteur_en_scene from film f
inner join film f1 on f1.acteur = f.metteur_en_scene;
#g
select distinct f.titre from film f
inner join film f1 on f1.titre = f.titre and f1.metteur_en_scene <> f.metteur_en_scene;
#h
select distinct personne from(
select distinct f.acteur personne from film f
where f.titre = 'Marion'
union
select distinct f.metteur_en_scene personne from film f
where titre = 'Marion'
);
#------------------------------------
use dbdragon;
### 2
#a
select d.dragon from dragons d
where d.feu = true;
#b
select d.dragon from dragons d
where d.feu = true and d.sexe = 'M';
#c
select d.dragon from dragons d
where d.feu = false and d.sexe = 'F';
#d
select d.dragon from dragons d
inner join aime a on a.dragonaimant = d.dragon or a.dragonaime = d.dragon;
#e
select a.dragonaimant, a.dragonaime from aime a
inner join dragons d on d.dragon = a.dragonaimant
and a.force_amour = 'passionnément';
#f
select d.dragon from dragons d
inner join repas r on r.dragon = d.dragon and r.produit = 'œuf';
#g
select d.dragon from dragons d
left join aime a on d.dragon = a.dragonaimant
where a.dragonaimant is null;
#h
select distinct a1.dragonaimant, a1.dragonaime from dragons d
inner join aime a on a.dragonaimant = d.dragon
inner join aime a1 on a1.dragonaime = d.dragon and a1.dragonaimant = a.dragonaime;
#i
select d.dragon from dragons d
left join repas r on r.dragon = d.dragon
where r.dragon is null;
#j
select d.dragon from dragons d
left join aime a on a.dragonaimant = d.dragon
left join repas r on r.dragon = d.dragon
where a.dragonaimant is null and r.dragon is null;
#k
select distinct d.dragon from dragons d
inner join repas r on r.dragon = d.dragon and
(select 1 from repas r1
where r1.dragon = d.dragon and r1.produit <> r.produit limit 1);
#------------------------------------
###3
use cl_fourn;
#a
select distinct p.nomp from commandes c
inner join clients cl on cl.nomc = 'Jean' and cl.nomc = c.nomc
inner join prix p on p.nomp = c.nomp;
#b
select distinct f.nomf from commandes c
inner join clients cl on cl.nomc = 'Paul' and cl.nomc = c.nomc
inner join prix p on p.nomp = c.nomp
inner join fournisseurs f on f.nomf = p.nomf;
#c
select f.adressef from fournisseurs f
inner join prix p on p.nomf = f.nomf and p.nomp = 'parpaing' and p.couts < 1200;
#d
select cl.nomc, cl.adressec, f.nomf, f.adressef from commandes c
inner join prix p on p.nomp = 'briques' and p.nomp = c.nomp
inner join fournisseurs f on f.nomf = p.nomf
inner join clients cl on cl.nomc = c.nomc;
#e
select distinct f.nomf from commandes c
inner join clients cl on cl.nomc = 'Jean' and cl.nomc = c.nomc
inner join prix p on p.nomp = c.nomp
inner join fournisseurs f on f.nomf = p.nomf;
#------------------------------------
###4
use dbtheatre;
#a
select distinct i.intervenant from spectacles s
inner join intervenants i on i.titre like 'L\'avare' and i.titre = s.titre;
#b
select distinct i.intervenant from spectacles s
inner join intervenants i on i.intervenant not in
(select i1.intervenant from intervenants i1
where i1.titre = 'L\'avare');
#c
select i.intervenant from spectacles s
inner join intervenants i on i.titre = s.titre
inner join salles sa on sa.nombreplaces > 200 and sa.salle = s.salle;
#d
select distinct sa.salle from spectacles s
inner join salles sa on sa.salle = s.salle
group by sa.salle
having count(distinct s.semaine) < (select count(s1.semaine) from spectacles s1);
#e
select s.titre, p.semaine, p.jour from spectacles s
inner join intervenants i on i.intervenant = 'Pierre' and i.titre = s.titre
inner join places p on p.salle = s.salle and p.semaine = s.semaine and p.disponibilite > 0;
#f
select i.intervenant from spectacles s
inner join intervenants i on i.titre = s.titre
group by i.intervenant
having count(distinct s.salle) = (select count(sa1.salle) from salles sa1);
#------------------------------------
###5
#a
select f.bar from frequente f
where f.personne = 'Charles Dupont';
#b
select f.bar from sert s
inner join aime a on a.personne = 'Charles Dupont' and a.biere = s.biere
inner join frequente f on f.bar = s.bar and f.personne = a.personne;
#c
select distinct a.personne from frequente f
inner join aime a on a.personne = f.personne
inner join sert s on s.biere = s.biere and s.bar = f.bar;
#d
select f.personne, f1.personne from frequente f
inner join frequente f1 on f1.bar = f.bar and f.personne <> f1.personne;
#e
select v.biere, sum(v.montant) from vente v
group by v.biere
order by (sum(v.montant)) desc;
#f
select v.bar, v.biere, avg(v.montant) from vente v
group by v.bar, v.biere;
#g
select v.bar, v.biere, max(v.montant) from vente v
inner join vente v1 on v1.biere = v.biere and v.bar <> v1.bar
group by v.bar, v.biere;
#h
select a.personne, count(a.biere) from aime a
group by a.personne
order by count(a.biere);
#i
|
drop table if exists imgs, users, posts; |
CREATE PROCEDURE spr_list_rejections_pidilite (@FROMDATE datetime,
@TODATE datetime)
AS
SELECT GRNDetail.Product_Code, "Item Code" = GRNDetail.Product_Code,
"Item Name" = Items.ProductName,
"Rejection" = SUM(GRNDetail.QuantityRejected),
"Reporting UOM" = SUM(GRNDetail.QuantityRejected / Case IsNull(ReportingUnit, 1) When 0 Then 1 Else IsNull(ReportingUnit, 1) End),
"Conversion Factor" = SUM(GRNDetail.QuantityRejected * IsNull(ConversionFactor, 0))
FROM GRNAbstract, GRNDetail, Items
WHERE GRNAbstract.GRNID = GRNDetail.GRNID AND
GRNDetail.Product_Code = Items.Product_Code AND
GRNAbstract.GRNDate BETWEEN @FROMDATE AND @TODATE
AND (GRNAbstract.GRNStatus & 64) = 0
AND (GRNAbstract.GRNStatus & 32) = 0
GROUP BY GRNDetail.Product_Code, Items.ProductName
HAVING SUM(GRNDetail.QuantityRejected) > 0
ORDER BY GRNDetail.Product_Code
|
-- phpMyAdmin SQL Dump
-- version 4.8.0.1
-- https://www.phpmyadmin.net/
--
-- Host: 127.0.0.1
-- Generation Time: Jun 18, 2018 at 09:56 AM
-- Server version: 10.1.32-MariaDB
-- PHP Version: 5.6.36
SET SQL_MODE = "NO_AUTO_VALUE_ON_ZERO";
SET AUTOCOMMIT = 0;
START TRANSACTION;
SET time_zone = "+00:00";
/*!40101 SET @OLD_CHARACTER_SET_CLIENT=@@CHARACTER_SET_CLIENT */;
/*!40101 SET @OLD_CHARACTER_SET_RESULTS=@@CHARACTER_SET_RESULTS */;
/*!40101 SET @OLD_COLLATION_CONNECTION=@@COLLATION_CONNECTION */;
/*!40101 SET NAMES utf8mb4 */;
--
-- Database: `mediawareonline`
--
-- --------------------------------------------------------
--
-- Table structure for table `city`
--
CREATE TABLE `city` (
`id` int(11) NOT NULL,
`name` varchar(255) NOT NULL,
`district` int(11) NOT NULL,
`longitude` varchar(255) NOT NULL,
`latitude` varchar(255) NOT NULL,
`description` varchar(255) NOT NULL
) ENGINE=InnoDB DEFAULT CHARSET=latin1;
--
-- Dumping data for table `city`
--
INSERT INTO `city` (`id`, `name`, `district`, `longitude`, `latitude`, `description`) VALUES
(1, 'Rajkot', 1, '22.3039', '70.8022', 'This is Rajkot Description'),
(2, 'Morbi', 1, '22.8120', '70.8236', 'This is Morbi Description'),
(3, 'Jamnagar', 3, '22.4707', '70.0577', 'This is Jamnagar Description'),
(4, 'JK', 3, '22.2053', '69.6588', 'This is JK Description');
-- --------------------------------------------------------
--
-- Table structure for table `district`
--
CREATE TABLE `district` (
`id` int(11) NOT NULL,
`name` varchar(255) NOT NULL,
`state` int(11) NOT NULL
) ENGINE=InnoDB DEFAULT CHARSET=latin1;
--
-- Dumping data for table `district`
--
INSERT INTO `district` (`id`, `name`, `state`) VALUES
(1, 'Rajkot', 2),
(2, 'Ahmedabad', 2),
(3, 'Jamnagar', 2),
(4, 'Amreli', 2),
(5, 'Thane', 1),
(6, 'Nashik', 1);
-- --------------------------------------------------------
--
-- Table structure for table `state`
--
CREATE TABLE `state` (
`id` int(11) NOT NULL,
`name` varchar(255) NOT NULL
) ENGINE=InnoDB DEFAULT CHARSET=latin1;
--
-- Dumping data for table `state`
--
INSERT INTO `state` (`id`, `name`) VALUES
(1, 'Maharashtra'),
(2, 'Gujarat'),
(3, 'MP'),
(4, 'Rajasthan');
-- --------------------------------------------------------
--
-- Table structure for table `user`
--
CREATE TABLE `user` (
`id` int(11) NOT NULL,
`username` varchar(255) NOT NULL,
`password` varchar(255) NOT NULL,
`latestLogin` text NOT NULL,
`createdDate` varchar(32) NOT NULL,
`updatedDate` varchar(32) NOT NULL
) ENGINE=InnoDB DEFAULT CHARSET=latin1;
--
-- Dumping data for table `user`
--
INSERT INTO `user` (`id`, `username`, `password`, `latestLogin`, `createdDate`, `updatedDate`) VALUES
(1, 'aliasgar.vanak', 'YWJjMTIz', 'ec48f818', '', ''),
(2, 'aliasgar.vanak@gmail.com', 'l8iJ5q96V4', '', '', '');
--
-- Indexes for dumped tables
--
--
-- Indexes for table `city`
--
ALTER TABLE `city`
ADD PRIMARY KEY (`id`);
--
-- Indexes for table `district`
--
ALTER TABLE `district`
ADD PRIMARY KEY (`id`);
--
-- Indexes for table `state`
--
ALTER TABLE `state`
ADD PRIMARY KEY (`id`);
--
-- Indexes for table `user`
--
ALTER TABLE `user`
ADD PRIMARY KEY (`id`);
--
-- AUTO_INCREMENT for dumped tables
--
--
-- AUTO_INCREMENT for table `city`
--
ALTER TABLE `city`
MODIFY `id` int(11) NOT NULL AUTO_INCREMENT, AUTO_INCREMENT=5;
--
-- AUTO_INCREMENT for table `district`
--
ALTER TABLE `district`
MODIFY `id` int(11) NOT NULL AUTO_INCREMENT, AUTO_INCREMENT=7;
--
-- AUTO_INCREMENT for table `state`
--
ALTER TABLE `state`
MODIFY `id` int(11) NOT NULL AUTO_INCREMENT, AUTO_INCREMENT=5;
--
-- AUTO_INCREMENT for table `user`
--
ALTER TABLE `user`
MODIFY `id` int(11) NOT NULL AUTO_INCREMENT, AUTO_INCREMENT=3;
COMMIT;
/*!40101 SET CHARACTER_SET_CLIENT=@OLD_CHARACTER_SET_CLIENT */;
/*!40101 SET CHARACTER_SET_RESULTS=@OLD_CHARACTER_SET_RESULTS */;
/*!40101 SET COLLATION_CONNECTION=@OLD_COLLATION_CONNECTION */;
|
SET FOREIGN_KEY_CHECKS=0;
INSERT INTO `core_DBversion` VALUES ('3', '2', '2', '2008-10-16 16:44:45');
CREATE TABLE `core_SystemMessageMaster` (
`MessageID` int(10) unsigned NOT NULL auto_increment,
`Title` varchar(75) default NULL,
`Content` text NOT NULL,
`StartDate` datetime default NULL,
`EndDate` datetime default NULL,
`IsAdminOnly` tinyint(4) NOT NULL default '0',
PRIMARY KEY (`MessageID`)
) ENGINE=InnoDB DEFAULT CHARSET=utf8;
CREATE TABLE `core_SystemMessageReadLog` (
`MessageID` int(10) unsigned NOT NULL,
`UserID` int(10) unsigned NOT NULL,
PRIMARY KEY (`MessageID`,`UserID`),
KEY `IDX_SystemMessageReadLog_UserID` (`UserID`),
CONSTRAINT `FK_SystemMessageReadLog_SystemMessageMaster` FOREIGN KEY (`MessageID`) REFERENCES `core_SystemMessageMaster` (`MessageID`),
CONSTRAINT `FK_SystemMessageReadLog_UserMaster` FOREIGN KEY (`UserID`) REFERENCES `core_UserMaster` (`UserID`)
) ENGINE=InnoDB DEFAULT CHARSET=utf8;
|
CREATE TABLE schools (
-- Creating ID to make a relationship
id INTEGER PRIMARY KEY AUTOINCREMENT,
name VARCHAR(100),
adrees VARCHAR(255),
principal VARCHAR(80),
enrollment INTEGER,
dbn VARCHAR(6) NOT NULL UNIQUE
/* Can I write comments? */
);
CREATE TABLE students(
id INTEGER PRIMARY KEY AUTOINCREMENT,
name VARCHAR(100) NOT NULL,
address VARCHAR(255) NOT NULL,
phone_number VARCHAR(10) NOT NULL,
-- Don't need to do math with phone numbers
dob DATE,
-- Don't care about time, just date "2015-07-24"
student_number VARCHAR(9) NOT NULL,
gender VARCHAR(1),
ethnicity VARCHAR(10) NOT NULL,
-- school VARCHAR(6) NOT NULL UNIQUE,
school_id INTEGER,
grade INTEGER,
is_graduated BOOLEAN,
iep BOOLEAN,
FOREIGN KEY(school_id) REFERENCES schools(id)
);
CREATE TABLE teachers(
id INTEGER PRIMARY KEY AUTOINCREMENT,
name VARCHAR(255)
);
CREATE TABLE courses(
id INTEGER PRIMARY KEY AUTOINCREMENT,
name VARCHAR(255),
teacher_id INTEGER,
FOREIGN KEY(teacher_id) REFERENCES teachers(id)
);
CREATE TABLE courses_students(
id INTEGER PRIMARY KEY AUTOINCREMENT,
student_id INTEGER,
course_id INTEGER,
FOREIGN KEY(student_id) REFERENCES students(id),
FOREIGN KEY(course_id) REFERENCES courses(id)
);
|
CREATE DATABASE psychomorph;
USE psychomorph;
\. /var/www/html/webmorph/resources/mysql/db.sql
\. /var/www/html/webmorph/resources/mysql/tems.sql
-- CREATE TABLE `user` (
-- `id` int(8) unsigned NOT NULL AUTO_INCREMENT,
-- `email` varchar(255) NOT NULL,
-- `password` varchar(255) NOT NULL,
-- `organisation` varchar(255) DEFAULT NULL,
-- `sex` enum('female','male','other') DEFAULT NULL,
-- `research` tinyint(1) DEFAULT NULL,
-- `personal` tinyint(1) DEFAULT NULL,
-- `business` tinyint(1) DEFAULT NULL,
-- `art` tinyint(1) DEFAULT NULL,
-- `regdate` datetime DEFAULT NULL,
-- `school` tinyint(1) DEFAULT NULL,
-- `firstname` varchar(255) DEFAULT NULL,
-- `lastname` varchar(255) DEFAULT NULL,
-- `pca` tinyint(1) DEFAULT '0',
-- `allocation` int(8) unsigned DEFAULT '1024',
-- PRIMARY KEY (`id`),
-- UNIQUE KEY `email` (`email`)
-- ) ENGINE=MyISAM AUTO_INCREMENT=91 DEFAULT CHARSET=latin1;
INSERT INTO user(id, email, password, organisation, sex, research, personal, business, art, regdate, school, firstname, lastname, pca, allocation)
VALUES ('12345678', 'default@example.com', 'default123', NULL, NULL, NULL, NULL, NULL, NULL, NULL, NULL, NULL, NULL, 0, 1024) |
-- phpMyAdmin SQL Dump
-- version 4.8.2
-- https://www.phpmyadmin.net/
--
-- Host: 127.0.0.1
-- Generation Time: Sep 08, 2019 at 12:06 PM
-- Server version: 10.1.34-MariaDB
-- PHP Version: 5.6.37
SET SQL_MODE = "NO_AUTO_VALUE_ON_ZERO";
SET AUTOCOMMIT = 0;
START TRANSACTION;
SET time_zone = "+00:00";
/*!40101 SET @OLD_CHARACTER_SET_CLIENT=@@CHARACTER_SET_CLIENT */;
/*!40101 SET @OLD_CHARACTER_SET_RESULTS=@@CHARACTER_SET_RESULTS */;
/*!40101 SET @OLD_COLLATION_CONNECTION=@@COLLATION_CONNECTION */;
/*!40101 SET NAMES utf8mb4 */;
--
-- Database: `parkertypes`
--
CREATE DATABASE IF NOT EXISTS `parkertypes` DEFAULT CHARACTER SET latin1 COLLATE latin1_swedish_ci;
USE `parkertypes`;
-- --------------------------------------------------------
--
-- Table structure for table `bfct_types`
--
DROP TABLE IF EXISTS `bfct_types`;
CREATE TABLE `bfct_types` (
`ptypeID` int(11) NOT NULL,
`parkertype` varchar(2) NOT NULL,
`ptypename` varchar(12) NOT NULL,
`ptypedesc` varchar(24) NOT NULL,
`btnimg` varchar(128) NOT NULL,
`ACTIVE` tinyint(1) NOT NULL DEFAULT '0',
`numOfReceipts` tinyint(1) NOT NULL DEFAULT '0',
`Discounted` tinyint(1) NOT NULL DEFAULT '0',
`DiscountPercentage` double NOT NULL
) ENGINE=InnoDB DEFAULT CHARSET=latin1;
--
-- Dumping data for table `bfct_types`
--
INSERT INTO `bfct_types` (`ptypeID`, `parkertype`, `ptypename`, `ptypedesc`, `btnimg`, `ACTIVE`, `numOfReceipts`, `Discounted`, `DiscountPercentage`) VALUES
(1, 'R', 'Bus', 'P250 Loading', 'http://127.0.0.1/img/bus.png', 1, 1, 0, 0),
(2, 'V', 'VIP', 'Free Parking', 'http://127.0.0.1/img/vip.png', 1, 1, 0, 0),
(3, 'UB', 'UnloadingBus', 'P100 Unloading', 'http://127.0.0.1/img/delivery.png', 0, 1, 0, 0),
(4, 'G', 'GracePeriod', '', 'http://127.0.0.1/img/generic.png', 1, 1, 0, 0),
(5, 'L', 'Lost', 'P50 plus P200', 'http://127.0.0.1/img/lost.png', 1, 1, 0, 0),
(6, 'C', 'Cars', 'Free if Validated', 'http://127.0.0.1/img/retail.png', 1, 1, 0, 0),
(7, 'Q', 'Senior', 'Free for Senior', 'http://127.0.0.1/img/qcsenior.png', 0, 2, 1, 100),
(8, 'NQ', 'NonQCSenior', 'Discounted 20%', 'http://127.0.0.1/img/senior.png', 1, 2, 1, 20),
(9, 'PW', 'PWD', 'Discounted 20%', 'http://127.0.0.1/img/pwd.png', 1, 2, 1, 20),
(10, 'M', 'Motorcycle', 'Motorcycles', 'http://127.0.0.1/img/motorcycle.png', 1, 1, 0, 0),
(11, 'D', 'Delivery', 'Delivery Parking', 'http://127.0.0.1/img/delivery.png', 1, 1, 0, 0),
(12, 'T', 'Trucks', 'Trucks', 'http://127.0.0.1/img/trucks.png', 1, 1, 0, 0);
-- --------------------------------------------------------
--
-- Table structure for table `bir_main`
--
DROP TABLE IF EXISTS `bir_main`;
CREATE TABLE `bir_main` (
`ptypeID` int(11) NOT NULL,
`parkertype` varchar(2) NOT NULL,
`ptypename` varchar(12) NOT NULL,
`ptypedesc` varchar(24) NOT NULL,
`btnimg` varchar(128) NOT NULL,
`ACTIVE` tinyint(1) NOT NULL DEFAULT '0',
`numOfReceipts` tinyint(1) NOT NULL DEFAULT '0',
`Discounted` tinyint(1) NOT NULL DEFAULT '0',
`DiscountPercentage` double DEFAULT NULL
) ENGINE=InnoDB DEFAULT CHARSET=latin1;
--
-- Dumping data for table `bir_main`
--
INSERT INTO `bir_main` (`ptypeID`, `parkertype`, `ptypename`, `ptypedesc`, `btnimg`, `ACTIVE`, `numOfReceipts`, `Discounted`, `DiscountPercentage`) VALUES
(1, 'R', 'Regular', 'P250 Loading', 'http://127.0.0.1/img/retail.png', 1, 1, 0, 0),
(2, 'V', 'VIP', 'Free Parking', 'http://127.0.0.1/img/vip.png', 1, 1, 0, 0),
(4, 'G', 'GracePeriod', '', 'http://127.0.0.1/img/generic.png', 1, 1, 0, 0),
(5, 'L', 'Lost', 'P50 plus P200', 'http://127.0.0.1/img/lost.png', 1, 1, 0, 0),
(6, 'P', 'Promo', 'Free if Validated', 'http://127.0.0.1/img/promo.png', 1, 1, 0, 0),
(7, 'Q', 'QCSenior', 'Free for Senior', 'http://127.0.0.1/img/qcsenior.png', 1, 2, 1, 100),
(8, 'NQ', 'NonQCSenior', 'Discounted 20%', 'http://127.0.0.1/img/senior.png', 1, 2, 1, 20),
(9, 'PW', 'PWD', 'Discounted 20%', 'http://127.0.0.1/img/pwd.png', 1, 2, 1, 20),
(10, 'M', 'Motorcycle', 'Motorcycles', 'http://127.0.0.1/img/motorcycle.png', 1, 1, 0, 0),
(23, 'J', 'Jeep', 'Free for 1 hour', 'http://127.0.0.1/img/jeepney.png', 1, 1, 0, 0),
(24, 'TC', 'Tricycle', 'Free', 'http://127.0.0.1/img/tricycle.png', 1, 1, 0, 0),
(25, 'D', 'Delivery', 'Free for 1 hour', 'http://127.0.0.1/img/deliveryred.png', 1, 1, 0, 0),
(27, 'BC', 'BPOEmployee', 'Free for 24hours', 'http://127.0.0.1/img/bpo_car.png', 1, 1, 0, 0),
(28, 'EM', 'Employees', 'One Car Only Free', 'http://127.0.0.1/img/employee.png', 1, 1, 0, 0),
(29, 'TN', 'Tenants', 'One Car Only Free', 'http://127.0.0.1/img/tenant.png', 1, 1, 0, 0),
(30, 'VD', 'Voids', 'Void Parkers', 'http://127.0.0.1/img/', 1, 1, 0, 0);
-- --------------------------------------------------------
--
-- Table structure for table `bir_types`
--
DROP TABLE IF EXISTS `bir_types`;
CREATE TABLE `bir_types` (
`ptypeID` int(11) NOT NULL,
`parkertype` varchar(2) NOT NULL,
`ptypename` varchar(12) NOT NULL,
`ptypedesc` varchar(24) NOT NULL,
`btnimg` varchar(128) NOT NULL,
`ACTIVE` tinyint(1) NOT NULL DEFAULT '0',
`numOfReceipts` tinyint(1) NOT NULL DEFAULT '0',
`Discounted` tinyint(1) NOT NULL DEFAULT '0',
`DiscountPercentage` double NOT NULL
) ENGINE=InnoDB DEFAULT CHARSET=latin1;
--
-- Dumping data for table `bir_types`
--
INSERT INTO `bir_types` (`ptypeID`, `parkertype`, `ptypename`, `ptypedesc`, `btnimg`, `ACTIVE`, `numOfReceipts`, `Discounted`, `DiscountPercentage`) VALUES
(1, 'R', 'Regular', 'P250 Loading', 'http://127.0.0.1/img/bus.png', 1, 1, 0, 0),
(2, 'V', 'VIP', 'Free Parking', 'http://127.0.0.1/img/vip.png', 1, 1, 0, 0),
(3, 'UB', 'UnloadingBus', 'P100 Unloading', 'http://127.0.0.1/img/delivery.png', 0, 1, 0, 0),
(4, 'G', 'GracePeriod', '', 'http://127.0.0.1/img/generic.png', 1, 1, 0, 0),
(5, 'L', 'Lost', 'P50 plus P200', 'http://127.0.0.1/img/lost.png', 1, 1, 0, 0),
(6, 'P', 'Promo', 'Free if Validated', 'http://127.0.0.1/img/retail.png', 1, 1, 0, 0),
(7, 'Q', 'Senior', 'Free for Senior', 'http://127.0.0.1/img/qcsenior.png', 0, 2, 1, 100),
(8, 'NQ', 'NonQCSenior', 'Discounted 20%', 'http://127.0.0.1/img/senior.png', 1, 2, 1, 20),
(9, 'PW', 'PWD', 'Discounted 20%', 'http://127.0.0.1/img/pwd.png', 1, 2, 1, 20),
(10, 'M', 'Motorcycle', 'Motorcycles', 'http://127.0.0.1/img/motorcycle.png', 1, 1, 0, 0),
(11, 'D', 'Delivery', 'Delivery Parking', 'http://127.0.0.1/img/delivery.png', 1, 1, 0, 0),
(12, 'T', 'Trucks', 'Trucks', 'http://127.0.0.1/img/trucks.png', 1, 1, 0, 0);
-- --------------------------------------------------------
--
-- Table structure for table `cedar_types`
--
DROP TABLE IF EXISTS `cedar_types`;
CREATE TABLE `cedar_types` (
`ptypeID` int(11) NOT NULL,
`parkertype` varchar(2) NOT NULL,
`ptypename` varchar(12) NOT NULL,
`ptypedesc` varchar(24) NOT NULL,
`btnimg` varchar(128) NOT NULL,
`ACTIVE` tinyint(1) NOT NULL DEFAULT '0',
`numOfReceipts` tinyint(4) NOT NULL,
`Discounted` tinyint(4) NOT NULL,
`DiscountPercentage` double NOT NULL
) ENGINE=InnoDB DEFAULT CHARSET=latin1;
--
-- Dumping data for table `cedar_types`
--
INSERT INTO `cedar_types` (`ptypeID`, `parkertype`, `ptypename`, `ptypedesc`, `btnimg`, `ACTIVE`, `numOfReceipts`, `Discounted`, `DiscountPercentage`) VALUES
(1, 'R', 'Retail', 'P35 plus P25 succeeding', 'http://127.0.0.1/img/retail.png', 1, 1, 0, 0),
(2, 'V', 'VIP', 'Free Parking', 'http://127.0.0.1/img/vip.png', 0, 1, 0, 0),
(3, 'M', 'Motorcycle', 'P35 plus P25 succeeding', 'http://127.0.0.1/img/motorcycle.png', 1, 1, 0, 0),
(4, 'G', 'GracePeriod', '', 'http://127.0.0.1/img/generic.png', 0, 1, 0, 0),
(5, 'L', 'Lost', 'P50 plus P200', 'http://127.0.0.1/img/lost.png', 1, 1, 0, 0),
(6, 'D', 'Delivery', '1st 2hrs free. P100/hr', 'http://127.0.0.1/img/delivery.png', 0, 1, 0, 0),
(7, 'Q', 'Senior', '20% DSC Senior or PWD', 'http://127.0.0.1/img/senior.png', 1, 1, 0, 0),
(8, 'NQ', 'NonQCSenior', 'P50 First 10 Hours', 'http://127.0.0.1/img/bpo_car.png', 0, 1, 0, 0),
(9, 'BM', 'BPOMotor', 'P35 First 10 Hours', 'http://127.0.0.1/img/bpo_motor.png', 0, 1, 0, 0),
(10, 'P', 'Promo', 'Discounted', 'http://127.0.0.1/img/promo.png', 1, 1, 0, 0);
-- --------------------------------------------------------
--
-- Table structure for table `ever_types`
--
DROP TABLE IF EXISTS `ever_types`;
CREATE TABLE `ever_types` (
`ptypeID` int(11) NOT NULL,
`parkertype` varchar(2) NOT NULL,
`ptypename` varchar(12) NOT NULL,
`ptypedesc` varchar(24) NOT NULL,
`btnimg` varchar(128) NOT NULL,
`ACTIVE` tinyint(1) NOT NULL DEFAULT '0'
) ENGINE=InnoDB DEFAULT CHARSET=latin1;
--
-- Dumping data for table `ever_types`
--
INSERT INTO `ever_types` (`ptypeID`, `parkertype`, `ptypename`, `ptypedesc`, `btnimg`, `ACTIVE`) VALUES
(1, 'R', 'Retail', 'P50 First 10hrs', 'http://127.0.0.1/img/retail.png', 1),
(2, 'V', 'VIP', 'Free Parking', 'http://127.0.0.1/img/vip.png', 1),
(3, 'M', 'Motorcycle', 'P35 First 10 Hours', 'http://127.0.0.1/img/motorcycle.png', 1),
(4, 'G', 'GracePeriod', '', 'http://127.0.0.1/img/generic.png', 1),
(5, 'L', 'Lost', 'P50 plus P200', 'http://127.0.0.1/img/lost.png', 1),
(6, 'D', 'Delivery', 'Free if Validated', 'http://127.0.0.1/img/delivery.png', 1),
(7, 'Q', 'QCSenior', 'Free for QC Senior', 'http://127.0.0.1/img/qcsenior.png', 1),
(8, 'NQ', 'NonQCSenior', 'Discounted 20%', 'http://127.0.0.1/img/senior.png', 1),
(9, 'JP', 'Jeep', 'Free', 'http://127.0.0.1/img/jeepney.png', 1),
(10, 'TX', 'Taxi', 'Free', 'http://127.0.0.1/img/taxi.png', 1);
-- --------------------------------------------------------
--
-- Table structure for table `main`
--
DROP TABLE IF EXISTS `main`;
CREATE TABLE `main` (
`ptypeID` int(11) NOT NULL,
`parkertype` varchar(2) NOT NULL,
`ptypename` varchar(12) NOT NULL,
`ptypedesc` varchar(24) NOT NULL,
`btnimg` varchar(128) NOT NULL,
`ACTIVE` tinyint(1) NOT NULL DEFAULT '0',
`numOfReceipts` tinyint(1) NOT NULL DEFAULT '0',
`Discounted` tinyint(1) NOT NULL DEFAULT '0',
`DiscountPercentage` double DEFAULT NULL
) ENGINE=InnoDB DEFAULT CHARSET=latin1;
--
-- Dumping data for table `main`
--
INSERT INTO `main` (`ptypeID`, `parkertype`, `ptypename`, `ptypedesc`, `btnimg`, `ACTIVE`, `numOfReceipts`, `Discounted`, `DiscountPercentage`) VALUES
(1, 'R', 'Regular', 'P250 Loading', 'http://127.0.0.1/img/retail.png', 1, 1, 0, 0),
(2, 'V', 'VIP', 'Free Parking', 'http://127.0.0.1/img/vip.png', 1, 1, 0, 0),
(4, 'G', 'GracePeriod', '', 'http://127.0.0.1/img/generic.png', 1, 1, 0, 0),
(5, 'L', 'Lost', 'P50 plus P200', 'http://127.0.0.1/img/lost.png', 1, 1, 0, 0),
(6, 'P', 'Promo', 'Free if Validated', 'http://127.0.0.1/img/promo.png', 1, 1, 0, 0),
(7, 'Q', 'Senior', 'Free for Senior', 'http://127.0.0.1/img/qcsenior.png', 1, 2, 1, 100),
(8, 'NQ', 'NonQCSenior', 'Discounted 20%', 'http://127.0.0.1/img/senior.png', 1, 2, 1, 20),
(9, 'PW', 'PWD', 'Discounted 20%', 'http://127.0.0.1/img/pwd.png', 1, 2, 1, 20),
(10, 'M', 'Motorcycle', 'Motorcycles', 'http://127.0.0.1/img/motorcycle.png', 1, 1, 0, 0),
(23, 'J', 'Jeep', 'Free for 1 hour', 'http://127.0.0.1/img/jeepney.png', 1, 1, 0, 0),
(24, 'TC', 'Tricycle', 'Free', 'http://127.0.0.1/img/tricycle.png', 1, 1, 0, 0),
(25, 'D', 'Delivery', 'Free for 1 hour', 'http://127.0.0.1/img/deliveryred.png', 1, 1, 0, 0),
(27, 'BC', 'BPOEmployee', 'Free for 24hours', 'http://127.0.0.1/img/bpo_car.png', 1, 1, 0, 0),
(28, 'EM', 'Employees', 'One Car Only Free', 'http://127.0.0.1/img/employee.png', 1, 1, 0, 0),
(29, 'TN', 'Tenants', 'One Car Only Free', 'http://127.0.0.1/img/tenant.png', 1, 1, 0, 0),
(30, 'VD', 'Voids', 'Void Parkers', 'http://127.0.0.1/img/', 1, 1, 0, 0);
--
-- Indexes for dumped tables
--
--
-- Indexes for table `bfct_types`
--
ALTER TABLE `bfct_types`
ADD PRIMARY KEY (`ptypeID`),
ADD UNIQUE KEY `parkertype_2` (`parkertype`),
ADD UNIQUE KEY `parkertype_4` (`parkertype`),
ADD UNIQUE KEY `parkertype_5` (`parkertype`),
ADD KEY `parkertype` (`parkertype`),
ADD KEY `parkertype_3` (`parkertype`);
--
-- Indexes for table `bir_main`
--
ALTER TABLE `bir_main`
ADD PRIMARY KEY (`ptypeID`),
ADD UNIQUE KEY `parkertype_2` (`parkertype`),
ADD UNIQUE KEY `parkertype_4` (`parkertype`),
ADD UNIQUE KEY `parkertype_5` (`parkertype`),
ADD KEY `parkertype` (`parkertype`),
ADD KEY `parkertype_3` (`parkertype`);
--
-- Indexes for table `bir_types`
--
ALTER TABLE `bir_types`
ADD PRIMARY KEY (`ptypeID`),
ADD UNIQUE KEY `parkertype_2` (`parkertype`),
ADD UNIQUE KEY `parkertype_4` (`parkertype`),
ADD UNIQUE KEY `parkertype_5` (`parkertype`),
ADD KEY `parkertype` (`parkertype`),
ADD KEY `parkertype_3` (`parkertype`);
--
-- Indexes for table `cedar_types`
--
ALTER TABLE `cedar_types`
ADD PRIMARY KEY (`ptypeID`),
ADD UNIQUE KEY `parkertype_2` (`parkertype`),
ADD UNIQUE KEY `parkertype_4` (`parkertype`),
ADD UNIQUE KEY `parkertype_5` (`parkertype`),
ADD KEY `parkertype` (`parkertype`),
ADD KEY `parkertype_3` (`parkertype`);
--
-- Indexes for table `ever_types`
--
ALTER TABLE `ever_types`
ADD PRIMARY KEY (`ptypeID`),
ADD UNIQUE KEY `parkertype_2` (`parkertype`),
ADD UNIQUE KEY `parkertype_4` (`parkertype`),
ADD UNIQUE KEY `parkertype_5` (`parkertype`),
ADD KEY `parkertype` (`parkertype`),
ADD KEY `parkertype_3` (`parkertype`);
--
-- Indexes for table `main`
--
ALTER TABLE `main`
ADD PRIMARY KEY (`ptypeID`),
ADD UNIQUE KEY `parkertype_2` (`parkertype`),
ADD UNIQUE KEY `parkertype_4` (`parkertype`),
ADD UNIQUE KEY `parkertype_5` (`parkertype`),
ADD KEY `parkertype` (`parkertype`),
ADD KEY `parkertype_3` (`parkertype`);
--
-- AUTO_INCREMENT for dumped tables
--
--
-- AUTO_INCREMENT for table `bfct_types`
--
ALTER TABLE `bfct_types`
MODIFY `ptypeID` int(11) NOT NULL AUTO_INCREMENT, AUTO_INCREMENT=13;
--
-- AUTO_INCREMENT for table `bir_main`
--
ALTER TABLE `bir_main`
MODIFY `ptypeID` int(11) NOT NULL AUTO_INCREMENT, AUTO_INCREMENT=31;
--
-- AUTO_INCREMENT for table `bir_types`
--
ALTER TABLE `bir_types`
MODIFY `ptypeID` int(11) NOT NULL AUTO_INCREMENT, AUTO_INCREMENT=13;
--
-- AUTO_INCREMENT for table `cedar_types`
--
ALTER TABLE `cedar_types`
MODIFY `ptypeID` int(11) NOT NULL AUTO_INCREMENT, AUTO_INCREMENT=11;
--
-- AUTO_INCREMENT for table `ever_types`
--
ALTER TABLE `ever_types`
MODIFY `ptypeID` int(11) NOT NULL AUTO_INCREMENT, AUTO_INCREMENT=11;
--
-- AUTO_INCREMENT for table `main`
--
ALTER TABLE `main`
MODIFY `ptypeID` int(11) NOT NULL AUTO_INCREMENT, AUTO_INCREMENT=31;
COMMIT;
/*!40101 SET CHARACTER_SET_CLIENT=@OLD_CHARACTER_SET_CLIENT */;
/*!40101 SET CHARACTER_SET_RESULTS=@OLD_CHARACTER_SET_RESULTS */;
/*!40101 SET COLLATION_CONNECTION=@OLD_COLLATION_CONNECTION */;
|
select * from ptworkflowlog ORDER BY ID DESC;
select * from ptworkflowcmxlog
select * from ptworkflowmxlog
delete from ptworkflowlog
delete from ptworkflowcmxlog
delete from ptworkflowmxlog
select * from v_bz011
select * from pt999 where menuid like '21%' order by menuid for update
select * from jscs019 where jsde954 like '2501%' for update
select * from
select name from v$database
select trunc(sysdate)+21/24 from dual
select * from jxjdjcb
select * from jxjdnrb where blbid=14901;
select * from oa_fip_gw_ybyj order by id desc for update
select * from jxjdjhb_mx
select * from zb099 where jsde117='BZ011XMJXGL1'
select * from JXJDJCRYB cascade constraints;
select * from jscs007and czde033=2
create or replace view v_bmys_relation_ry as
select a.*,case nvl(czde033,0) when 0 then 'KY' when 1 then 'JZ' when 2 then 'KZ' end JB from (
select a.* ,row_number() over(partition by de062, jsde909 order by de062, jsde909,nvl(czde033,0) desc,czde938,jsde047) num
from (
select b.de062 de062,b.jsde909 jsde909,b.jsde908 jsde908,b.czde938 czde938,a.czde939 czde939,czde033,jsde047 from
(select * from jscs033 where jsde047=5 or czde938 in ('01','02') ) a,
( select a.*,b.jsde908 from (select * from CFG018 where de011=bc_hd_comm.GETYSNFYSZX()) a, jscs007 b where a.jsde909=b.jsde909 )b
where a.czde938=b.czde938
) a
) a
where num=1
order by de062,jsde908,czde938
02 ,a1
select 5.35*900 +60 from dual
union all
select 9.65*500 from dual
select 5.33*720 +60 from dual
union all
select 9.7*400 from dual
select * from v_bz007 where de011=9999
select * from v_bz008 where czde103=99990000000044 order by rptmxid
select * from dtjccz where czde103=99990000000044
select distinct c17 from dtjccz where czde103=99990000000044
--select c1,c11,c17,c31,c32,
select c1,c11,c31,c32,max(imax),max(imin),max(iavg)
from (
select c1,c11,'' c17,c31,c32,max(n0) imax,min(n0) imin,0 iavg
from (
select c1,c11,c17,c31,c32,n81,n82,round(n81/n82,2) n0
from dtjccz
where czde103=99990000000044 and n82>0 and c1='029004' and c17>=to_char(to_number(bc_hd_comm.GETYSNFYSZX())-1)||'06' and c17<=bc_hd_comm.GETYSNFYSZX()||'05'
union all
select c1,c11,c17,'','',sum(nvl(n81,0)),sum(nvl(n82,0)),round(sum(nvl(n81,0))/sum(nvl(n82,0)),2)
from ( select c1,c11,c17,c31,c32,n81,n82,round(n81/n82,2) n0
from dtjccz
where czde103=99990000000044 and n82>0 and c1='029004' and c17>=to_char(to_number(bc_hd_comm.GETYSNFYSZX())-1)||'06' and c17<=bc_hd_comm.GETYSNFYSZX()||'05'
) group by c1,c11,c17
) group by c1,c11,c31,c32
union all
select c1,c11,c17,c31,c32,0 imax,0 imin,round(nvl(n81,0)/nvl(n82,0),2) iavg
from (
select c1,c11,'' c17,c31,c32,sum(n81) n81,sum(n82) n82
from dtjccz
where czde103=99990000000044 and n82>0 and c1='029004' and c17>=to_char(to_number(bc_hd_comm.GETYSNFYSZX())-1)||'06' and c17<=bc_hd_comm.GETYSNFYSZX()||'05'
group by c1,c11,'',c31,c32
union all
select c1,c11,'','','',sum(n81),sum(n82)
from dtjccz
where czde103=99990000000044 and n82>0 and c1='029004' and c17>=to_char(to_number(bc_hd_comm.GETYSNFYSZX())-1)||'06' and c17<=bc_hd_comm.GETYSNFYSZX()||'05'
group by c1,c11
)
) group by c1,c11,c31,c32 order by c1,c11,c31,c32
|
-- phpMyAdmin SQL Dump
-- version 4.7.7
-- https://www.phpmyadmin.net/
--
-- Servidor: localhost:8889
-- Tiempo de generación: 06-10-2018 a las 22:10:27
-- Versión del servidor: 5.6.38
-- Versión de PHP: 7.1.12
SET SQL_MODE = "NO_AUTO_VALUE_ON_ZERO";
SET time_zone = "+00:00";
--
-- Base de datos: `tienda`
--
CREATE DATABASE IF NOT EXISTS `tienda` DEFAULT CHARACTER SET utf8mb4 COLLATE utf8mb4_spanish_ci;
USE `tienda`;
-- --------------------------------------------------------
--
-- Estructura de tabla para la tabla `compras_usuario`
--
DROP TABLE IF EXISTS `compras_usuario`;
CREATE TABLE `compras_usuario` (
`id` int(11) NOT NULL,
`usuario` varchar(150) COLLATE utf8mb4_spanish_ci NOT NULL,
`fecha_compra` varchar(150) COLLATE utf8mb4_spanish_ci NOT NULL,
`total_compra` varchar(150) COLLATE utf8mb4_spanish_ci NOT NULL,
`tienda_id` int(11) NOT NULL
) ENGINE=InnoDB DEFAULT CHARSET=utf8mb4 COLLATE=utf8mb4_spanish_ci;
-- --------------------------------------------------------
--
-- Estructura de tabla para la tabla `inventario`
--
DROP TABLE IF EXISTS `inventario`;
CREATE TABLE `inventario` (
`sku` int(11) NOT NULL,
`No. disponible` varchar(100) COLLATE utf8mb4_spanish_ci NOT NULL,
`color` varchar(150) COLLATE utf8mb4_spanish_ci NOT NULL
) ENGINE=InnoDB DEFAULT CHARSET=utf8mb4 COLLATE=utf8mb4_spanish_ci;
-- --------------------------------------------------------
--
-- Estructura de tabla para la tabla `Productos`
--
DROP TABLE IF EXISTS `Productos`;
CREATE TABLE `Productos` (
`sku` int(11) NOT NULL,
`nombre` varchar(100) COLLATE utf8mb4_spanish_ci NOT NULL,
`categoria` varchar(100) COLLATE utf8mb4_spanish_ci NOT NULL,
`p_id` int(11) NOT NULL
) ENGINE=InnoDB DEFAULT CHARSET=utf8mb4 COLLATE=utf8mb4_spanish_ci;
--
-- Volcado de datos para la tabla `Productos`
--
INSERT INTO `Productos` (`sku`, `nombre`, `categoria`, `p_id`) VALUES
(123, 'licuadora', 'electrodomesticos', 0),
(232, 'aliminio 23cm', 'metales', 0),
(234, 'caja para motos', 'automotriz', 0),
(542, 'refrigerador', 'electrodomesticos', 0);
-- --------------------------------------------------------
--
-- Estructura de tabla para la tabla `tiendas`
--
DROP TABLE IF EXISTS `tiendas`;
CREATE TABLE `tiendas` (
`id` int(11) NOT NULL,
`nombre` varchar(150) COLLATE utf8mb4_spanish_ci NOT NULL,
`ubicacion` varchar(150) COLLATE utf8mb4_spanish_ci NOT NULL,
`logo` varchar(150) COLLATE utf8mb4_spanish_ci NOT NULL,
`prodcut_id` int(11) NOT NULL
) ENGINE=InnoDB DEFAULT CHARSET=utf8mb4 COLLATE=utf8mb4_spanish_ci;
--
-- Volcado de datos para la tabla `tiendas`
--
INSERT INTO `tiendas` (`id`, `nombre`, `ubicacion`, `logo`, `prodcut_id`) VALUES
(1, 'sucursal 1', 'pachuca', 'imagenes/pachuca.png', 0),
(2, 'sucursal 2', 'zacatecas', 'imagenes/zacatecas.png', 0),
(3, 'sucursal 3', 'sonora', 'imagenes/sonora.png', 0),
(4, 'sucursal 4', 'veracruz', 'imagenes/veracruz.png', 0),
(5, 'sucursal 5', 'puebla', 'imagenes/puebla.png', 0),
(6, 'sucursal 6', 'monterrey', 'imagenes/monterrey.png', 0);
-- --------------------------------------------------------
--
-- Estructura de tabla para la tabla `Usuarios`
--
DROP TABLE IF EXISTS `Usuarios`;
CREATE TABLE `Usuarios` (
`id_usuario` int(11) NOT NULL,
`nombre` varchar(100) COLLATE utf8mb4_spanish_ci NOT NULL,
`apellidos` varchar(100) COLLATE utf8mb4_spanish_ci NOT NULL,
`contrasena` varchar(100) COLLATE utf8mb4_spanish_ci NOT NULL,
`email` varchar(150) COLLATE utf8mb4_spanish_ci NOT NULL,
`departamento` varchar(200) COLLATE utf8mb4_spanish_ci NOT NULL,
`telefono` varchar(15) COLLATE utf8mb4_spanish_ci NOT NULL,
`direccion` varchar(300) COLLATE utf8mb4_spanish_ci NOT NULL,
`ciudad` varchar(200) COLLATE utf8mb4_spanish_ci NOT NULL
) ENGINE=InnoDB DEFAULT CHARSET=utf8mb4 COLLATE=utf8mb4_spanish_ci;
--
-- Volcado de datos para la tabla `Usuarios`
--
INSERT INTO `Usuarios` (`id_usuario`, `nombre`, `apellidos`, `contrasena`, `email`, `departamento`, `telefono`, `direccion`, `ciudad`) VALUES
(1, 'mario', 'ponce', '12345', 'mario@gmail.com', '', '', '', ''),
(2, 'freddy', 'ponce', '12345', 'freddy@gmail.com', '', '', '', ''),
(3, 'margarita', 'escobar', '12345', 'margarita@gmail.com', '', '', '', ''),
(4, 'pedro', 'perez', '12345', 'pedro@gmail.com', '', '', '', ''),
(5, 'raul', 'perez', '12345', 'raul@gmail.com', '', '', '', ''),
(6, 'jose', 'perez', '12345', 'jose@gmail.com', '', '', '', ''),
(7, 'benito', 'escobar', '12345', 'benito@gmail.com', '', '', '', ''),
(8, 'sara', 'perez', '12345', 'sara@gmail.com', '', '', '', ''),
(9, 'gustavo', 'perez', '12345', 'gustavo@gmail.com', '', '', '', ''),
(10, 'leti', 'perez', '12345', 'leti@gmail.com', '', '', '', '');
--
-- Índices para tablas volcadas
--
--
-- Indices de la tabla `compras_usuario`
--
ALTER TABLE `compras_usuario`
ADD PRIMARY KEY (`id`),
ADD KEY `id` (`id`),
ADD KEY `tienda_id` (`tienda_id`);
--
-- Indices de la tabla `inventario`
--
ALTER TABLE `inventario`
ADD PRIMARY KEY (`sku`),
ADD KEY `sku` (`sku`);
--
-- Indices de la tabla `Productos`
--
ALTER TABLE `Productos`
ADD PRIMARY KEY (`sku`),
ADD KEY `p_id` (`p_id`),
ADD KEY `categoria` (`categoria`);
--
-- Indices de la tabla `tiendas`
--
ALTER TABLE `tiendas`
ADD PRIMARY KEY (`id`),
ADD KEY `id` (`id`),
ADD KEY `logo` (`logo`),
ADD KEY `prodcut_id` (`prodcut_id`);
--
-- Indices de la tabla `Usuarios`
--
ALTER TABLE `Usuarios`
ADD PRIMARY KEY (`id_usuario`);
--
-- AUTO_INCREMENT de las tablas volcadas
--
--
-- AUTO_INCREMENT de la tabla `compras_usuario`
--
ALTER TABLE `compras_usuario`
MODIFY `id` int(11) NOT NULL AUTO_INCREMENT;
--
-- AUTO_INCREMENT de la tabla `Usuarios`
--
ALTER TABLE `Usuarios`
MODIFY `id_usuario` int(11) NOT NULL AUTO_INCREMENT, AUTO_INCREMENT=11;
--
-- Restricciones para tablas volcadas
--
--
-- Filtros para la tabla `compras_usuario`
--
ALTER TABLE `compras_usuario`
ADD CONSTRAINT `compras_usuario_ibfk_1` FOREIGN KEY (`id`) REFERENCES `Usuarios` (`id_usuario`) ON UPDATE CASCADE;
--
-- Filtros para la tabla `inventario`
--
ALTER TABLE `inventario`
ADD CONSTRAINT `inventario_ibfk_1` FOREIGN KEY (`sku`) REFERENCES `Productos` (`sku`) ON UPDATE CASCADE;
--
-- Filtros para la tabla `tiendas`
--
ALTER TABLE `tiendas`
ADD CONSTRAINT `tiendas_ibfk_1` FOREIGN KEY (`prodcut_id`) REFERENCES `Productos` (`p_id`) ON DELETE CASCADE ON UPDATE CASCADE;
|
insert into tbl_users (isadmin, password) values (true,'pw');
insert into tbl_users (isadmin, password) values (false,'customer');
insert into tbl_users (isadmin, password) values (false,'yf');
insert into tbl_users (isadmin, password) values (true,'ab');
insert into tbl_users (isadmin, password) values (false,'db');
insert into tbl_users (isadmin, password) values (false,'hl');
insert into tbl_users (isadmin, password) values (false,'qy');
insert into tbl_users (isadmin, password) values (false,'sr');
insert into tbl_users (isadmin, password) values (true,'un');
insert into tbl_users (isadmin, password) values (true,'ec');
insert into tbl_users (isadmin, password) values (true,'mi');
insert into tbl_users (isadmin, password) values (true,'ao');
insert into tbl_users (isadmin, password) values (false,'oq');
insert into tbl_users (isadmin, password) values (false,'kg');
insert into tbl_users (isadmin, password) values (true,'sh');
insert into tbl_users (isadmin, password) values (false,'vu');
insert into tbl_users (isadmin, password) values (false,'of');
insert into tbl_users (isadmin, password) values (true,'tb');
insert into tbl_users (isadmin, password) values (true,'mw');
insert into tbl_users (isadmin, password) values (false,'fr');
insert into tbl_users (isadmin, password) values (false,'za');
insert into tbl_users (isadmin, password) values (false,'ag');
insert into tbl_users (isadmin, password) values (false,'lo');
insert into tbl_users (isadmin, password) values (false,'qq');
insert into tbl_users (isadmin, password) values (true,'ei');
insert into tbl_users (isadmin, password) values (false,'ci');
insert into tbl_users (isadmin, password) values (false,'jn');
insert into tbl_users (isadmin, password) values (false,'zn');
insert into tbl_users (isadmin, password) values (false,'zu');
insert into tbl_users (isadmin, password) values (true,'wp');
insert into tbl_users (isadmin, password) values (true,'ri');
insert into tbl_users (isadmin, password) values (true,'xl');
insert into tbl_users (isadmin, password) values (false,'bi');
insert into tbl_users (isadmin, password) values (true,'sr');
insert into tbl_users (isadmin, password) values (true,'sa');
insert into tbl_users (isadmin, password) values (true,'sa');
insert into tbl_users (isadmin, password) values (true,'jm');
insert into tbl_users (isadmin, password) values (false,'vo');
insert into tbl_users (isadmin, password) values (true,'or');
insert into tbl_users (isadmin, password) values (true,'hr');
insert into tbl_users (isadmin, password) values (true,'kh');
insert into tbl_users (isadmin, password) values (true,'pm');
insert into tbl_users (isadmin, password) values (false,'we');
insert into tbl_users (isadmin, password) values (true,'pc');
insert into tbl_users (isadmin, password) values (true,'dv');
insert into tbl_users (isadmin, password) values (false,'xa');
insert into tbl_users (isadmin, password) values (false,'sw');
insert into tbl_users (isadmin, password) values (true,'sw');
insert into tbl_users (isadmin, password) values (false,'zr');
insert into tbl_users (isadmin, password) values (false,'jr');
insert into tbl_users (isadmin, password) values (false,'yk');
insert into tbl_users (isadmin, password) values (false,'uv');
insert into tbl_users (isadmin, password) values (false,'dp');
insert into tbl_users (isadmin, password) values (false,'xt');
insert into tbl_users (isadmin, password) values (false,'oa');
insert into tbl_users (isadmin, password) values (true,'eq');
insert into tbl_users (isadmin, password) values (false,'ml');
insert into tbl_users (isadmin, password) values (false,'nm');
insert into tbl_users (isadmin, password) values (false,'ib');
insert into tbl_users (isadmin, password) values (false,'gk');
insert into tbl_users (isadmin, password) values (true,'xb');
insert into tbl_users (isadmin, password) values (true,'uh');
insert into tbl_users (isadmin, password) values (true,'ia');
insert into tbl_users (isadmin, password) values (false,'mu');
insert into tbl_users (isadmin, password) values (false,'rr');
insert into tbl_users (isadmin, password) values (true,'hw');
insert into tbl_users (isadmin, password) values (false,'ui');
insert into tbl_users (isadmin, password) values (false,'kf');
insert into tbl_users (isadmin, password) values (false,'ay');
insert into tbl_users (isadmin, password) values (true,'en');
insert into tbl_users (isadmin, password) values (false,'ia');
insert into tbl_users (isadmin, password) values (false,'kt');
insert into tbl_users (isadmin, password) values (false,'mv');
insert into tbl_users (isadmin, password) values (false,'op');
insert into tbl_users (isadmin, password) values (false,'gt');
insert into tbl_users (isadmin, password) values (true,'hp');
insert into tbl_users (isadmin, password) values (true,'oo');
insert into tbl_users (isadmin, password) values (false,'ft');
insert into tbl_users (isadmin, password) values (false,'of');
insert into tbl_users (isadmin, password) values (true,'bq');
insert into tbl_users (isadmin, password) values (true,'vj');
insert into tbl_users (isadmin, password) values (true,'nn');
insert into tbl_users (isadmin, password) values (true,'cp');
insert into tbl_users (isadmin, password) values (true,'vc');
insert into tbl_users (isadmin, password) values (true,'ka');
insert into tbl_users (isadmin, password) values (false,'bd');
insert into tbl_users (isadmin, password) values (true,'mu');
insert into tbl_users (isadmin, password) values (false,'zj');
insert into tbl_users (isadmin, password) values (false,'iq');
insert into tbl_users (isadmin, password) values (false,'mg');
insert into tbl_users (isadmin, password) values (false,'hf');
insert into tbl_users (isadmin, password) values (false,'sl');
insert into tbl_users (isadmin, password) values (false,'qk');
insert into tbl_users (isadmin, password) values (true,'lc');
insert into tbl_users (isadmin, password) values (false,'xd');
insert into tbl_users (isadmin, password) values (false,'za');
insert into tbl_users (isadmin, password) values (true,'ka');
insert into tbl_users (isadmin, password) values (false,'nu');
insert into tbl_users (isadmin, password) values (true,'nv');
insert into tbl_users (isadmin, password) values (true,'oz');
insert into tbl_users (isadmin, password) values (true,'he');
insert into tbl_users (isadmin, password) values (true,'nk');
--import java.util.Random;
--public class Make {
-- private static final int NUM_THINGOS = 100;
-- public static void main (String[] args) {
-- Random rng = new Random();
-- boolean tf;
-- String pw;
-- for (int i=0; i < NUM_THINGOS; i++) {
-- tf = rng.nextBoolean();
-- pw = "";
-- pw += (char) ('a' + rng.nextInt(26));
-- pw += (char) ('a' + rng.nextInt(26));
-- System.out.println("insert into tbl_users (isadmin, password) values (" + tf +",\'"+pw+"\');");
-- }
--
-- }
--}
|
REM ------------------------------------------------------------------------
REM REQUIREMENTS:
REM SELECT on V$ tables
REM ------------------------------------------------------------------------
REM PURPOSE:
REM Show control file status
REM ------------------------------------------------------------------------
set linesize 80
set pages 100
set feedback off
col name for a44
SELECT *
FROM v$controlfile
;
prompt
exit
|
create table CONTACTBASE_ACCESS_REQUEST_REGION_LINK (
ACCESS_REQUEST_ID uuid,
REGION_ID uuid,
primary key (ACCESS_REQUEST_ID, REGION_ID)
);
|
# Write your MySQL query statement below
#https://leetcode.com/problems/department-highest-salary/submissions/
SELECT Department.Name as 'Department',Employee.Name AS 'Employee',Salary
FROM Employee
JOIN Department ON Employee.DepartmentID = Department.ID
WHERE
(Employee.DepartmentID,Salary) IN
(SELECT
DepartmentId, MAX(Salary)
FROM
Employee
GROUP BY DepartmentId
) |
SELECT USER
FROM DUAL;
--■■■ 팀 별 실습 수행 과제 ■■■--
|
create table articles (
id serial primary key,
title text,
content text
); |
BEGIN TRANSACTION;
CREATE TABLE IF NOT EXISTS `utilizatori` (
`username` TEXT NOT NULL,
`password` TEXT NOT NULL,
`prenume` TEXT NOT NULL,
`nume` TEXT NOT NULL,
PRIMARY KEY(`username`)
);
INSERT INTO `utilizatori` VALUES ('Andreea','d74ff0ee8da3b9806b18c877dbf29bbde50b5bd8e4dad7a3a725000feb82e8f1','andreea','Popescu');
INSERT INTO `utilizatori` VALUES ('Ana','b28a23c85bed4b50f9ee8c18738e9e3a320ae9e9ead3e5c61c59a11c38d694fe','Ana','Pop');
INSERT INTO `utilizatori` VALUES ('contnou','a80b568a237f50391d2f1f97beaf99564e33d2e1c8a2e5cac21ceda701570312','Ion','Pop');
INSERT INTO `utilizatori` VALUES ('contnou2','252f10c83610ebca1a059c0bae8255eba2f95be4d1d7bcfa89d7248a82d9f111','Ioana','Nechifor');
INSERT INTO `utilizatori` VALUES ('lala','494414ded24da13c451b13b424928821351c78fce49f93d9e1b55f102790c206','Lala','Lala');
INSERT INTO `utilizatori` VALUES ('malina','a80b568a237f50391d2f1f97beaf99564e33d2e1c8a2e5cac21ceda701570312','Malina','Marin');
INSERT INTO `utilizatori` VALUES ('user1','0a041b9462caa4a31bac3567e0b6e6fd9100787db2ab433d96f6d178cabfce90','Andrei','Georgescu');
INSERT INTO `utilizatori` VALUES ('b','3e23e8160039594a33894f6564e1b1348bbd7a0088d42c4acb73eeaed59c009d','Bianca','Ionescu');
INSERT INTO `utilizatori` VALUES ('ioana','858e2b14533db9791a67003491d9ca28e7421ce4d20d3f78119a8c3df4ee6d99','Ioana','popescu');
INSERT INTO `utilizatori` VALUES ('user2','6025d18fe48abd45168528f18a82e265dd98d421a7084aa09f61b341703901a3','Oana','Bulai');
INSERT INTO `utilizatori` VALUES ('_user_','04f8996da763b7a969b1028ee3007569eaf3a635486ddab211d512c85b9df8fbn','Andrada','Popescu');
INSERT INTO `utilizatori` VALUES ('puf','5879cab24833171537522833828ca2d75ebc4ecb0dabd9116e4580ff928960a5g.ini','Puf','Puf');
INSERT INTO `utilizatori` VALUES ('pufi','a4b429e4351bd149658ac87d9e740612a303b038a069ecb52653134f9296286bn','puf','puf');
INSERT INTO `utilizatori` VALUES ('pufii','66654e2785c214b41c968ab7e216806236d7a1a7889aee0705119efaa240398d','pufii','pufii');
INSERT INTO `utilizatori` VALUES ('oana','89e3564556d7d659e3065c41b23cce12fc4446d72508d5ce993677ec4c789ad7','Oana','Georgescu');
INSERT INTO `utilizatori` VALUES ('test','9f86d081884c7d659a2feaa0c55ad015a3bf4f1b2b0b822cd15d6c15b0f00a08','test','test');
INSERT INTO `utilizatori` VALUES ('test2','60303ae22b998861bce3b28f33eec1be758a213c86c93c076dbe9f558c11c752','test2','test2');
INSERT INTO `utilizatori` VALUES ('test4','a4e624d686e03ed2767c0abd85c14426b0b1157d2ce81d27bb4fe4f6f01d688a','Prenume_test4','Nume_test4');
INSERT INTO `utilizatori` VALUES ('test5','a140c0c1eda2def2b830363ba362aa4d7d255c262960544821f556e16661b6ff','test5','test5');
CREATE TABLE IF NOT EXISTS `prietenii` (
`user1` TEXT NOT NULL,
`user2` TEXT NOT NULL
);
INSERT INTO `prietenii` VALUES ('Ana','ioana');
INSERT INTO `prietenii` VALUES ('ioana','Ana');
INSERT INTO `prietenii` VALUES ('user1','ioana');
INSERT INTO `prietenii` VALUES ('ioana','user1');
INSERT INTO `prietenii` VALUES ('Ana','user1');
INSERT INTO `prietenii` VALUES ('user1','Ana');
INSERT INTO `prietenii` VALUES ('b','Ana');
INSERT INTO `prietenii` VALUES ('Ana','b');
INSERT INTO `prietenii` VALUES ('Ana','lala');
INSERT INTO `prietenii` VALUES ('Ana','a');
INSERT INTO `prietenii` VALUES ('oana','Ana');
INSERT INTO `prietenii` VALUES ('Ana','oana');
INSERT INTO `prietenii` VALUES ('test','b');
INSERT INTO `prietenii` VALUES ('b','test');
INSERT INTO `prietenii` VALUES ('Ana','test');
INSERT INTO `prietenii` VALUES ('test5','Ana');
INSERT INTO `prietenii` VALUES ('Ana','test5');
CREATE TABLE IF NOT EXISTS `discutii` (
`capitol` INTEGER NOT NULL,
`username` TEXT,
`post` TEXT
);
INSERT INTO `discutii` VALUES (4,'Ana','Aici sunt discutiile despre capitolul 4?');
INSERT INTO `discutii` VALUES (4,'ioana','Da');
INSERT INTO `discutii` VALUES (4,'Ana','Ok');
INSERT INTO `discutii` VALUES (6,'ioana','Unde pot gasi informatii suplimentare?');
INSERT INTO `discutii` VALUES (6,'Ana','pe net');
INSERT INTO `discutii` VALUES (4,'ioana','Buna');
INSERT INTO `discutii` VALUES (4,'Ana','Hello');
INSERT INTO `discutii` VALUES (1,'Ana','buna');
INSERT INTO `discutii` VALUES (1,'ioana','hello');
INSERT INTO `discutii` VALUES (1,'user1','buna');
INSERT INTO `discutii` VALUES (7,'ioana','hello');
INSERT INTO `discutii` VALUES (6,'Ana','Aici sunt discutiile despre capitolul 6?');
INSERT INTO `discutii` VALUES (6,'ioana','da, aici sunt');
INSERT INTO `discutii` VALUES (4,'Ana','hello');
INSERT INTO `discutii` VALUES (7,'Ana','buna');
INSERT INTO `discutii` VALUES (7,'b','helloo');
INSERT INTO `discutii` VALUES (7,'ioana','......');
INSERT INTO `discutii` VALUES (5,'b','aici este capitolul 5');
INSERT INTO `discutii` VALUES (3,'Ana','aici este capitoul 3');
INSERT INTO `discutii` VALUES (3,'b','da');
INSERT INTO `discutii` VALUES (4,'Ana','hello');
INSERT INTO `discutii` VALUES (4,'b','buna');
INSERT INTO `discutii` VALUES (11,'Ana','buna');
INSERT INTO `discutii` VALUES (11,'b','salut');
INSERT INTO `discutii` VALUES (7,'b','...');
INSERT INTO `discutii` VALUES (6,'b','da');
INSERT INTO `discutii` VALUES (6,'Ana','dap');
CREATE TABLE IF NOT EXISTS `cursuri` (
`capitol` INTEGER NOT NULL,
`text` TEXT,
PRIMARY KEY(`capitol`)
);
INSERT INTO `cursuri` VALUES (1,'Cursul 1
Concepte si notiuni de baza
(c)Lenuta Alboaie
adria@info.uaic.ro
https://profs.info.uaic.ro/~computernetworkscursullaboratorul.php
Cuprins:
• Concepte
• Definitii
• Necesitatea si utilizarea retelelor de calculatoare
• Clasificare
• Topologii
• Componente
• Protocol
• Modele de arhitecturi deretea
CONCEPTE
◦ Informatie: orice poate fi reprezentat sub forma de biti
◦ Resursa: termen generic, putand reprezenta date, echipamente etc
◦ Pachet: modalitate de stocare a datelor
◦ Legatura:conexiune realizata intre membrii retelei
◦ Nod:calculator din retea care are asociata o adresa
◦ Protocol:reguli utilizate pentru realizarea comunicarii
◦ Comunicare:schimb de informatii intre nodurile din retea
• Protocol
A protocol defines the format and the order of messages exchanged between two or more communicating entities, as well as the actions taken on the transmission and/or receipt of a message or other event.
◦ Definitii:
▪ Colectie interconectata de calculatoare autonome
▪ O retea poate fi definita in mod recursiv ca doua sau mai multe noduri conectate printr-o legatura fizica, sau prin doua sau mai multe retele conectate de unul sau mai multe noduri
◦ Aspecte:
▪ Hardware:conecteaza“fizic” computerele intre ele
▪ Software:Protocoale– specifica serviciile furnizate de retea
De ce suntnecesare:
• Partajarea resurselor (fizice,date)
• Asigurarea fiabilitatii
• Reducerea costurilor
• Impactul in viata reala:
◦ Conversatiile electronice
◦ Access la informatii la distanta
◦ Divertisment interactiv
◦ Comert electronic
◦ Dupa dispunerea spatiala:
▪ PAN(Personal Area Network)
▪ LAN(Local Area Network)
▪ MAN(Metropolitan Area Network)
▪ WAN(Wide Area Network)
▪ Internet
Tipuri de retele - clasificare
◦ In functie de tehnologia de transmisie:
▪ Retele cu difuzare(un singur canal de comunicare)
• broadcast,multicast
▪ Retele point-to-point
• unicast
Topologie fizica: modul de interconectare a calculatoarelor in retea
Topologie logica: modul in care datele sunt transferate de la un calculator la altul
Posibile topologii fizice pentru:
• Retele cu difuzare LAN
◦ Magistrala(bus)
◦ Inel (ring)
• Retele point-to-point
◦ Stea(star)
◦ Inel (ring)
◦ Arbore(tree)
◦ Completa
◦ In functie de tehnologia hardware(si software)folosita pentru interconectare
▪ Retele folosind medii de transmisie cu fir
▪ Retele folosind medii de transmisie fara fir
◦ In functie de elementele componente:
▪ Omogena:retea de calculatoare folosind configuratii si protocoale similare
• Exemplu: O retea folosind Microsoft Windows via TCP/IP
▪ Eterogena:retea care contine tipuri diferite de calculatoare, sisteme de operare si/sau protocoale diferite.
• Exemplu: LAN care conecteaza un smartphone cu Android si un computer Apple Machintosh
Componente
Gazda(eng.Host) – este un sistem computational conectat la Internet
Hub(Hub Network) – dispozitiv (deseori amplificator de semnal) folosit pentru conectarea mai multor dispozitive =>segment deretea (network segment)
Switch(Switch)- dispozitiv care filtreaza si retrimite pachetele in retea
Leonard-Kleinrock ->IMP (Interface Message Processor) 1969
Componente
◦ Ruter(Router) – dispozitiv oferind conectivitatea intre retele individuale, realizand dirijarea pachetelor intre aceste retele
• Punte(Bridge) – dispozitiv care conecteaza doua sau mai multe segmente intr-oretea
• Poarta(Gateway) –este punctul de conectare a doua retele incompatibile
• Repeater-este un dispozitiv electronic care primeste semnale pe care le retransmite la un nivel mai inalt sau la o putere mai mare,astfel ca semnalul sa poata acoperi zone mari fara degradare a calitatii sale
');
INSERT INTO `cursuri` VALUES (2,'Cursul 2
(c)Lenuta Alboaie
adria@info.uaic.ro
https://profs.info.uaic.ro/~computernetworkscursullaboratorul.php
Cuprins
• Retele de calculatoare – organizare
• Modele de arhitecturi de retea(OSI,TCP/IP)
• Modelul TCP/IP
• ISO/OSI versus TCP/IP
Retele de calculatoare – organizare
• Organizarea retelelor de calculatoare –stiva de nivele
◦ Functionalitate:
▪ Interfata:asigura comunicarea intre doua nivele consecutive
▪ Serviciu:furnizeaza functionalitatea unui nivel
◦ Rezultat:reducerea complexitatii proiectarii
◦ Principiul de comunicare:ce transmite emitatorul la nivelul n este ceea ce se primeste la destinatar la nivelul n
• Protocol–regulile si conventiile prin care se realizeaza comunicarea
• Specificarea serviciului este realizata printr-un set de primitive(operatii) puse la dispozitia celui ce foloseste serviciul
• Serviciu != Protocol
◦ Tipuri de servicii
▪ Orientat-conexiune(eng.connection-oriented)
• Comunicarea necesita stabilirea unei conexiuni
• Similar serviciului telefonic
▪ Fara conexiune(eng.connectionless)
• Comunicarea nu necesita stabilirea unei conexiuni
• Similar serviciului postal
• Arhitectura de retea:multimea de nivele si de protocoale
–Specificatia unei arhitecturi trebuie sa ofere suficiente informatii pentru ca programele sau echipamentele destinate unui nivel sa indeplineasca protocoalele corespunzatoare
• Stiva de protocoale:lista de protocoale(de pe toate nivelele)utilizate de catre un anumit sistem
◦ Fiecare nivel trebuie sar ealizeze indentificarea emitatorilor&receptorilor printr-un mecanism de adresare
◦ Identificarea regulilor de transfer a datelor
▪ comunicare simplex
• Exemplu:TV
▪ comunicare half-duplex
• Exemplu:"walkie-talkie"
▪ comunicare full-duplex
• Exemplu:telefon
Modelul OSI- motivatie
• Necesitatea unui nivel deabstractizare diferit => crearea unui nou nivel
◦ Obs. Numarul de niveluri trebuie sa fie optim a.i. acelasi nivel sa aiba functii diferite,dar arhitectura sa fie functionala
• Un nivel are un rol bine definit; functia nivelului trebuie aleasa acordindu-se atentie definirii de protocoale standardizate pe plan international
• Minimizarea fluxului de informatii intre nivele este realizata printr-o buna delimitare a nivelelor
=> nivelele pot fi modificate si implementate in mod independent
• Fiecare nivel ofera un serviciu nivelului superior (folosind servicii de pe nivelurile anterioare)
• Nivelurile “peer” al sistemelor diferite comunica via un protocol
Modelul OSI – structura
• Nivelul Fizic
• Nivelul LegaturiideDate
• Nivelul Retea
• Nivelul Transport
• Nivelul Sesiune
• Nivelul Prezentare
• Nivelul Aplicati
Modelul TCP/IP
▪ sistem terminal(eng.end-system)–gazda(eng. host)
▪ retea(eng.network) -oferasuportul pentrutransferuldedate intresistemeterminale
▪ internet- colectie deretele(interconectate)
▪ subretea(eng.subnetwork) -componentadin internet
▪ sistem intermediar(eng.intermediatesystem)-conecteazadouasubretele
• Oferaposibilitateade ainterconectamai multe tipuri deretele
• Arecaaxanivelurilereteasitransport
– suportat de multe implementari ale nivelului fizic (cablu coaxial,twisted pair, fibra optica)
◦ Nivelul“fizic”
– Asigura conectareahost-ului laretea
• Nivelultransport
◦ Asigurarealizareacomunicariiintregazdasursasigazda
destinatie
◦ Protocoale
▪ TCP(TransmissionControl Protocol) - RFC793,761
▪ UDP(User Datagram Protocol) – RFC768
▪ Alte protocoale: SCTP(Stream ControlTransmissionProtocol) – RFC 4960, 3286 (2960, 3309);DCCP(Datagram Congestion Control Protocol) – RFC 4340,4336;
• Asemanari:
◦ Ambele sebazeazapeostivadeprotocoale
◦ Functionalitatile straturiloresteoarecumasemanatoare
◦ Ambele au nivelul aplicatie ca nivel superior
◦ Sebazeaza(direct sau indirect) pe nivelul transport
• Deosebiri:
◦ ISO/OSIesteindicat ca model teoretic;TCP/IPesteeficient inimplementare
◦ OSI faceexplicitadistinctia intre serviciu,interfatasiprotocol;TCP/IPnu
◦ ISO/OSI pune la dispozitie protocoalecareasigura o comunicare fiabila (detectarea sitratarede erori la fiecarenivel);
TCP/IP face verificarea comunicarii la nivelul transport
');
INSERT INTO `cursuri` VALUES (3,'Cursul 3
Nivelul Retea
Lenuta Alboaie
adria@info.uaic.ro
https://profs.info.uaic.ro/~computernetworkscursullaboratorul.php
Cuprins
• Nivelul Retea
• Protocolul IPv4
• Problematica
• Caracterizare
• Subretele
• Retele Private
• ICMP
• Rezolutia adreselor
• IPv6 – imagine generala
Preliminarii
• Situatia initiala
- Inainte de Internet doar nodurile din aceeasi retea puteau comunica
intre ele
Preliminarii
• Probleme
– Cum se pot transporta pachete intr-un mediu eterogen?
• Eterogenitate
• La nivelurile inferioare: cum
se poate face interconectarea
unui numar mare de retele
independente?
• La nivelurile superioare: cum
se poate oferi suport pentru
o mare varietate de aplicatii?
• Scalare: cum s-ar putea suporta un numar mare de noduri si
aplicatii intr-un astfel de sistem de retele interconectate?
Solutia
• IP – Internet Protocol
Nivelul retea
• Protocolul IP este utilizat de sisteme autonome (AS – Autonomous
Systems) in vederea interconectarii
Figura:
Internetul -
colectie de
retele
interconectate
[Computer Networks, 2003
Andrew S. Tanenbaum]
Nivelul Retea
• Rol: ofera servicii neorientate-conexiune
pentru a transporta datagrame de la sursa
la destinatie; sursa si destinatia pot fi in
retele diferite
• Fiecare datagrama este independenta de
celelalte
• Nu se garanteaza trimiterea corecta a
datagramelor (pierdere, multiplicare,…)
Protocolul IP
• Datagrama IPv4
• Valorile uzuale ale
campului Version
sunt:
• 4 – protocolul IP
(RFC 791)
(6 pentru protocolul
IPv6 (RFC 1883))
9
Data
Figura: Datagrama IPv4
Specifica lungimea
antetului
datagramei
Specifica
dimensiunea
intregului pachet
Protocolul IP
• Datagrama IPv4
• Campul Type of
service permite gazdei
sa comunice
subretelei (e.g.
routere) ce tip de
serviciu doreste
10
Data
Figura: Campul Type of Service
Figura: Datagrama IPv4
• Datagrama IPv4
• Campul Identification
permite gazdei
destinatie sa identifice
apartenenta la o
datagrama a noului
fragment primit
Data
Figura: Datagrama IPv4
• Flagurile:
• DF (Don’t Fragment) – indica ruterelor sa nu fragmenteze
datagrama
• MF (More Fragments) – semnalizeaza ca pachetul este un
fragment, urmat de altele; ultimul fragment are acest bit 0
• Campul Fragment offset – locul fragmentului in datagrama
Protocolul IP
• Datagrama IP
• Fragmentarea datagramelor:
• Fiecare fragment (pachet) are aceeasi structura ca
datagrama IP
• Reasamblarea datagramelor se face la destinatar
• Daca un fragment al unei datagrame e pierdut, acea
datagrama e distrusa (se trimite la expeditor un mesaj
ICMP – Internet Control Message Protocol)
• Mecanismul de fragmentare a fost folosit pentru unele
atacuri – firewall piercing (un fragment “special” e
considerat ca fiind parte a unei conexiuni deja stabilite,
astfel incat ii va fi permis accesul via firewall)
Protocolul IP
• Datagrama IP
• Filtrarea datagramelor:
• Se realizeaza de un firewall: ofera accesul din
exterior in reteaua interna, conform unor politici
de acces, doar pentru anumite tipuri de pachete
(utilizate de anumite protocoale/servicii)
• Preintimpina o serie de atacuri vizind
securitatea
• Firewall-ul poate fi software sau hardware
• Firewall-ul poate juca rol de proxy sau de
gateway
Protocolul IP
• Rolul si arhitectura unui proxy:
– Acces indirect la alte retele (Internet) pentru gazdele
dintr-o retea locala via proxy
– Proxy-ul poate fi software sau hardware
– Rol de poarta (gateway), de firewall sau de server de
cache
– Proxy-ul ofera partajarea unei conexiuni Internet
– Utilizat la imbunatatirea performantei (e.g., caching,
controlul fluxului), filtrarea cererilor, asigurarea
anonimitatii
Protocolul IP
• Datagrama IPv4
• Campul TTL (Time to
Live) specifica durata
de viata a pachetului;
numarul este
decrementat de
fiecare router prin
care trece pachetul
Data
Figura: Datagrama IPv4
Protocolul IP
• Datagrama IPv4
• Campul Protocol
specifica protocolul
(de nivel superior)
caruia ii este destinata
informatia inclusa in
datagrama:
Data
1 ICMP (Internet Control Message Protocol)
2 IGMP (Internet Group Message Protocol)
6 TCP (Transmission Control Protocol)
17 UDP (User Datagram Protocol)
… etc.(RFC 1700)
Protocolul IP
• Datagrama IPv4
• Campul Header
checksum folosit
pentru detectarea
erorilor; daca
apare o eroare
datagrama este
distrusa
• Datagrama IPv4
• Campul Options
Optiune Descriere
Securitate Mentioneaza cat de secreta este datagrama
Dirijare stricta pe baza sursei (engl. strict
source routing)
Indica calea completa de parcurs
Dirijarea aproximativa pe baza sursei (engl.
Loose source routing)
Indica o lista a ruterelor care nu trebuie sarite
Intregistreaza calea (engl. record route) Face fiecare ruter sa-si adauge adresa IP
Amprenta de timp (engl. timestamp) Face fiecare ruter sa-si adauge adresa si o amprenta de timp
Protocolul IP
• Datagrama IPv4
• Campul Source
adress si
Destination adress
indica adresa
sursei si destinatiei
Data
Figura: Datagrama IPv4
Protocolul IP
• Adrese IPv4
• Fiecare adresa IP include un identificator de
retea (NetID) si un identificator de gazda
(HostID)
• Fiecare interfata de retea are o adresa IPv4
unica
• O adresa IPv4 are lungimea de 32 biti
• Initial (RFC 791) exista impartirea in clase de
adrese: A,B,C,D,E
Protocolul IP
• Adrese IPv4
• Clasa A: 128 retele posibile, 224 gazde/retea
• Clasa B: 214 retele posibile, 216 gazde/retea
• Clasa C: peste 2 milioane de retele, 255 gazde/retea
• Identificatorul de retea (NetID) este asignat de o
autoritate centrala (NIC – Network Information Center)
• Identificatorul de gazda (HostID) este asignat local de
administratorul retelei
• Exemplu: 85.122.23.145 – Clasa A (conventie de notatie
in zecimal)
0101 0101 0111 1010 0001 0111 1001 0001
• Pentru IPv6 se recomanda reprezentarea hexadecimal
• O interfata (placa) de retea are asignata o unica adresa IP
• O gazda poate avea mai multe placi de retea, deci mai multe
adrese IP
• Gazdele unei aceleiasi retele vor avea acelasi identificator de
retea (acelasi NetID)
• Adresele de broadcast au HostID cu toti bitii 1
• Adresa IP care are HostID cu toti bitii 0 se numeste adresa
retelei – refera intreaga retea
• Exemplu: adresa 85.122.23.0 (adresa network a masinilor
85.122.23.145 si 85.122.23.1
• 127.0.0.1 – adresa de loopback (localhost)
• Din spatiul de adrese ce pot fi alocate efectiv sunt rezervate
urmatoarele (RFC 1918):
• 0.0.0.0 – 0.255.255.255
• 10.0.0.0 – 10.255.255.255 (adrese private)
• 127.0.0.0 – 127.255.255.255 (pentru loopback)
• 172.16.0.0 - 172.31.255.255 (adrese private)
• 192.168.0.0 - 192.168.255.255 (adrese private)
• Adrese private: adrese care nu sunt accesibile spre exterior
(Internetul “real”), ci doar in intranetul organizatiei
Retele private
• Aspecte:
• Cresterea exponentiala a numarului de gazde
• Nu toate masinile gazda ofera resurse accesibile de
pe Internet
• Solutia: NAT (Network Address Translation) – RFC
3022, 4008
• Se reutilizeaza adresele private (RFC 1918)
• Se bazeaza pe inlocuirea adresei private cu adresa IP
neprivata (IP masquerading)
• Functionalitate:
• Ruterele in mod
normal ignora
datagramele continind
adrese private => pot
fi folosite adrese IP
private in cadrul
intranet-ului
organizatiei
• Accesul spre exterior
(Internetul “real”) se
realizeaza via o poarta
(mediating gateway)
ce rescrie adresele IP
sursa/destinatie
Protocolul IP
• Subretele folosind masti de retea
• A aparut ca solutie pentru problema epuizarii spatiului de
adrese IP
• Simplifica rutarea
• Subretelele nu pot fi detectate ca subretele din exterior
Protocolul IP
• Subretele folosind masti de retea
• Divizarea in subretele se va face via masca de retea (netmask): bitii
NetID sunt 1, bitii HostID sunt 0
• Identificatorul subretelei (SubnetID) este utilizat in general sa
grupeze calculatoarele pe baza topologiei fizice
Figura. O cale de a crea o subretea dintr-o retea de clasa B
Protocolul IP
• Subretele folosind masti de retea
• Exemplu:
– Fie adresa IP: 160.0.6.7
10100000 00000000 00000110 00000111
– Masca de retea: 255.255.252.0
11111111 11111111 11111100 00000000
– Adresa de retea: 160.0.4.0
10100000 00000000 00000100 00000000
Adresa retelei = masca de retea AND adresa IP
• Masti de subretea implicite:
• 255.0.0.0 Clasa A
• 255.255.0.0 Clasa B
• 255.255.255.0 Clasa C
Protocolul IP
• Conventii de notare: x.x.x.x/m inseamna ca se aplica o masca
de m biti adresei IP precizata de x.x.x.x
• Exemplu:
• 10.0.0.0/12 – se aplica o masca de 12 biti adresei 10.0.0.0,
selectindu-se valorile posibile in ultimii 20 de biti (=32-12) de
adresa
• 85.122.16.0/20 – se aplica o masca de 20 biti adresei
85.122.16.0
Nivelul Retea
• Protocoale
• ICMP (RFC 792)
• ARP (RFC 826)
• RARP (RFC 903)
• BOOTP (RFC 951,1048,1084)
• DHCP
• De la IPv4 la IPv6
Protocolul ICMP
• ICMP – Internet Control Message Protocol
• Utilizat pentru schimbul de mesaje de control
• Foloseste IP
• Mesajele ICMP sunt procesate de software-ul IP, nu de
procesele utilizatorului
• Tipuri de mesaje :
Tipul mesajului Descriere
8 Echo Request Intreaba o masina daca este activa
0 Echo Replay “Da, sunt activa”
3 Destination Unreachable Pachetul nu poate fi livrat (e.g. DF setat)
5 Redirect Schimbarea rutei
11 Time Exceeded A expirat timpul
… etc (RFC 792) http://www.iana.org/assignments/icmp-parameters
Protocolul ICMP
• Utilizat de:
• comanda ping (Packet Internet Gropher)
• comanda traceroute
• Se trimite un pachet cu TTL=1 (1 hop)
• Primul router ignora pachetul si trimite inapoi un mesaj
ICMP de tip “time-to-live exceeded”
• Se trimite un pachet cu TTL=2 (2 hop-uri)
• Al doilea router ignora pachetul si trimite inapoi un
mesaj “time-to-live exceeded”
• Se repeta pina cind se primeste raspuns de la destinatie
sau s-a ajuns la numarul maxim de hop-uri
Rezolutia adreselor
• Adrese IP <-> adrese hardware (fizice)
• Procesul de a gasi adresa hardware a unei gazde stiind adresa IP se
numeste rezolutia adresei (address resolution) – protocolul ARP
(RFC 826)
• ARP – protocol de tip broadcast (fiecare masina primeste
cererea de trimitere a adresei fizice, raspunde doar cea in cauza)
• Procesul de a gasi adresa IP pe baza adresei hardware se numeste
rezolutia inversa a adresei (reverse address resolution) – protocolul
RARP (RFC 903)
• Utilizat la boot-are de statiile de lucru fara disc
• BOOTP (RFC 951,1048,1084)
IPv6
• Context:
– Probleme de adresabilitate via IPv4 clasic:
• Cresterea exponentiala a numarului de gazde
(e.g. IoT)
• Aparitia unor tabele de rutare de mari
dimensiuni
• Configuratii tot mai complexe, utilizatori tot mai
multi
• Imposibilitatea asigurarii calitatii serviciilor
(QoS)
– Presiuni din partea operatorilor de telefonie
mobila 35
• Obiective pentru un nou protocol:
– Suport pentru miliarde de gazde
– Reducerea tabelelor de rutare
– Simplificarea protocolului
– Suport pentru gazde mobile
– Compatibilitatea cu vechiul IP
– Suport pentru evolutiile viitoare ale Internet-ului
• RFC 2460, 2553
IPv6
• Aspecte:
– Adresele IPv6 au lungime de 16 octeti - 2
128 adrese
– Notatie: 16 numere hexa, fiecare de 2 cifre, delimitate de “:”
• Exemplu: 2001:0db8:0000:0000:0000:0000:1428:57ab
• Daca unul sau mai multe din grupurile de 4 cifre este 0000,
zerourile pot fi omise si inlocuite (o singura data) cu “::”
– Exemplu: 2001:0db8::1428:57ab
– Pentru pastrarea compatibilitatii: adresele IP publice sunt
considerate un subset al spatiului de adrese IPv6
– Adresele IPv4 in IPv6 pot fi scrise astfel:
10.0.0.1 -> ::10.0.0.1 sau 0:0:0:0:0:0:A00:1
• ICMPv6
– Ofera functiile ICMP (raportarea transmiterii datelor,
erorilor, etc.) plus:
• Descoperirea vecinilor (Neighbor Discovery Protocol –
NDP) - Inlocuieste ARP
• Descoperirea ascultatorilor multicast (Multicast
Listener Discovery) – inlocuieste IGMP (Internet
Group Management Protocol)
– Detalii in RFC 4443
');
INSERT INTO `cursuri` VALUES (4,'Cursul 4
Nivelul Transport
Lenuta Alboaie
adria@info.uaic.ro
https://profs.info.uaic.ro/~computernetworkscursullaboratorul.php
Cuprins
Nivelul Transport
• Preliminarii
• UDP (User Datagram Protocol)
• TCP (Transmission Control Protocol)
• TCP versus UDP
Furnizoare de
servicii de
transport
Nivelul transport|Preliminarii
Utilizatoare de
servicii de
Transport
Figura. Modelul OSI
[conform Computer
Networks, 2010 –
Andrew S.
Tanenbaum, et.al.]
Nivelul Transport
• Relatia (logica) intre nivele: retea-transport-aplicatie
Entitatea de transport: utilizeaza
serviciile nivelului retea si ofera
servicii nivelului superior
TPDU (Transport Protocol Data Unit) –
unitatea de date pentru transport
[conform Computer Networks, 2010
– Andrew S. Tanenbaum, et.al.]
adresa IP
adresa IP: port
• Ofera servicii mult mai fiabile decat cele de la nivelul retea (e.g.
pachetele pierdute/incorecte de la nivelul retea pot fi
detectate/corectate la nivelul transport)
• Calitatea serviciilor – QoS (Quality of Service)
– Intarzierea la stabilirea conexiunii
– Productivitatea sau rata de transfer
– Intirzierea la transfer
– Rata reziduala a erorilor
– Protectia
– Prioritatea
– Rezilienta
• Asigura comunicarea logica dintre procese rulind pe host-uri
diferite (comunicare end-to-end)
• (Curs anterior!) Nivelul retea asigura comunicarea logica
intre host-uri
• PORT
• Adauga o noua dimensiune adreselor IP de la nivelul retea
• Se asociaza unei aplicatii (serviciu) si nu unei gazde
• Un proces poate oferi mai multe servicii => poate utiliza mai
multe porturi
• Un serviciu poate corespunde mai multor procese
• PORT
– Este un numar pe 16 biti si poate avea valori intre 0 – 65535
– 1-1024 – valori rezervate (well-known), 1-512 servicii de sistem
(IANA – Internet Assigned Number Authority: RFC 1700)
Exemple:
/etc/services : sunt precizate porturile asociate serviciilor
sistem
HTTP – 80; SMTP – 25; telnet – 23; SSH - 22
Primitive generale
– Permit utilizatorilor nivelului transport (e.g. programe de
aplicatie) sa acceseze serviciile
Primitiva Unitatea de date trimisa
(TPDU)
Explicatie
LISTEN (nimic) Se blocheaza pana cand un proces
incearca sa se conecteze
CONNECT CONNECTION REQUEST Incearca sa stabileasca conexiunea
SEND DATA Transmite informatie
RECEIVE (nimic) Se blocheaza pana cand se
primeste date trimise
DISCONNECT DISCONNECTION REQ. Trimisa de partea care vrea sa se
deconecteze
Cele mai importante protocoale la nivelul
transport:
CP (Transmission Control Protocol) –
protocol de transport orientat
conexiune; RFC 793 (1122), 1323
UDP (User Datagram Protocol) –
protocol de transport neorientat
conexiune; RFC 768
• Protocol de transport neorientat conexiune,
nesigur, minimal
• Nu ofera nici o calitate suplimentara serviciilor
• Nu recurge la negocieri sau la confirmari ale
primirii datelor
UDP
• Analogie: UDP – similar postei terestre
Trimiterea unei scrisori
Nu se garanteaza
ordinea receptionarii
Mesajul se poate pierde
• Utilizeaza IP
• Pentru a oferii servicii de comunicare intre
procese foloseste porturi
• UDP transmite pachete: antet (8 bytes) +
continut
UDP
Figura: Antet UDP [conform Computer Networks, 2010
– Andrew S. Tanenbaum, et.al.]
• Source port si
Destination port
identifica “endpoint”-urile de pe
masinile sursa si
destinatie
UDP
Figura: Antet UDP
• UDP length =
8 bytes +
dimensiunea
continutului
• UDP
checksum
nu este
obligatoriu
• Exemple de utilizari:
– DNS (Domain Name System)
Use-case: A are nevoie de IP-ul host-ului cu numele
www.info.uaic.ro
Pas 1. A trimite un pachet UDP continind numele
host-ului : www.info.uaic.ro
Pas 2. Serverul de DNS trimite un pachet UDP de
raspuns continind adresa IP a host-ului : 85.122.23.146
– RPC (Remote Procedure Call) – mecanism de apel
al procedurilor la distanta
UDP
• Ce nu ofera?
– Controlul fluxului
– Controlul erorilor
– Retransmisia la receptionarea unui pachet eronat
• Ce ofera?
– Folosind port-uri extinde protocolul IP pentru comunicarea
intre procese aflate pe host-uri diferite si nu numai intre
host-uri
• Controleaza fluxul de date (stream-oriented)
• Utilizat de multe protocoale de aplicatii: HTTP, SMTP, …
• Protocol de transport
orientat conexiune,
fara pierdere de
informatii
• Vizeaza oferirea
calitatii maxime a
serviciilor
• Integreaza mecanisme
de stabilire si de
eliberare a conexiunii
• Analogie: TCP – similar telefoniei
TCP
Initierea unei
convorbiri
Dialogul dintre parti
Terminarea convorbirii
[conform Retele de calculatoare – curs
2007-2008, Sabin Buraga]
• Utilizeaza conexiuni, nu porturi ca abstractiuni fundamentale
• Ambele parti (expeditorul, destinatarul) trebuie sa participe la
realizarea conexiunii
• Conexiunile se identifica prin perechi reprezentate de
adresa IP:PORT (soclu - socket)
– Exemplu:
(85.122.23.146: 12345, 85.122.23.146: 22)
• Una din parti ofera o deschidere pasiva - asteapta aparitia unei
cereri de conectare a partenerului de comunicare care
realizeaza o deschidere activa
• Un soclu poate fi partajat de conexiuni multiple de pe aceeasi
masina
• Conexiunile TCP sunt full-duplex
• O conexiune TCP este un flux de octeti si nu un flux de mesaje
Exemplu:
- Emitatorul trimite 4 fragmente de 512 octeti
- Receptorul poate primi:
- 1. doua fragmente de 1024 de octeti
- 2. un fragment de 1 octet si unul de 2047 de octeti
- 3. … (orice alta combinatie)
Patru segmente de 512 octeti
trimise ca datagrame IP separate
Livrarea celor 2048
octeti catre aplicatie
Antet IP
Antet TCP
Client
Server
Legenda:
-Fiecare linie este
etichetata cu o pereche
eveniment/actiune
Exemplu: ACK/-
[conform Computer
Networks, 2010 – Andrew
S. Tanenbaum, et.al.]
Automatul finit TCP
Modeleaza comportamentul protocolului
Starile sunt utilizate la managementul conexiunii
Antetul TCP
Cimpurile Source Port si Destination
Port identifica punctele finale ale
conexiunii
TCP
Flaguri de control
– URG (URGence) (1 bit) – daca este setat, campul Urgent
Pointer este folosit
– ACK (ACKnowledgment)
daca este setat campul Acknowledge Number este folosit;
este setat in toate pachetele de confirmare
Antetul TCP
• Flaguri de control
– PSH (PuSH)– datele vor fi
transmise imediat aplicatiei
destinatare
– RST (ReSeT) – semnalizeaza erori in conexiune (e.g.
deschiderea unei conexiuni este refuzata)
Antetul TCP
• Flaguri de control
– SYN (SYNchronize)
• folosit pentru stabilirea
conexiunii
(Cererea de conexiune: SYN=1,
ACK=0; Raspunsul la cerere:
SYN=1, ACK=1; )
• indica cererea de conexiune si conexiune
acceptata
– FIN (FINish)- indica inchiderea conexiunii
Antetul TCP
Campul Sequence Number
(SEQ)
- Daca flagul SYN este setat
=> SEQ are valoarea initiala
a numarului de ordine;
- Daca flagul SYN este nesetat => SEQ are ca valoare
numarul de ordine a primului octet trimis in acest
pachet
Antetul TCP
Campul Acknowldge Number
- Daca flagul ACK este setat
=> are valoarea numarului
de ordine al urmatorului
octet care se asteapta a fi
receptionat;
Campul Window size – numarul de octeti pe care
receptorul doreste sa ii receptioneze (controlul
fluxului)
Antetul TCP
Campul Checksum – folosit
pentru verificarea sumei de
control al pachetului TCP
(antet si data)
Campul Urgent Pointer – daca flagul URG este setat,
indica deplasamentul fata de numarul curent de
ordine la care se gaseste informatia urgenta
Stabilirea conexiunii -> Three-way handshaking
Administrarea conexiunii TCP
CONNECT LISTEN
[conform Computer
Networks, 2010 – Andrew
S. Tanenbaum, et.al.]
Controlul fluxului
Mecanism general:
• Protocol de comunicare simplu: se trimite un pachet si
apoi se asteapta confirmarea de primire de la
destinatar inainte de a trimite pachetul urmator.
• Daca confirmarea (ACK) nu este primita intr-un interval
de timp prestabilit, pachetul este trimis din nou
Emitator Receptor
Trimite pachetul 1 Primeste pachetul 1;
confirma (ACK) primirea
Trimite pachetul 2 Primeste pachetul 2;
confirma (ACK) primirea
Problema: mecanismul asigura siguranta comunicarii dar
determina folosirea doar a unei parti din banda disponibila a
retelei
Fiabilitatea
Comunicarii
(reliability)
Administrarea conexiunii TCP
Fereastra glisanta – context:
– TCP asigura un flux de octeti => numerele de secventa sunt
atribuite fiecarui octet din stream
– TCP imparte fluxul de octeti in segmente TCP; segmentele trimise
si confirmarile vor transporta numere de secventa (vezi slide 19)
– Dimensiunea ferestrei este exprimata in octeti si nu in numar de
pachete
– Dimensiunea ferestrei este determinata de catre receptor cind
conexiunea este stabilita si este variabila in timpul transferului de
date; Fiecare mesaj ACK va include dimensiunea ferestrei pe care
receptorul este apt sa opereze in momentul respectiv al
comunicarii
Controlul fluxului
• Protocol de comunicare cu fereastra glisanta :
– emitatorul grupeaza pachetele intr-un buffer
– emitatorul poate transmite pachetele din fereastra fara sa receptioneze o confirmare (ACK),
dar porneste cate un cronometru (care va semnaliza depasirea unui interval de timp
prestabilit) pentru fiecare dintre pachete
- receptorul trebuie sa confirme fiecare pachet primit, indicand numarul de secventa al
ultimului octet receptionat corect
– in urma confirmarilor primite emitatorul deplaseaza fereastra (o gliseaza)
Emitator Receptor
Trimite pachetul 1
Primeste pachetul 1;
confirma (ACK 1) primirea
1 2 3 4 5 6 7 8 9 …
Fereastra Trimite pachetul 2
Trimite pachetul 3
Trimite pachetul 4
Trimite pachetul 5
1 2 3 4 5 6 7 8 9 … Primeste ACK 1
Fereastra
Poate trimite pachetul 6
Directia de deplasare a ferestrei …
Controlul fluxului folosind fereastra glisanta – situatii
• Pachetul 2 s-a pierdut
– emitatorul nu receptioneaza ACK 2, deci fereastra ramine pe pozitia 1
– receptorul nu primeste pachetul 2, si nu va confirma inca pachetele 3,4,5
– cronometrul emitatorului va semnaliza timpul de asteptare a confirmarii
si pachetul este retransmis
– receptorul primeste pachetul 2 si va emite confirmarea ACK 5 (secventa
de pachete 2-5 au fost receptionate cu succes) => fereastra glisanta se
deplaseaza cu patru pozitii dupa receptionarea ACK 5
• Pachetul 2 a ajuns la destinatie dar confirmarea s-a pierdut
– Emitatorul nu primeste ACK 2, dar primeste ACK 3 (toate pachetele pina
la 3 au ajuns cu succes) => emitentul deplaseaza fereastra glisanta la
pachetul 4
Administrarea conexiunii TCP
Ferastra glisanta asigura:
– Transmisie sigura
– Folosirea mai buna a latimii de banda => o mai
mare viteza de transmisie
– Controlul transmisiei (receptorul poate intarzia
confirmarea datelor, cunoscind memoria libera de
care dispune si dimensiunea ferestrei de
comunicare)
• Detectia erorilor & retransmiterea datelor
– Fiecare segment trimis contine un numar de secventa
(Sequence Number) indicind pozitia octetilor transmisi in cadrul
fluxului de date
– Gazda destinatar verifica numarul de secventa pentru fiecare
segment (se testeaza daca anumite segmente se pierd, sunt
duplicate sau nu sunt in ordine) si trimite inapoi pentru fiecare
segment un numar de confirmare (Acknowledgment Number),
specificind numarul de secventa al urmatorului octet care se
astepta a fi receptionat
– Segmentele pierdute sunt detectate folosindu-se un timer de
retransmisie a datelor
– Pentru detectarea erorilor se utilizeaza si checksum-uri
• Resetarea conexiunii
– Uneori conditii anormale forteaza aplicatiile sau
software-ul de retea sa distruga conexiunea
– Pentru resetarea conexiunii, o parte a comunicarii
initiaza terminarea, trimitind un segment cu bitul
RST setat
– Cealalta parte abandoneaza conexiunea, fara a se
mai transmite eventuale date ramase netransmise
– Transferul in ambele directii este oprit, buffer-ele
sunt golite
• Fortarea transmiterii datelor
– TCP poate divide fluxul de date in segmente de
dimensiuni diferite de pachetele vehiculate de aplicatii
=> eficienta transmisiei
– Uneori intervine situatia de a transmite datele fara a
se mai astepta umplerea buffer-elor (e.g., aplicatii
interactive)
– Fortarea transmiterii se realizeaza prin push: se
seteaza bitul PSH si se forteaza transmiterea
segmentelor, indiferent de starea de umplere a bufferelor
• Inchiderea conexiunii
– Conexiunile TCP fiind full-duplex, cand o aplicatie
semnaleaza ca nu mai exista date de trimis, TCP va
inchide conexiunea doar intr-o directie
• Partenerul de comunicatie poate expedia un
segment TCP cu bitul FIN setat; confirmarea
semnifica ca sensul respectiv de comunicare
este efectiv oprit
– Conexiunea este desfiintata cand ambele directii
au fost oprite
TCP
• Automatul finit TCP
– Stabilirea conexiunii:
• CLOSED – din aceasta stare se poate cere o deschidere activa (se
trece in SYN_SENT) sau pasiva (SYN_RCVD)
• LISTEN – se poate trimite o cerere de conexiune activa (se trece in
SYN_SENT) ori pasiva (SYN_RCVD)
– Conexiune stabilita:
• ESTABLISHED – poate incepe transmisia de date (din aceasta stare
se poate trece in CLOSE_WAIT sau FIN_WAIT_1)
– Deconectarea initiata de procesul partener
• CLOSE_WAIT, LAST_ACK, CLOSE
– Stari ce intervin in procesul de deconectare
• FIN_WAIT_1, FIN_WAIT_2, CLOSING, TIME_WAIT
• Exemple de utilizari ale TCP:
– Majoritatea protocoalelor de aplicatii:
• HTTP
• TELNET
• SMTP
• SSH
• …
• Ambele se bazeaza pe IP, utilizeaza porturi
• Unitatea de transmisie
– TCP -> Segment TCP
– UDP -> Pachet UDP
• UDP ofera servicii minimale de transport (efort
minim de transmisie)
TCP ofera servicii orientate-conexiune, fullduplex, sigure – pentru transportul fluxurilor
de octeti ( -> mecanism complex de transmisie)
• Utilizarea TCP sau UDP depinde de aplicatie:
e-mail, transfer de fisiere, operare in timp-real,
transmisii multimedia in timp real, chat, …
');
INSERT INTO `cursuri` VALUES (5,'Cursul 5
Programarea in retea I
Lenuta Alboaie
adria@info.uaic.ro
https://profs.info.uaic.ro/~computernetworkscursullaboratorul.php
Cuprins
• Modelul client/server
• API pentru programarea in retea
• Socket‐uri BSD
• Modelul client/server TCP
Modelul client/server
Paradigme ale comunicarii in retea:
modelul client/server
apelul procedurilor la distanta (RPC)
comunicarea punct‐la‐punct (peertopeer – P2P)
Modelul client/server
• Proces server
– Ofera servicii obtinute prin retea
– Accepta (iterativ sau concurent) cereri de la
un proces client, realizeaza un anumit serviciu
si returneaza rezultatul
• Proces client
– Initializeaza comunicarea cu serverul
– Solicita un serviciu,
apoi asteapta raspunsul serverului
• Moduri de interactiune (via canale de comunicatie):
orientat‐conexiune – se foloseste TCP
neorientat‐conexiune – se utilizeaza UDP
• Implementare:
iterativa – fiecare cerere e tratata pe rind, secvential
concurenta – cererile sint procesate concurent
Procese copil pentru fiecare cerere de procesat
Multiplexarea conexiunii
Tehnici combinate
API retea
• Necesitatea existentei unui API
pentru realizarea de aplicatii in retea
– Interfata generica pentru programare
– Suport pentru comunicatii orientate‐conexiune si
prin mesaje
– Compatibilitate cu serviciile I/O comune
– Independenta de hardware si de sistem de operare
– Suport pentru familii (suite) de protocoale multiple
– Independenta in reprezentarea adreselor
– Oferirea de servicii speciale pentru aplicatii
• TCP/IP nu include definirea unui API
• Se pot utiliza mai multe API‐uri
pentru programarea aplicatiilor Internet (TCP/IP)
– Socket‐uri BSD (Berkeley System Distribution)
– TLI (Transport Layer Interface) – AT&T, XTI
– Winsock
– MacTCP
• Functii oferite:
specificare de puncte terminale locale si la distanta,
initiere si acceptare de conexiuni, trimitere si receptare
de date, terminare conexiune, tratare erori
Cuprins
• Interfata de programare
a aplicatiilor (API)
bazata pe socket‐uri BSD
– Caracterizare
– Creare
– Primitive
Socket
• Socket‐uri BSD (Berkeley System Distribution)
• Facilitate generala, independenta de hardware,
protocol si tipul de transmitere,
pentru comunicarea intre procese
aflate pe masini diferite, in retea
• Suporta pentru familii multiple de protocoale
– Protocolul domeniului UNIX pentru comunicatii
(locale) intre masini UNIX (e.g., uucp)
– Protocolul domeniului Internet folosind TCP/IP
– Altele: XNS Xerox, ISO/OSI,…
• Independenta in reprezentarea adreselor
• Abstractiune a unui punct terminal (endpoint)
la nivelul transport
• Utilizeaza interfata de programare
I/O existenta
(similar fisierelor, pipe‐urilor, FIFO‐urilor etc.)
• Poate fi asociat cu unul/mai multe procese,
existind in cadrul unui domeniu de comunicatie
• Ofera un API pentru programarea in retea,
avind implementari multiple
Similar unui descriptor de fisier
Diferente apar la creare si la diferite operatiuni
de control al socket‐urilor
Socket | primitive de baza
socket() creeaza un nou punct terminal al conexiunii
bind() ataseaza o adresa locala la un socket
listen() permite unui socket sa accepte conexiuni
accept() blocheaza apelantul pina la sosirea
unei cereri de conectare (utilizata de serverul TCP)
connect() tentativa (activa) de stabilire a conexiunii
(folosita de clientul TCP)
send()/receive() trimitere/receptare de date via socket
close() elibereaza conexiunea (inchide un socket)
shutdown() inchide directional un socket
• Alte apeluri
– citire de date
read() / readv() / recvfrom() / recvmsg()
– trimitere de date
write() / writev() / sendto() / sendmsg()
– multiplexare I/O
select()
– administrarea conexiunii
fnctl() / ioctl() / setsockopt() / getsockopt()
getsockname() / getpeername()
Socket‐uri|creare
• Apelul de sistem (primitiva) socket()
#include <sys/types.h>
#include <sys/socket.h>
int socket (int domain, int type, int protocol)
Domeniul de comunicare:
AF_UNIX, AF_INET,
AF_ROUTE
Protocolul utilizat
pentru transmitere
(uzual: 0 pentru niv. transp.)
Modalitatea de realizare a comunicarii:
SOCK_STREAM, SOCK_DGRAM, SOCK_RAW
• Valoarea de retur
– Succes: descriptorul de socket creat
– Eroare: –1
• Raportarea erorii se realizeaza via errno
– EMFILE
– ENFILE
– EACCES
– EPROTONOSUPPORT
– ENOMEM
– ENOBUFFERS
– EINVAL
Socket‐uri
• Domeniul & tipul unui socket si protocoalele folosite
AF_LOCAL ≡ AF_UNIX
(din motive istorice)
AF_INET AF_INET6 AF_LOCAL AF_ROUTE
SOCK_STREAM TCP TCP Da
SOCK_DGRAM UDP UDP Da
SOCK_RAW IP IPv6 Da
• Observatii
– Primitiva socket() aloca resursele necesare
unui punct terminal de comunicare,
dar nu stabileste modul de adresare
– Socket‐urile ofera un mod generic de adresare
– Pentru TCP/IP trebuie specificate (adresa IP, port)
– Alte suite de protocoale pot folosi
alte scheme de adresare
• Tipuri POSIX: int8_t, uint8_t, int16_t, uint16_t, int32_t,
uint32_t, u_char, u_short, u_int, u_long
• Tipuri POSIX folosite de socket‐uri:
– sa_family_t – familia de adrese
– socklen_t – lungimea structurii de memorare
– in_addr_t – adresa IP (v4)
– in_port_t – numarul de port
• Specificarea adreselor generice
struct sockaddr {
uint8_t sa_len;
sa_family_t sa_family;
char sa_data[14];
};
• Tipul sockaddr permite oricare tip de adresare
• Exemplu: folosirea socket‐urilor
pentru comunicarea dintre studenti
– Tipul de adresa: AF_STUDENTS
– Valori de adrese:
Zaq ⇔ 1, Moko ⇔ 2, Tux ⇔ 3,…
– Initializarea structurii AF_STUDENTS
pentru a indica un anumit student:
struct sockaddr un_stud;
un_stud.sa_family = AF_STUDENTS;
un_stud.sa_data[0] = 3;
Tux
• Pentru AF_INET vom avea nevoie de
16 biti – numarul de port si de 32 biti – adresa IPv4
• Se foloseste o structura speciala: sockaddr_in
struct sockaddr_in {
uint8_t sin_len;
sa_family_t sin_family;
in_port_t sin_port;
struct in_addr sin_addr;
char sin_zero[8];
};
struct in_addr {
in_addr_t s_addr;
};
Socket‐uri
• Toate valorile stocate in sockaddr_in vor respecta
ordinea de codificare a retelei (network byte order)
sin_port un numar de port TCP/IP
sin_addr o adresa IP
• ‘h’ : host byte order ‘n’ : network byte order
• ‘s’ : short (16 biti) ‘l’ : long (32 biti)
uint16_t htons(uint16_t);
uint16_t ntohs(uint_16_t);
uint32_t htonl(uint32_t);
uint32_t ntohl(uint32_t);
• Pentru IPv6, se foloseste sockaddr_in6
struct sockaddr_in {
u_int16_t sin6_family; /* AF_INET6 */
u_int16_t sin6_port;
u_int32_t sin6_flowinfo;
u_int32_t sin6_scope_id;
struct in6_addr sin6_addr;
};
struct in6_addr {
unsigned char s6_addr[16];
};
Socket‐uri|asignarea unei adrese
• Asignarea unei adrese la un socket existent
se realizeaza cu bind()
int bind ( int sockfd,
const struct sockaddr *myaddr,
int addrlen );
• Se returneaza: 0 succes, –1 eroare
variabila errno contine eroarea efectiva: EBADF,
ENOTSOCK, EADDRINUSE, EINVAL, EACCESS
const!
• Exemplu:
#define PORT 7000
int sd, eroare;
struct sockaddr_in adresa;
sd = socket (AF_INET, SOCK_STREAM, 0); /* TCP */
adresa.sin_family = AF_INET; /* umplerea structurii */
adresa.sin_port = htons (PORT); /* portul */
adresa.sin_addr = htonl (adresaIP); /* adresa IP */
eroare = bind (sd, (sockaddr *) &adresa, sizeof (adresa));
• Utilizari ale lui bind()
– Serverul doreste sa ataseze un socket la un port pre‐
stabilit (pentru a oferi servicii via acel port)
– Clientul vrea sa ataseze un socket la un port specificat
– Clientul cere sistemului de operare sa asigneze
orice port disponibil
• In mod normal, clientul nu necesita atasarea
la un port specificat
• Alegerea oricarui port liber:
adresa.port = htons (0);
• Alegerea adresei IP la bind()
– Daca gazda are asignate mai multe adrese IP?
– Cum se rezolva independenta de platforma?
• Pentru a atasa un socket la adresa IP locala, se va utiliza
in locul unei adrese IP constanta INADDR_ANY
• Conversia adreselor IP:
int inet_aton ( void *, struct in_addr *);
ASCII “x.x.x.x” ⇒ reprezentare interna pe 32 biti
char *inet_ntoa ( struct in_addr );
reprezentare 32 biti (network byte order)
⇒ ASCII “x.x.x.x”
vezi si functia inet_addr()
• Observatii:
– Pentru IPv6 in locul constantei INADDR_ANY
se va folosi – vezi antetul netinet/in.h:
serv.sin6.addr = in6addr_any;
– Functiile de conversie pentru IPv6 sunt:
inet_pton()
inet_ntop()
Socket‐uri|listen()
• Stabilirea modului pasiv de interactiune
– Adresa intotdeauna este cunoscuta
– Nucleul sistemului va trebui sa accepte cereri
de conectare directionate la adresa la care
este atasat socket‐ul
3way handshake
– Conexiunile multiple receptionate
vor fi plasate intr‐o coada de asteptare
– Se returneaza 0 = succes, –1 = eroare
int listen ( int sockfd, int backlog );
Socket TCP atasat unei adrese
Numarul
de conex.
din coada
de astept.
• Remarci:
– Alegerea valorii backlog depinde
de aplicatie – in mod uzual 5
– Serverele HTTP ar trebui sa specifice
o valoare backlog cit mai mare
(din cauza incarcarii cu cereri multiple)
Socket‐uri|accept()
• Asteptarea conexiunilor din partea clientilor
– Cind aplicatia este pregatita pentru a trata o noua
conexiune, va trebui sa interogam sistemul asupra
unei alte conexiuni cu un client
– Se returneaza descriptorul de socket corespunzator
punctului terminal al clientului sau –1 = eroare
int accept( int sockfd,
struct sockaddr* cliaddr,
socklen_t *addrlen );
Socket TCP
(mod pasiv)
• trebuie initial sa fie egal cu lungimea structurii cliaddr
• se va returna numarul de bytes folositi in cliaddr
Socket‐uri|connect()
• Incercarea de a stabili o conexiune cu serverul
– Stabilirea unui punct terminal (al serverului)
– Nu necesita atasarea cu bind(), sistemul
de operare va asigna o adresa locala (IP, port)
– Se incearca stabilirea unei conexiuni
3way handshake
int connect( int sockfd,
const struct sockaddr *server,
socklen_t addrlen );
Socket TCP
Contine adresa
serverului
(IP, port)
Socket‐uri|connect()
• Returneaza:
– Valoarea 0 = succes
– Valoarea –1 = eroare
• EISCONN
• ETIMEDOUT
• ECONNREFUSED
• ENETUNREACH
• EADDRINUSE
• EINPROGRESS
• EADDRNOTAVAIL
• EAFNOSUPPORT
I/O TCP|read()
• Apelul este blocant in mod normal,
read() returneaza doar cind exista date disponibile
• Citirea de la un socket TCP poate returna
mai putini octeti decit numarul maxim dorit
• Trebuie sa fim pregatiti sa citim cite 1 byte
la un moment dat!
• Daca partenerul a inchis conexiunea si nu mai sunt date
de primit, se returneaza 0 (EOF)
• Erori: EINTR – un semnal a intrerupt citirea,
EIO – eroare I/O, EWOULDBLOCK – socket‐ul nu are date
intr‐o citire neblocanta
int read ( int sockfd, void *buf, int max );
I/O TCP|write()
• Apelul este blocant in mod normal
• Pentru un socket neblocant,
write() poate scrie mai putin de num octeti
• Erori:
– EPIPE – scriere la un socket neconectat
– EWOULDBLOCK – nu se pot accepta date
fara blocare, insa operatiunea este setata
ca fiind neblocanta
int write ( int sockfd, void *buf, int num );
I/O TCP|exemplu
#define MAXBUF 127 /* lungime buffer citire */
char *cerere = “da-mi ceva”;
char buf[MAXBUF]; /* buffer pentru raspuns */
char *pbuf = buf; /* pointer la buffer */
int n, lung = MAXBUF;
/* nr. bytes cititi,
nr. bytes liberi in buffer */
/* trimitem cererea */
write (sd, cerere, strlen (cerere));
/* asteaptam raspunsul */
while ((n = read (sd, pbuf, lung)) > 0) {
pbuf += n;
lung -= n;
} Comunicarea dintre client si server
Inchiderea conexiunii|close()
• Terminarea “gratioasa” a conexiunii
• Dealocarea memoriei alocate socket‐ului
– 3way handshake pentru inchiderea conexiunii
– Pentru procese care partajeaza acelasi socket,
se decrementeaza numarul de referinte la acel socket;
cind ajunge la 0, socket‐ul este dealocat
• Probleme
– Serverul nu poate termina conexiunea,
nu stie daca si cind clientul nu va mai trimite si alte cereri
– Clientul nu poate sti daca datele au ajuns la server
int close ( int sockfd );
Inchiderea conexiunii|shutdown()
• Inchiderea unidirectionala
– Cind un client termina de trimis cererile, poate apela
shutdown() pentru a specifica faptul ca nu va mai trimite
date pe socket, fara a dealoca socket‐ul
– Serverul va primi EOF si, dupa expedierea catre client
a ultimului raspuns, va putea inchide conexiunea
int shutdown ( int sockfd, int dir );
• 0 nu se accepta operatii de citire (SHUT_RD)
• 1 nu se accepta operatii de scriere (SHUT_WR)
• 2 nu se accepta operatii I/O
inchidere in ambele sensuri (SHUT_RDWR)
Client/server TCP|server
• Modelul unui server TCP iterativ
– Creare socket pentru tratarea conexiunilor cu clientii: socket()
– Pregatirea structurilor de date (sockaddr_in)
– Atasarea socket‐ului la adresa locala (port): bind()
– Pregatirea socket‐ului pentru ascultarea portului
in vederea stabilirii conexiunii cu clientii: listen()
– Asteptarea realizarii unei conexiuni cu un anumit client
(deschidere pasiva): accept()
– Procesarea cererilor clientului, folosindu‐se socket‐ul returnat
de accept(): succesiune de read()/write()
– Inchiderea (directionata) a conexiunii cu clientul:
close(), shutdown()
Client/server TCP|client
• Modelul unui client TCP iterativ
– Creare socket pentru conectarea la server: socket()
– Pregatirea structurilor de date (sockaddr_in)
– Atasarea socket‐ului: bind() – optional
– Conectarea la server (deschidere activa): connect()
– Solicitarea de servicii si receptionarea rezultatelor
trimise de server: succesiune de write()/read()
– Inchiderea (directionata) a conexiunii cu serverul:
close(), shutdown()
');
INSERT INTO `cursuri` VALUES (6,'Cursul 6
Programarea in retea (II)
Lenuta Alboaie
adria@info.uaic.ro
https://profs.info.uaic.ro/~computernetworkscursullaboratorul.php
Client/Server UDP
• Pentru socket() se va folosi SOCK_DGRAM
• Apelurile listen(), accept(), connect() nu vor mai fi
utilizate in mod uzual
• Pentru scriere de datagrame se pot folosi sendto()
sau send() (mai general)
• Pentru citire de datagrame se pot folosi recvfrom()
sau recv()
• Nimeni nu garanteaza ca datele expediate au ajuns
la destinatar sau nu sunt duplicate
Client/Server UDP
• Socket-urile UDP pot fi “conectate”: clientul poate folosi
connect() pentru a specifica adresa (IP, port) a punctului
terminal (serverul) – pseudo-conexiuni:
– Utilitate: trimiterea mai multor datagrame la acelasi
server, fara a mai specifica adresa serverului pentru
fiecare datagrama in parte
– Pentru UDP, connect() va retine doar informatiile despre
punctul terminal, fara a se initia nici un schimb de date
– Desi connect() raporteaza succes, nu inseamna ca
adresa punctului terminal e valida sau serverul este
disponibil
Client/Server UDP
• Pseudo-conexiuni UDP
– Se poate utiliza shutdown() pentru a opri
directionat transmiterea de date, dar nu
se va trimite nici un mesaj partenerului
de conversatie
– Primitiva close() poate fi apelata si pentru
a elimina o pseudo-conexiune
Alte primitive| I/O
#include <sys/types.h>
#include <sys/socket.h>
int send (int sockfd, char *buff, int nbytes, int flags);
int recv (int sockfd, char *buff, int nbytes, int flags);
• Pot fi folosite in cadrul comunicatiilor orientate conexiune sau pentru
pseudo-conexiuni
Apelurile send() si recv() presupun că sunt cunoscute toate elementele
unei asocieri, adică a fost efectuat în prealabil un apel connect()
• Primele 3 argumente sunt similare cu cele de la write(), respectiv read()
• Argumentul a patrulea este de regulă 0, dar poate avea si alte valori
care precizează condiții de efectuare a apelului
• Cele 2 apeluri returnează la execuție normală lungimea transferului în
octeți
Alte primitive| I/O
#include <sys/types.h>
#include <sys/socket.h>
int sendto ( int sockfd, char *buff, int nbytes, int flags,
struct sockaddr *to, int addrlen);
int recvfrom (int sockfd, char *buff, int nbytes, int flags,
struct sockaddr *from, int *addrlen);
• Sunt folosite pentru comunicatii neorientate conexiune
• La sendto() si recvfrom() elementele pentru identificarea
nodului la distanță se specifică în apel, prin ultimele 2
argumente
• Cele 2 apeluri returnează la execuție normală lungimea
transferului în octeți
Alte primitive| I/O
#include <sys/uio.h>
ssize_t readv (int fd, const struct iovec *iov, int iovcnt);
ssize_t writev (int fd, const struct iovec *iov, int iovcnt);
– Mai generale decit read()/write(), ofera posibilitatea de a
lucra cu date aflate in zone necontigue de memorie
#include <sys/types.h>
#include <sys/socket.h>
ssize_t recvmsg (int s, struct msghdr *msg, int flags);
ssize_t sendmsg (int s, const struct msghdr *msg, int flags);
– Receptioneaza/transmite mesaje extragindu-le din
structura msghdr
Exemplu de server/client UDP
DEMO
Server UDP Client UDP
Alte primitive|informatii
• getpeername() – returneaza informatii despre celalalt capat al
conexiunii
#include <sys/socket.h>
int getpeername (int sockfd, struct sockaddr *addr,
socklen_t *addrlen);
• getsockname() – returneaza informatii asupra socketului(local)
specificat –> (adresa la care este atasat)
#include <sys/socket.h>
#include <sys/types.h>
int getsockname( int sockfd, struct sockaddr * addr,
socklen_t * addrlen);
Programare retea avansata
• Optiuni atasate socket-urilor
– getsockopt() si setsockopt()
• Multiplexare I/O
Primitive|optiuni
• Optiuni atasate socket-urilor
– Atribute utilizate pentru consultarea sau
modificarea unui comportament, general ori
specific unui protocol, pentru unele (tipuri de)
socket-uri
– Tipuri de valori:
• Booleene (flag-uri)
• Mai “complexe”:
int, timeval, in_addr, sock_addr, etc
Primitive|optiuni
• getsockopt() – consultarea
optiunilor
#include <sys/types.h>
#include <sys/socket.h>
int getsockopt (int sockfd, int level, int optname, void *optval,
socklen_t *optlen);
Level - indica daca optiunea este generala sau specifica
unui protocol
Level - indica daca optiunea este generala sau specifica
unui protocol
Numele, valoarea si lungimea
optiunii
Exemplu:
len = sizeof (optval);
getsockopt (sockfd, SOL_SOCKET, SO_REUSEADDR, &optval, &len);
Primitive|optiuni
• setsockopt() – setarea
optiunilor
#include <sys/types.h>
#include <sys/socket.h>
int setsockopt (int sockfd, int level, int optname, void *optval,
socklen_t *optlen);
Returneaza:
– 0 = succes
– -1 = eroare: EBADF, ENOTSOCK, ENOPROTOOPT,...
Numele, valoarea si lungimea
optiunii
Primitive|optiuni
Optiuni generale
- Independente de protocol
- Unele suportate doar de anumite tipuri de socketuri
(SOCK_DGRAM, SOCK_STREAM)
– SO_BROADCAST
– SO_ERROR
– SO_KEEPALIVE
– SO_LINGER
– SO_RCVBUF, SO_SNDBUF
– SO_REUSEADDR
- SO_OOBINLINE
-
[http://www.beej.us/guide/bgnet/output/html/multipage/setsockoptman.html]
Primitive|optiuni
• SO_BROADCAST (boolean)
– Activeaza/dezactiveaza trimiterea de date in regim broadcast
– Utilizata doar pentru SOCK_DGRAM
– Previne anumite aplicatii sa nu trimita in mod neadecvat broadcast-uri
• SO_ERROR (int)
– Indica eroarea survenita (similara lui errno)
– Poate fi folosita cu primitiva getsockopt()
• SO_KEEPALIVE (boolean)
– Folosita pentru SOCK_STREAM
– Se va trimite o informatie de proba celuilalt punct terminal daca nu s-a realizat
schimb de date timp indelungat
– Utilizata de TCP (e.g., telnet): permite proceselor sa determine daca
procesul/gazda cealalta a picat
Primitive|optiuni
• SO_LINGER (struct linger)
– Controleaza daca si dupa cit timp un apel de inchidere a conexiunii va
astepta confirmari(ACK-uri) de la punctul terminal
– Folosita doar pentru socket-uri orientate-conexiune pentru a ne asigura ca
un apel close() nu va returna imediat
– Valorile vor fi de tipul:
struct linger {
int l_onoff; /* interpretat ca boolean */
int l_linger; /* timpul in secunde*/
}
– l_onoff = 0: close() returneaza imediat, dar datele netrimise sunt transmise
– l_onoff !=0 si l_linger=0: close() returneaza imediat si datele netrimise sunt
sterse
– l_onoff!=0 si l_linger !=0: close() nu returneaza pina cind datele netrimise
sunt transmise (sau conexiunea este inchisa de sistemul remote)
Primitive|optiuni
• SO_LINGER – Exemplu
int result;
struct linger lin;
lin.l_onoff=1 ; /*0 -> l_linger este ignorata */
lin.l_linger=1; /* 0 = pierderea datelor; nonzero= asteptare pina
se trimit datele */
result= setsockopt( sockfd,
SOL_SOCKET,
SO_LINGER,
&lin, sizeof(lin));
Primitive|optiuni
• SO_RCVBUF/SO_SNDBUF (int)
– Modifica dimensiunile buffer-elor de receptionare sau de
trimitere a datelor
– Utilizate pentru SOCK_DGRAM si SOCK_STREAM
• Exemplu:
int result; int buffsize = 10000;
result= setsockopt (s, SOL_SOCKET, SO_SNDBUF, &buffsize,
sizeof(buffsize));
Primitive|optiuni
• SO_REUSEADDR – (boolean)
– Permite atasarea la o adresa(port) deja in uz
nu incalca regula de asociere unica realizata de bind
– Folosita pentru ca un socket pasiv sa poata folosi un port deja utilizat de alte
procese
Stare 1
Stare 2
• Daca daemon-ul care asculta la portul 2000 este killed, incercarea de restart a
daemon-ului va esua daca SO_REUSEADDR nu este setat
Exemplu
int optval = 1;
setsockopt (sockfd, SOL_SOCKET, SO_REUSEADDR, &optval, sizeof(optval));
bind (sockfd, &sin, sizeof(sin) );
Primitive|optiuni
Optiuni specifice protocolului IP
• IP_TOS permite setarea cimpului “Type Of Service”
(e.g., ICMP) din antetul IP
• IP_TTL permite setarea cimpului “Time To Live” din
antetul IP
Exista si optiuni pentru IPv6.(RFC 2460,2462)
-IPV6_V6ONLY, …
Primitive|optiuni
Optiuni specifice protocolului TCP
• TCP_KEEPALIVE seteaza timpul de asteptare daca
SO_KEEPALIVE este activat
• TCP_MAXSEG stabileste lungimea maxima a unui segment (nu
toate implementarile permit modificarea acestei valori de catre
aplicatie)
• TCP_NODELAY seteaza dezactivarea algoritmului Nagle
(reducerea numarului de pachete de dimensiuni mici intr-o
retea WAN; TCP va trimite intotdeauna pachete de marime
maxima, daca este posibil) – utilizata pentru generatori de
pachete mici (e.g., clienti interactivi precum telnet)
Multiplexare I/O
• Posibilitatea de a monitoriza mai multi descriptori I/O
– Un client TCP generic (e.g., telnet)
– Un client interactiv (e.g., ftp, scp, browser Web,…)
– Un server care poate manipula mai multe protocoale (TCP si
UDP) simultan
– Rezolvarea unor situatii neasteptate (i.e. caderea unui server
in mijlocul comunicarii)
• Exemplu: datele citite de la intrarea standard trebuie scrise la
un socket, iar datele receptionate prin retea trebuie afisate la
iesirea standard
Multiplexare I/O| solutii
• Utilizarea mecanismului neblocant folosind primitivele
fnctl() / ioctl()
• Utilizarea mecanismului asincron
• Folosirea alarm() pentru a intrerupe apelurile de
sistem lente
• Utilizarea unor procese/thread-uri multiple
(multitasking)
• Folosirea unor primitive care suporta verificarea
existentei datelor de intrare de la descriptori de citire
multipli: select() si poll()
Multiplexare I/O| solutii
• Utilizarea mecanismului neblocant folosind primitiva
fnctl()
– Se seteaza apelurile I/O ca neblocante
int flags;
flags = fcntl ( sd, F_GETFL, 0 );
fcntl( sd, F_SETFL, flags | O_NONBLOCK);
– Daca nu sunt date disponibile un apel read() va
intoarce -1 sau daca nu este suficient spatiu in
buffer un apel write() va intoarce -1 (cu eroarea
EAGAIN)
Multiplexare I/O| solutii
Utilizarea mecanismului neblocant folosind primitiva ioctl()
#include <sys/ioctl.h>
ioctl (sd, FIOSNBIO, &arg);
Daca socketul este in mod neblocant, urmatoarele apeluri sunt afectate
astfel:
– accept() – daca nu este prezenta nici o cerere, accept() returneaza cu
eroarea EWOULDBLOCK
– connect() – daca conexiunea nu se poate stabili imediat, connect()
returneaza cu eroarea EINPROGRESS
– recv() – daca nu exista date de primit, recv() returneaza -1 cu eroarea
EWOULDBLOCK
– send() – daca nu exista spatiu in buffer pentru ca datele sa fie transmise,
send() returneaza -1 cu eroarea EWOULDBLOCK
-arg este un pointer la un int
-Daca int are valoare 0, socketul este setat in mod blocant
-Daca int are valoare 1, socketul este setat in mod neblocant
-arg este un pointer la un int
-Daca int are valoare 0, socketul este setat in mod blocant
-Daca int are valoare 1, socketul este setat in mod neblocant
Multiplexare I/O| solutii
Trimiterea si receptarea datelor in mod asincron
– Problema: In conditiile in care socket-urile sunt
create implicit in mod blocant (I/O), cum s-ar putea
instiinta procesul atunci cind se intimpla “ceva” la
un socket?
– Socket-urile asincrone permit trimiterea unui
semnal (SIGIO) procesului
– Socket-urile asincrone permit utilizatorului
separarea “procesarilor socket” de alte procesari
– Generarea semnalului SIGIO este dependenta de
protocol
Trimiterea si receptarea datelor in mod asincron
• Pentru TCP semnalul SIGIO poate aparea cind:
– Conexiunea a fost complet stabilita
– O cerere de deconectare a fost initiata
– Cererea de deconectare a fost realizata complet
– shutdown() pentru o directie a comunicatiei
– Au aparut date de la celalalt punct terminal
– Datele au fost trimise
– Eroare
Multiplexare I/O| solutii
Trimiterea si receptarea datelor in mod asincron
– Pentru UDP semnalul SIGIO apare cind:
• Se receptioneaza o datagrama
• Apare o eroare
– Putem permite proceselor sa realizeze alte
activitati si sa monitorizeze transferurile UDP
Multiplexare I/O| solutii
Trimiterea si receptarea datelor in mod asincron
• Implementarea
– Socket-ul trebuie setat ca fiind asincron
#include <sys/unistd.h>
#include <sys/fcntl.h>
int fcntl (int s, int cmd, long arg)
Exemplu:
int sd = socket(PF_INET, SOCK_STREAM, 0);
fcntl (sd, F_SETFL, O_ASYNC); /* setarea asincrona I/O */
Multiplexare I/O| solutii
Multiplexare I/O| solutii
• Utilizarea alarmelor
while(…){
signal (SIGALRM, alarmHandler);
alarm (MAX_TIME);
read (0,…);
signal (SIGALRM, alarmHandler);
alarm (MAX_TIME);
read (tcpsock,…);...
}
Functie scrisa de
programator
Multitasking
Servere concurente – per-client process
Servere concurente pre-forked
– Se creeaza un numar de procese copil imediat la initializare, fiecare proces
liber interactionind cu un anumit client
Servere concurente pre-threaded
– Ca mai sus, dar se folosesc thread-uri (fire de executie) in locul proceselor
(vezi POSIX threads –pthread.h)
– Exemplu: serverul Apache
Probleme:
– Numarul de clienti mai mare decit numarul de procese/thread-uri
– Numarul de procese/thread-uri prea mare fata de numarul de clienti
– OS overhead
..... (curs viitor)
Multiplexare I/O| solutii
Probleme care apar:
• Folosind apeluri neblocante, se utilizeaza intens
procesorul
• Pentru alarm(), care este valoarea optima a
constantei MAX_TIME?
Multiplexarea I/O|select()
• Permite utilizarea apelurilor blocante pentru un set de descriptori (fisiere, pipeuri, socket-uri,…)
• Suspenda programul pana cand descriptori din liste sunt pregatiti de operatii de
I/O
#include <sys/time.h>
#include <sys/types.h>
#include <unistd.h>
int select (int nfds,
fd_set *readfds,
fd_set *writefds,
fd_set *exceptfds,
struct timeval *timeout);
Multimea
descriptorilor
de citire,
scriere,
exceptie
Multimea
descriptorilor
de citire,
scriere,
exceptie
Timpul de asteptare
Valoarea maxima a
descript. plus 1
Multiplexarea I/O|select()
Manipularea elementelor multimii de descriptori (tipul fd_set) se
realizeaza folosindu-se macrourile:
FD_ZERO (fd_set *set); Sterge multimea de descriptori din
set.
FD_SET (int fd, fd_set *set); Adauga descriptorul fd in multimea
set.
FD_CLR (int fd, fd_set *set); Sterge descriptorul fd din multimea
set.
FD_ISSET(int fd, fd_set *set); Testeaza daca descriptorul fd
apartine sau nu multimii set.
Multiplexarea I/O|select()
Pentru timpul de asteptare se foloseste structura definita in
sys/time.h:
struct timeval {
long tv_sec;/* secunde*/
long tv_usec;/* microsecunde*/
}
• Daca timeout este NULL, select() va returna imediat
• Daca timeout este !=0 specifica intervalul de timp in care
select() va astepta
Multiplexarea I/O|select()
Un descriptor de socket este gata de citire daca:
• Exista octeti receptionati in buffer-ul de intrare (se
poate face read() care va returna >0)
• O conexiune TCP a receptionat FIN (read() returneaza
0)
• Socket-ul e socket de ascultare si nr. de conexiuni
complete este nenul (se poate utiliza accept() )
• A aparut o eroare la socket (read() returneaza –1, cu
errno setat) – erorile pot filtratate via getsockopt() cu
optiunea SO_ERROR
Multiplexarea I/O|select()
Un descriptor de socket este gata de scriere daca:
– Exista un numar de octeti disponibili in buffer-ul de
scriere (write() va returna > 0)
– Conexiunea in sensul scrierii este inchisa
(incercarea de write() va duce la generarea
SIGPIPE)
– A aparut o eroare de scriere (write() returneaza –1,
cu errno setat) – erorile pot fitratate via
getsockopt() cu optiunea SO_ERROR
Multiplexarea I/O|select()
• Un descriptor de socket este gata de exceptie
daca:
– Exista date out-of-band sau socket-ul este
marcat ca out-of-band (curs viitor optional)
–Daca capatul remote a socket-ului TCP a fost
inchis in timp ce date erau pe canal;
urmatoarea operatie de read/write va
intoarce ECONNRESET
Multiplexarea I/O|select()
select() poate returna
– Numarul descriptorilor pregatiti pentru o operatiune de
citire, scriere sau exceptie
– Valoarea 0 – timpul s-a scurs, nici un descriptor nu este gata
– Valoarea –1 in caz de eroare
Utilizarea lui select() – pasii generali:
– Declararea unei variabile de tip fd_set
– Initializarea multimii cu FD_ZERO()
– Adaugarea cu FD_SET() a fiecarui descriptor dorit a fi
monitorizat
– Apelarea primitivei select()
– La intoarcerea cu succes, verificarea cu FD_ISSET() a
descriptorilor pregatiti pentru I/O
Demo
Exemplu de utilizare a
primitivei select()
Socket-uri BSD|utilizare
• Serviciile Internet (serviciile folosesc socket-urile
pentru comunicarea intre host-uri remote)
– Exemplu de aplicatii distribuite
• World Wide Web
• Accesul remote la o baza de date
• Distribuirea de task-uri mai multor hosturi
• Jocuri on-line
• …
Socket-uri BSD|critici
API-ul bazat pe socket-uri BSD are o serie de limitari:
– Are o complexitate ridicata, deoarece a fost proiectata sa
suporte familii de protocoale multiple (dar rar folosite in
practica)
– Nu este portabila (unele apeluri/tipuri au alte
denumiri/reprezentari pe alte platforme; numele fisierelor -
antet.h depind de sistem)
– Exemplu: la WinSock descriptorii de socket sunt pointeri,
in contrast cu implementarile Unix care folosesc intregi
');
INSERT INTO `cursuri` VALUES (7,'Cursul 7
Programarea in retea (III)
Lenuta Alboaie
adria@info.uaic.ro
https://profs.info.uaic.ro/~computernetworkscursullaboratorul.php
Cuprins
• Primitive I/O - discutii
• Server concurent UDP
• TCP sau UDP – aspecte
• Instrumente
• Alternative de proiectare si
implementare al modelului
client/server TCP
Primitive I/O
• Citire de date
– read() / recv() / readv() / recvfrom()/ recvmsg()
• Trimitere de date
– write() / send() / writev() / sendto()/ sendmsg()
Alte primitive| I/O
#include <sys/uio.h>
ssize_t readv (int filedes, const struct iovec *iov, int iovcnt);
ssize_t writev (int filedes, const struct iovec *iov, int iovcnt);
struct iovec
{
void *iov_base; /* adresa de start a bufferului */
size_t iov_len; /* dimensiunea bufferului */
};
Mai generale decit read()/write(), ofera posibilitatea de a
transmite date aflate in zone necontigue de memorie
Cele 2 apeluri returneaza la execuție normala lungimea
transferului in octeti
Alte primitive| I/O
#include <sys/socket.h>
ssize_t recvmsg (int sockfd, struct msghdr *msg, int flags);
ssize_t sendmsg (int sockfd, struct msghdr *msg, int flags);
Ambele functii au majoritatea optiunilor incorporate in
structura msghrd
Cele mai generale functii I/O; apelurile
read/readv/recv/recvfrom pot fi inlocuite de recvmsg
Cele 2 apeluri returnează la execuție normală lungimea
transferului în octeți; -1 in caz de eroare
Alte primitive| I/O
Comparatie intre primitivele I/O:
Server UDP | situatii
Majoritatea serverelor UDP sunt iterative
– Server UDP care citeste cererea clientului,
proceseaza cererea, trimite raspunsul si termina
cu acel client
– Daca este nevoie de schimb de datagrame
multiple cu clientul?
Server UDP concurent
- daca elaborarea raspunsului ia mult timp serverul
poate crea (fork()) un proces copil care va rezolva
cererea
Server UDP | situatii
Server UDP concurent
• Server UDP care schimba datagrame multiple cu un client
– Problema: Doar un numar de port este cunoscut de client
ca fiind un port “wellknown”
– Solutia: serverul creaza un socket nou pentru fiecare
client, si il ataseaza la un port “efemer”, si utilizeaza acest
socket pentru toate raspunsurile.
• Obligatoriu clientul trebuie sa preia din primul raspuns
al serverului noul numar de port si sa faca urmatoarele
cereri la acel port
– Exemplu: TFTP - Trivial File Transfer Protocol
Server concurent UDP
– TFTP utilizeaza UDP si portul 69
TCP sau UDP – discutii
Aspecte privind utilizarea UDP:
- UDP suporta broadcasting si multicasting
- UDP nu are nevoie de un mecanism de stabilire a conexiunii
- Minimul de timp necesar unei tranzactii UDP cerere-raspuns
este: RRT(Round Trip Time) + SPT (server processing time)
Aspecte privind utilizarea TCP:
- TCP suporta point-to-point
- TCP este orientat conexiune
- Ofera siguranta si asigura transmiterea in ordine a datelor;
- Ofera mecanisme de control al fluxului si control al congestiei
- Minimul de timp necesar unei tranzactii TCP cerere-raspuns
daca se creaza o noua conexiune este: 2 *RRT + SPT
TCP sau UDP – discutii
Folosirea UDP , respectiv TCP – recomandari
• UDP trebuie folosit pentru aplicatii multicast sau
broadcast
Controlul erorilor trebuie (eventual) adaugat la nivelul
serverului sau clientului
• UDP poate fi folosit pentru operatii de cerere-raspuns
simple; erorile trebuie tratate la nivelul aplicatiei
Exemple: streaming media, teleconferinte, DNS
TCP sau UDP – discutii
Folosirea UDP , respectiv TCP – recomandari
• TCP trebuie folosit pentru bulk data transfer (e.g.
transfer de fisiere)
– S-ar putea folosi UDP? Reinventam TCP la nivelul
aplicatiei!
Exemple: HTTP (Web), FTP (File Transfer Protocol),
Telnet, SMTP
Instrumente
• Multe sisteme UNIX ofera facilitatea de “system call
tracing ”
Instrumente
• Programe de test de dimensiuni reduse
• Instrumente:
– tcpdump – majoritatea versiunilor de Unix
• Ofera informatii asupra pachetelor din retea
• http://www.tcpdump.org/
– snoop – Solaris 2.x
– lsof
• Identifica ce procese au un socket deschis la o adresa IP sau port specificat
– netstat
Instrumente
• Instrumente:
– tcptrack
Alternative de proiectare si implementare al modelului client/server TCP
Fire de executie| Necesitate
• fork() poate fi un mecanism costisitor
– implementarile curente folosesc mecanismul copyon-write
• IPC (Inter-Process Comunication) necesita trimiterea
informatiei intre parinte si copil dupa fork()
Fire de executie| Caracteristici
• Firele de executie (threads) sunt numite si
lightweight processes (LWP)
• Pot fi vazute ca un program aflat in executie fara
spatiu de adresa proprie
Procese, Fire de executie| Comparatii
• Exemplu: Costurile asociate crearii si managementului
proceselor (50.000) este mai mare decat in cazul firelor
de executie(50.000)
Platform
fork() pthread_create()
user sys user sys
AMD 2.4 GHz Opteron (8cpus/node) 2.2 15.7 0.3 1.3
IBM 1.9 GHz POWER5 p5-575
(8cpus/node) 30.7 27.6 0.6 1.1
IBM 1.5 GHz POWER4 (8cpus/node)
48.6 47.2 1.0 1.5
INTEL 2.4 GHz Xeon (2 cpus/node)
1.5 20.8 0.7 0.9
INTEL 1.4 GHz Itanium2 (4 cpus/node) 1.1 22.2 1.2 0.6
Fire de executie| Implementare
• Pthreads (POSIX Threads) standard ce
defineste un API pentru crearea si manipularea
firelor de executie
– FreeBSD
– NetBSD
– GNU/Linux
– Mac OS X
– Solaris
• Pthread API pentru Windows – pthreads-w32
Fire de executie| Primitive de baza
#include <pthread.h>
int pthread_create(
pthread_t *tid,
const pthread_attr_t *attr,
void *(*func) (void *),
void *arg);
Returneaza: 0 in caz de succes
o valoare Exxx pozitiva in caz de eroare
pthread_t (-> adeseori un unsigned int)
(Identificatorul thread-ului)
pthread_t (-> adeseori un unsigned int)
(Identificatorul thread-ului)
Structura ce specifica atributele noului fir
creat (e.g. dimensiunea stivei, prioritatea,
NULL = comportamentul implicit )
Structura ce specifica atributele noului fir
creat (e.g. dimensiunea stivei, prioritatea,
NULL = comportamentul implicit )
Referinta la functia ce va fi executata
de thread
Referinta la functia ce va fi executata
de thread
Argumentul catre thread ce este
transmis functiei
Argumentul catre thread ce este
transmis functiei
Fire de executie| Primitive de baza
#include <pthread.h>
int pthread_join(
pthread_t *tid,
void **status );
- Realizeaza asteptarea terminarii unui anumit thread
Returneaza: 0 in caz de succes
o valoare Exxx pozitiva in caz de eroare
24Identificatorul Identificatorul thread-ului
… va stoca valoarea de return a threadului (un pointer la un obiect)
… va stoca valoarea de return a threadului (un pointer la un obiect)
Fire de executie| Primitive de baza
#include <pthread.h>
pthread_t pthread_self();
Returneaza: ID-ul thread-ului care a apelat primitiva
Identificatorul Identificatorul thread-ului
Fire de executie| Primitive de baza
#include <pthread.h>
int pthread_detach(pthread_t tid);
Thread-urile pot fi:
– joinable: cind thread-ul se termina, ID-ul si codul de iesire sunt pastrate
pina cand se apeleaza pthread_join() <– comportament implicit
– detached: cand thread-ul se termina toate resursele sunt eliberate
Returneaza: 0 in caz de succes
o valoare Exxx pozitiva in caz de eroare
Exemplu: pthread_detach(pthread_self());
Identificatorul Identificatorul thread-ului
Fire de executie| Primitive de baza
#include <pthread.h>
void pthread_exit(void*status);
- Terminarea unui thread
Thread-urile se pot termina:
– Functia executata de thread returneaza (Obs. Valoarea de
return este void * si va reprezenta codul de iesire a threadului )
– Daca functia main a procesului returneaza sau oricare din
thread-uri a apelat exit(), procesul se termina
Fire de executie|Exemplu
Exemplu de server TCP concurent care nu foloseste fork()
pentru a deservi clientii, ci foloseste thread-uri
Obs. Compilarea: gcc –lpthread server.c sau
gcc server.c –lpthread
Alternative de proiectare al modelului
client/server TCP
• Client TCP - modelul uzual
– Aspecte:
• Atat timp cat este blocat asteptind date de la
utilizator, nu sesizeaza evenimentele de retea
(e.g. peer close())
• Functioneaza in modul “stop and wait”
• “batch processing”
Alternative de proiectare al modelului
client/server TCP
• Client TCP – utilizind select()
– Clientul este notificat de evenimentele din retea in timp ce
asteapta date de intrare de la utilizator
Aspecte:
• Apelul write() poate fi blocant daca buffer-ul de la socket-ul
emitator este plin
Daca peer-ul trimite date, read() returneaza o
valoare >0;
Daca peer-ul TCP trimite FIN, socket-ul devine
“citibil” si read() intoarce 0;
Daca peer-ul trimite RST (peer-ul a cazut sau a
rebootat), socket-ul devine “citibil” si read()
intoarce -1;
RST date FIN
error EOF
date sau
EOF
stdin
socket
client
select()
Alternative de proiectare al modelului
client/server TCP
• Client TCP – utilizind select() si operatii I/O
neblocante
– Aspecte:
• Implementare complexa => cand sunt necesare
operatii I/O neblocante se recomanda utilizare
de procese (fork()) sau de thread-uri (vezi slideurile urmatoare)
Alternative de proiectare al modelului
client/server TCP
• Client TCP – utilizind fork()
– Mecanismul de functionare:
• exista doua procese
– Un proces face managementul datelor client-server
– Un proces face managementul datelor server-client
Parintele si copilul
partajeaza acelasi socket
Parintele si copilul
partajeaza acelasi socket
Alternative de proiectare al modelului
client/server TCP
• Client TCP – utilizind pthread()
– Mecanismul de functionare:
• exista doua fire de executie
– Un fir de executie face managementul datelor clientserver
– Un fir de executie face managementul datelor
server-client
server
copyto
thread
main
thread
pthread_create
stdin
stdout
client
Alternative de proiectare al modelului
client/server TCP
• Comparatie a timpilor de executie a clientilor TCP cu
arhitecturile client discutate
• Obs. Masuratoarea s-a realizat folosindu-se comanda time
pentru implementari client/server echo
Tip client TCP Timp executie
(secunde)
Modelul uzual (stop-and-wait) …
Modelul folosind select si I/O blocante 12.3
Modelul folosind select si I/O neblocante 6.9
Modelul folosind fork() 8.7
Modelul folosind thread-uri 8.5
[Unix Network Programming, R. Stevens B.
Fenner, A. Rudoff - 2003
Alternative de proiectare al modelului
client/server TCP
• Server TCP – iterativ
– Se realizeaza procesarea completa a cererii
clientului inainte de a deservi urmatorul client
Aspecte:
– Sunt destul de rar intilnite in implementarile reale
– Un astfel de server serveste foarte rapid un client
Alternative de proiectare al modelului
client/server TCP
• Server TCP – cate un proces copil pentru fiecare client
• Serverul deserveste clintii in mod simultan
• Este des intilnit in practica
– Exemplu de mecanism folosit pentru distribuirea
cererilor: DNS round robin
Aspecte:
– Crearea fiecarui copil (fork()) pentru fiecare client
consuma mult timp de CPU
Alternative de proiectare al modelului
client/server TCP
• Server TCP – preforking; fara protectie pe accept()
– Serverul creaza un numar de procese copil cand este pornit, si apoi
acestia sunt gata sa serveasca clientii
Aspecte
• Daca numarul de clienti este mai mare decat numarul de procese copil
disponibile, clientul va resimti o “degradare” a raspunsului in raport cu
factorul timp
• Acest timp de implementare merge pe sisteme ce au accept() primitiva de
sistem
Alternative de proiectare al modelului
client/server TCP
• Server TCP – preforking; cu blocare pentru protectia accept()
Implementare:
– Serverul creaza un numar de procese copil cand este pornit, si
apoi acestia sunt gata sa serveasca clientii
– Se foloseste un mecansim de blocare (e.g. fcntl()) a apelului
primitivei accept(), si doar un singur proces la un moment dat
va putea apela accept(); procesele ramase vor fi blocate pina
vor putea obtine accesul
• Exemplu: Apache (http://www.apache.org) foloseste tehnica de
preforking
Alternative de proiectare al modelului
client/server TCP
• Server TCP – preforking; cu “transmiterea” socket-ului conectat
Implementare:
• Serverul creaza un numar de procese copil cand este pornit, si
apoi acestia sunt gata sa serveasca
clientii
Aspecte:
Procesul parinte trebuie sa aiba evidenta actiunilor proceselor
fii => o complexitate mai mare a implementarii
• Procesul parinte este cel care
apeleaza accept() si “transmite”
socket-ul conectat la un copil
soketpair()
Alternative de proiectare al modelului
client/server TCP
• Server TCP – cate un thread pentru fiecare client
Implementare:
Thread-ul principal este blocat la apelul lui accept() si de fiecare
data cind este acceptat un client se creaza (pthread_create())
un thread care il va servi
Aspecte:
Aceasta implementare este in general mai rapida decat cea mai
rapida versiune de server TCP preforked
DEMO (Slide 28)
Alternative de proiectare al modelului
client/server TCP
• Server TCP – prethreaded; cu blocare pentru protectia accept()
Implementare:
– Serverul creaza un numar de thread-uri cand este pornit, si
apoi acestea sunt gata sa serveasca clientii
– Se foloseste un mecansim de blocare (e.g. mutex lock) a
apelului primitivei accept(), si doar un singur thread la un
moment dat va apela accept();
Obs. Thread-urile nu vor fi blocate in apelul accept()
Alternative de proiectare al modelului
client/server TCP
• Server TCP – prethreaded; cu “transmiterea” socket-ului conectat
Implementare:
Serverul creaza un numar de thread-uri cand este pornit, si apoi
acestia sunt gata sa serveasca clientii
Procesul parinte este cel care apeleaza accept() si “transmite”
socket-ul conectat la un thread disponibil
Obs. Deoarece thread-urile si descriptorii sunt in cadrul aceluiasi
proces ,“transmiterea” socket-ului conectat inseamna de fapt ca
thread-ul vizat sa stie numarul descriptorului
Alternative de proiectare al modelului
client/server TCP| Discutii
• Daca serverul nu este foarte solicitat, varianta traditionala de server
concurent ( un fork() per client) este utilizabila
• Crearea unei multimi de procese copil (eng. pool of children) sau
multimi de thread-uri (eng. pool of threads) este mai eficienta din
punct de vedere al factorului timp; trebuie avut grija la monitorizarea
numarului de procese libere, la cresterea sau descresterea acestui
numar a.i. clientii sa fie serviti in mod dinamic
• Mecanismul prin care procesele copil sau thread-urile pot apela
accept() este mai simplu si mai rapid decit cel in care thread-ul
principal apeleaza accept() si apoi “transmite” descriptorul proceselor
copil sau thread-urilor.
• Aplicatiile ce folosesc thread-uri sunt in general mai rapide decat daca
utilizeaza procese, dar alegerea depinde de ce ofera SO sau de specificul problemei
');
INSERT INTO `cursuri` VALUES (8,'Cursul 8
Sistemul numelor de domenii
https://profs.info.uaic.ro/~computernetworkscursullaboratorul.php
Lenuta Alboaie (adria@info.uaic.ro)
Andrei Panu (andrei.panu@info.uaic.ro)
Cuprins
• Domain Name System (DNS)
• Caracterizare
•Organizare
• Configurare
• Comenzi, Primitive
•IDN
DNS
• Adresele IP (de ex. 85.122.23.145,
2001:0db8:0001:0000:0000:0ab9:C0A8:0102)
sunt dificil de memorat
• Se utilizeaza un sistem al numelor de domenii
pentru a translata adresele IP in nume de
domenii si invers
• Numele de domenii se organizeaza in ierarhii
• RFC 1034, 1035, 1123, 2181 3
DNS| organizare
• Initial: /etc/hosts – perechi (nume, IP)
– Probleme de scalabilitate
• Actual: DNS consta dintr-o schema ierarhica de
nume de domenii si dintr-un sistem de baze de
date distribuite ce implementeaza aceasta
schema de nume
DNS| Tipuri de domenii
• Primare (Top Level Domains – TLD)
– pentru Infrastructura Internet – un singur domeniu .arpa ARPA
(Address and Routing Parameter Area)
• “Changes to the .arpa zone must be coordinated manually with IANA”
– State (ccTLD) – coduri de state: .ro, .fr, .jp, …
– IDN ccTLD (Internationalized Country Code Top-Level Domains)
– Generice: .biz, .com, .info, .name, .net, .org, .pro
– Sponsorizate: .aero, .edu, .gov, .int, .jobs, .mil, .tel
– Rezervate: .example, .invalid, .localhost, .test
– Pseudo-domenii: .bitnet, .local, .root, .uucp etc.
https://www.iana.org/domains/root/db/ 6
http://例子.测试 http://example.test
• Domeniu de nume
– Subarbore al arborelui de domenii
– Nu trebuie sa respecte topologia retelei fizice
• Sub-domenii:
– intreaga cale de nume nu depaseste 255 de
caractere
• Nume de calculatoare (gazde)
DNS| organizare
• Reguli de alocare a numelor de domenii:
– Fiecare domeniu controleaza cum sunt alocate
subdomeniile sale
– Pentru a crea un nou subdomeniu, se cere
permisiunea domeniului in care va fi inclus (un
domeniu de la un anumit nivel va avea o autoritate)
– Atribuirea de nume de domenii respecta granitele
organizationale, nu pe cele ale retelelor
– Un anumit nivel din ierarhia de niveluri poate fi
controlat de mai multe servere
• Servere de nume (name servers)
– Teoretic, un singur server de nume poate contine
intreaga baza de date DNS si poate raspunde
tuturor cererilor
• Probleme: incarcarea si “single point of failure”
– Spatiul de nume DNS se divide in zone nesuprapuse
• Servere de nume (name servers)
Exemplu: O posibila impartire a spatiului de
nume DNS in zone
• Servere de nume (name servers)
– Exista un server primar (primary/authoritative
name server) care deserveste un anumit domeniu
si, eventual, mai multe servere secundare
continand baze de date replicate
– TCP se utilizeaza pentru replicarea DNS
– UDP pentru interogari (lookups)
• Client DNS
– Denumit resolver, trimite un pachet UDP serverului
DNS, care cauta numele si returneaza adresa IP
• Exemplu de implementari ale serverului de
nume: BIND (Berkeley Internet Name Domain),
MSDNS, PowerDNS etc.
• Ca resolver (client) interactiv, se poate folosi de
exemplu una dintre comenzile: nslookup, host
sau dig.
DNS| interogari
• Interogari:
– Recursiva – daca un server DNS nu cunoaste adresa
pentru numele solicitat, atunci va interoga alt
server DNS
– Incrementala – daca serverul DNS nu stie sa
raspunda, returneaza eroare si adresa altui server
DNS (numit si referral) care ar putea cunoaste
raspunsul la interogare
DNS| interogari
• Fiecarui domeniu ii este asociata o multime de
inregistrari de resurse (resource record – RR)
• Mecanismul:
– Cererea: resolver-ul trimite un nume de domeniu
– Raspunsul: inregistrarile de resurse asociate acelui
nume (stocate in bazele de date DNS)
DNS realizeaza corespondenta dintre numele de
domenii si inregistrarile de resurse
• Forma generala RR este:
Nume_domeniu Timp_de_viata Tip Clasa Valoare
Nume_domeniu (domain name) – precizeaza
domeniul caruia i se aplica aceasta inregistrare
Timp_de_viata (time-to-live) – da o indicatie despre
cat de stabila este inregistrarea
Tip - precizeaza tipul inregistrarii
– SOA (Start Of Authority) : domeniul curent, adresa e-mail a
administratorului, etc.
– A – adresa IP a gazdei
– MX (mail exchangers) – precizeaza numele domeniului
pregatit sa accepte posta electronica pentru domeniul
specificat
– CNAME (Canonical Name) – permite crearea pseudonimelor
– PTR (Pointer) – Pseudonim pentru adresa IP
– HINFO- permit aflarea tipului de masina si de sistem de
operare carora le corespunde domeniul
– TXT: text neinterpretat (comentarii) 19
Clasa: pentru Internet valoarea acestuia este IN
Valoare: acest camp poate fi un numar, un nume de
domeniu sau un sir ASCII; semantica depinde de
tipul de inregistrare
DNS| configurare
• Exemplu de fisier /etc/resolv.conf
DNS| interogari inverse
• Problema:
– Data o adresa, care va fi numele ei simbolic?
(reverse DNS resolution sau reverse DNS lookup)
Exemple:
1)
2) 2001:db8::567:89ab
b.a.9.8.7.6.5.0.0.0.0.0.0.0.0.0.0.0.0.0.0.0.0.0.8.b.d.0.1.0.0.2.ip6.arpa
DNS| optimizari
Proximitatea spatiala: serverele locale vor fi
interogate mai des decat cele la distanta
Proximitatea temporala: daca un set de domenii sunt
referentiate repetat atunci se apeleaza la caching
DNS
Fiecare intrare DNS va avea stabilita o valoare TTL
(time to live)
Se va utiliza si replicarea (servere multiple, servere
root multiple) – se va interoga cel mai apropiat
(geografic) server
DNS| comenzi
Ca resolver interactiv se pot folosi comenzile:
– nslookup
– dig
– host
–whois
–…
DNS| nslookup
nslookup www.info.uaic.ro
- Returneaza RR de tip A folosind serverul DNS local
Exemple de utilizari:
nslookup 85.122.23.1
- Returneaza RR de tip PTR pentru 85.122.23.1 in ierarhia de domenii in-addr.arpa
Host Lookup
Reverse IP
Lookup
[http://www.zytrax.com/books/dns/ch3/]
DNS| nslookup
nslookup www.axiologic.ro
- Returneaza RR de tip A folosind serverul DNS specificat
Exemple de utilizari:
man nslookup
Host Lookup
DNS| dig
dig – un instrument mai puternic decat nslookup
Exemplu de utilizare:
dig www.info.uaic.ro A
DNS| comenzi
host
30
Exemplu de utilizare:
DNS| whois
whois ibm.com
DNS| primitive
• Nu trebuie scris un resolver pentru a afla adresa IP a
unei gazde
• Functii principale:
• gethostbyname(); getaddrinfo();
• gethostbyaddr() ; getnameinfo();
• La unele sisteme de operare (e.g., Solaris) va trebui la
compilare sa folosim biblioteca nsl (Name Server
Library): gcc … -lnsl
DNS| primitive
Una din structurile folosite: hostent
struct hostent {
char *h_name; /* nume oficial (canonical) */
char **h_aliases; /* alias-uri */
int h_addrtype; /* AF_INET */
int h_length; /* lungimea adresei: 4 sau 6 */
char **h_addr_list; /*pointeri la adresele IP */
};
DNS| primitive
Structura hostent:
h_name
h_aliases
h_addrtype
h_length
h_addr_list
Numele oficial al hostului
(canonical name)
…
NULL
…
NULL
alias 1
alias 2
Adresa IP 1
Adresa IP 2
AF_INET
DNS| gethostbyname()
#include <netdb.h>
struct hostent *gethostbyname
(const char *hostname);
• In termenii DNS, gethostbyname() realizeaza o
cerere pentru o inregistrare A
• Obs. gethostbyname() se foloseste in special
pentru IPv4
DNS| gethostbyname()
• Returneaza:
– In caz de succes returneaza un pointer la hostent, ce
contine adresa IP a host-ului
– In caz de eroare NULL, iar variabila h_errno indica
eroarea aparuta:
• HOST_NOT_FOUND
• …
• NO_RECOVERY
• …
Constante definite in netdb.h
DNS| gethostbyname()
• Exemplu de utilizare: completarea structurii sockaddr_in avand in
loc de adresa IP un nume simbolic:
struct sockaddr_in server;
struct hostent *hos;
if(!( hos = gethostbyname(“fenrir.info.uaic.ro”) )
{/*Eroare la rezolvarea adresei*/}
server.sin_family=AF_INET
/* adresa IP o luam din structura hos */
memcpy(&server.sin_addr.s_addr, hos->h_addr_list[0],
sizeof(hos->h_addr_list));
server.sin_port=htons(4321);
DNS| gethostbyaddr()
#include <netdb.h>
struct hostent *gethostbyaddr (
const char *addr,
socklen_t len,
int family);
• In termenii DNS, gethostbyaddr() realizeaza o cerere la serverul
de nume pentru o inregistrare PTR in domeniul in-addr.arpa
• Returneaza: In caz de succes returneaza un pointer la hostent, ce
contine numele oficial al host-ului ; In caz de eroare NULL, iar
variabila h_errno indica eroarea aparuta
Obs. gethostbyaddr() se foloseste in special pentru IPv4
DNS| getservbyname()
#include <netdb.h>
struct servent *getservbyname (const char *servname, const char
*protoname);
• Returneaza: un pointer la struct servent in caz de sucess, NULL in
caz de eroare
struct servent {
char *s_name; /* numele oficial al serviciului*/
char **s_aliases; /* alias-uri */
int s-port; /* portul (network-byte order) */
char *s_proto; /* protocolul */ };
Exemplu: struct servent *pserv;
pserv=getservbyname(“ftp”,”tcp”); /*FTP folosind TCP */39
DNS| getservbyport()
#include <netdb.h>
struct servent *getservbyport (int port, const char *protoname);
• Cauta un serviciu dupa un numar de port si dupa protocol
(optional)
• Returneaza: un pointer la struct servent in caz de sucess, NULL in
caz de eroare
Obs. port este in network byte order
Exemplu:
struct servent *pserv;
pserv=getservbyport( htons(53), ”udp”); /*DNS folosind UDP */
pserv=getservbyport( htons(21),”tcp”); /*FTP folosind TCP */ 40
DNS| getaddrinfo()
#include <netdb.h>
int getaddrinfo (
const char *hostname,
const char *service,
const struct addrinfo *hints,
struct addrinfo **result ) ;
• Obs. hostname, service, hints – parametri de intrare
• Returneaza: 0 in caz de sucess, !=0 in caz de eroare
• Se recomanda a fi folosita si pentru IPv4 si pentru IPv6
• Combina functionalitati ale: gethostbyname(), getservbyname(),
getservbyport()
Numele host-lui sau o adresa IPv4 sau
IPv6 ca string
Portul serviciului sau numele serviciului
(“http”,”pop”,..) (vezi /etc/services )
Contine informatii despre tipul
de informatii pe care trebuie sa
le intoarca primitiva
DNS| getaddrinfo()
struct addrinfo {
int ai_flags; /* AI_PASSIVE, AI_CANONNAME */
int ai_family; /* AF_INET, AF_INET6, AF_UNSPEC */
int ai_socktype; /* SOCK_STREAM sau SOCK_DGRAM */
int ai_protocol; /* 0 (auto) sau IPPROTO_TCP, IPPROTO_UDP */
socklen_t ai_addrlen; /* lungimea lui ai_addr */
char *ai_canonname; /* numele canonic al host-ului */
struct sockaddr *ai_addr; /* adresa binara a socket-ului */
struct addrinfo *ai_next; /* pointer la urmatoarea structura din
lista */
};
DNS| getaddrinfo()
Discutii:
• Daca functia returneaza cu succes result va pointa la lista de struct
addrinfo.
Cazuri cind se pot obtine structuri multiple:
– Exista mai multe adrese asociate cu numele hostului si cate o
structura este returnata pentru fiecare adresa
– Daca serviciul este furnizat pentru tipuri diferite de socket-uri,
atunci cate o structura este returnata pentru fiecare tip de socket
• Informatia returnata de getaddrinfo() in structura struct addrinfo
**result poate fi utilizata astfel:
– Pentru socket() : ai_family, ai_socktype, ai_protocol
– Pentru connect() sau bind(): ai_addr si ai_addrlen
• freeaddrinfo()
DNS| getnameinfo()
#include <netdb.h>
int getnameinfo (
const struct sockaddr *sockaddr,
socklen_t addrlen,
char *host,
socklen_t hostlen,
char *serv,
socklen_t servlen,
int flags) ;
• Inlocuieste gethostbyaddr() si getservbyport()
• Returneaza: 0 in caz de sucess, !=0 in caz de eroare
numele host-ului intors
Numele serviciului
Adresa socket-ului trimisa ca
argument
NI_NOFQDN -> host va contine doar
numele host-ului si nu intreg numele
al domeniului
DNS| IDN
• International Domain Names (IDN)
– Extensie care permite folosirea caracterelor Unicode
in numele de domenii, nu doar a celor ASCII
https://www.icann.org/en/topics/idn/
16 Noiembrie 2009 - Inregistrarea de domenii ccIDN
sau IDN ccTLD
– Pot fi exploatate pentru atacuri de tip phishing
(… detalii intr-un curs viitor)
DNS| administrare
• Radacina DNS este oficial administrata
de Internet Corporation for Assigned
Names and Numbers (ICANN)
• Exista si alte organizatii care ofera
radacini alternative (alt DNS roots),
precum OpenNIC (Network Information
Center) sau New.Net
');
INSERT INTO `cursuri` VALUES (9,'Curs 9
Nivelul Aplicatie
https://profs.info.uaic.ro/~computernetworkscursullaboratorul.php
Lenuta Alboaie (adria@info.uaic.ro)
Andrei Panu (andrei.panu@info.uaic.ro)
Cuprins
• Protocoale la nivelul aplicatie
– Preliminarii
– Caracteristici de proiectare
– Accesul la terminal de la distanta
– Posta Electronica
• SMTP (Simple Mail Transfer Protocol)
• POP (Post Office Protocol)
– Transferul de fisiere
• TFTP (Trivial File Transfer Protocol)
• FTP (File Transfer Protocol)
– World-Wide Web (HTTP)
– Privire de ansamblu
Preliminarii
• La nivelul aplicatie sunt puse la dispozitie o serie de servicii :
– Terminal la distanta (TELNET, SSH, …)
– Posta electronica (SMTP, IMAP, POP, …)
– Transferul de fisiere (TFTP, FTP si altele)
– World-Wide Web (HTTP)
– Conversatii instantanee (ICQ, XMPP (din Mai 2014 -> nu mai
are suport in Google Voice), Hangouts IM, WhatsApp… )
• Se ofera si protocoale pentru rezolvarea unor sarcini de
sistem - /etc/services, /etc/protocols
– Sistemul de fisiere in retea (NFS)
– Conectivitatea cu alte sisteme de fisiere (SMB)
– Servicii de baze de date (MySQL, PostgreSQL, …, Hive, …)
Caracteristici de proiectare
• Tipuri de protocoale in functie de natura datelor transferate
– Fluxuri de caractere generate de utilizator
• Folosite pentru aplicatii interactive la distanta (telnet,
rlogin, IRC, …)
• Traficul este in mare masura compus din date
neinterpretate
• Se pot include secvente de control (i.e. controlul
terminalului, coduri de culoare) – coduri ANSI
(Exemplu: CSI n E -> numit: CNL – Cursor Next Line
Moves cursor to beginning of the n-th (default 1) following
line)
• Tipuri de protocoale in functie de natura datelor transferate
– Mesaje intrebare/raspuns ASCII
• Serverul si clientul vehiculeaza siruri de caractere care pot fi
citite si de utilizatori umani (SMTP, FTP, HTTP/1.1, XMPP, SIP, …)
• Uzual, sunt compuse din linii de text
– Formate binare
• Utilizate pentru protocoale de nivel inferior (SNMP – Simple
Network Management Protocol) sau de nivel inalt (NFS peste
RPC, HTTP/2.0)
• Apar probleme la reprezentarea datelor (de ex. ordinea octetilor)
– Protocoale ad-hoc folosite de aplicatiile (nestandard) scrise de
utilizatori
• Pot adopta unele dintre tipurile anterioare
• Cerinte referitoare la proiectarea unui protocol
– Parametri critici: lungimea numelui comenzilor,
marimea buffer-elor, modul de adresare
– Definirea operatiilor permise (e.g., creare, citire,
scriere, stergere, actualizare)
– Raportarea erorilor: coduri de eroare, mesaje
– Formatul mesajelor: sursa, destinatie, parametri,
codificarea datelor, lungime fixa/variabila, …
• Scenariul uzual
– Serverul – citeste coduri de operatii (opcode-uri) si
raporteaza starea folosind coduri de eroare
– Clientul – construieste mesaje folosind opcodeurile permise
• Problema fiabilitatii (engl. Reliability) comunicarii
– Reteaua poate pierde mesaje
– Abordari:
• Posta clasica (post-office)
– Nu asteapta nici un fel de confirmari
• Handshaking – toate mesajele sunt confirmate
• Raspuns confirmat (acknowledged reply)
– Se asteapta un raspuns, iar expeditorul raspunsului
asteapta confirmarea primirii lui
• Cerere/raspuns (request/reply) – expeditorul asteapta
(un timp) venirea raspunsului (e.g. RPC, SOAP)
Accesul la terminal
• Serviciu “antic” standard Internet
• Folosit prin comenzi precum rlogin, telnet, ssh (varianta
securizata a telnet)
• Utilizeaza modelul client/server:
– Clientul interactioneaza cu utilizatorul
– Serverul furnizeaza acces la un shell (e.g., bash)
Aplicatie de tip
remote login
Figura: Mecanismul de functionare a unei aplicatii de tip
remote login [Retele de calculatoare –
curs 2007-2008, Sabin Buraga]
• Implementare – mecanism general
Pentru conectarea la distanta, fiecare client va fi deservit de un proces copil al
serverului
Procesul copil va crea un alt proces care va conecta clientul la un pseudoterminal si va executa shell-ul
[Retele de calculatoare –
curs 2007-2008, Sabin Buraga] 13
Accesul la terminal
• Probleme
– Initializarea si autentificarea
• Cum identificam clientul?
• Cum stim ca serverul este unul oficial?
– Procesarea caracterelor speciale (inclusiv sfarsitul de linie –
EOL)
– Cine proceseaza actiuni precum editarea liniei, afisarea
caracterelor tastate (echoing), suspendarea terminalului
(CTRL + S), etc.?
– Modul de comunicare intre client si server
• Intreruperi din partea utilizatorului
• Controlul dimensiunii ferestrei de afisare
• rlogin
– protocol simplu de acces la distanta
– utilizat exclusiv pentru conectarea de masini UNIX
– RFC 1258: “The rlogin facility provides a remote-echoed,
locally flow-controlled virtual terminal with proper flushing
of output”
Functionare:
– rlogin comunica cu un daemon rlogind de pe gazda remote
– autentificarea se face prin apelarea la gazde “de incredere”
(“trusted” hosts)
• rlogind permite logarea fara parola daca gazda remote
apare in fisierul /etc/hosts.equiv sau daca utilizatorul are
un fisier .rlogin in directorul home
• telnet (terminal network)
– Protocol standard TCP/IP de acces la distanta (RFC 854,855)
– Utilizat indiferent de platforma
– Poate fi utilizat drept client generic fara a sti detalii despre server
– Autentificarea clientilor nu se face de catre protocol, ci de catre
aplicatie
– Protocolul se bazeaza pe:
• Conceptul NVT (Network Virtual Terminal): un dispozitiv
virtual cu o structura generala comuna cu o gama larga de
terminale; fiecare host face maparea caracteristicilor
propriului terminal cu cele ale NVT
• Odata ce a fost stabilita o conexiune prin TELNET, ambele
capete ale comunicarii sunt tratate simetric
• telnet (terminal network)
– Protocolul se bazeaza pe:
• Ambele parti ale comunicarii pot sa negocieze utilizarea de
optiuni aditionale care sa reflecte partea hardware utilizata
– Optiuni pentru : editarea liniei, dimensiunea ferestrei de
afisare etc.
A B
“Will X”
“Do X”
A B
“Will X”
“Don’t X”
telnet ofera compatibilitate cu
terminale
vechi (vt52, vt100,…)
[ TCP/IP Tutorial and Technical
Overview, IBM, 2006 ] 17
Accesul la terminal
• telnet (terminal network)
– Comunicare dintre client si server se realizeaza prin comenzi de
tipul:
• IP (Interrupt Process; 244) -> terminarea programului care
ruleaza
• AO (Abort output; 245) -> elibereaza orice buffer de iesire
• AYT (Are you there; 246) -> permite clientului trimiterea unei
interogari OOB pentru verificarea faptului ca partea remote
este activa
• EC (Erase character; 247) -> stergerea caracterului anterior
• EL (Erase Line; 248) -> stergerea intregii linii curente
• … (RFC 854)
– Trimiterea unei comenzi: comanda (1 octet) precedata de un
octet cu valoarea 255 - IAC (Interpret As Command)
SSH
• SSH (secure shell)
– Fata de telnet, furnizeaza o comunicare sigura (bazata pe
TCP) prin mesaje criptate si mesaje de autentificare
– SSH foloseste modelul client/server
• Un program client SSH este utilizat pentru stabilirea unei
conexiuni cu un daemon SSH
– Utilizari:
• logarea pe o masina la distanta si executarea de comenzi
• suport pentru tunneling (curs viitor)
• permite si transfer de fisiere in asociere cu protocoalele
SFTP sau SCP
– Are suport in majoritatea sistemelor de operare moderne
E-mail (Electronic Mail)
• Protocoale bazate pe TCP:
– SMTP (Simple Mail Transfer Protocol)
• RFC 821 (specifica modul de schimb a mail-ului intre
doua host-uri)
– POP (Post Office Protocol)
• RFC 1939
– POP3S – varianta securizata a POP3
• A se vedea si: RFC 822 (specificatii privind antetul unui
mail), 2049 (specificatii privind documente diferite de plain
text ASCII ce pot fi continute intr-un email), RFC 974
(standard privind rutarea mailurilor folosind DNS)
• RFC 822 si 974 -> consolidate in RFC 2821, 2822
E-mail
• Terminologie
– Agent utilizator (MUA – Mail User Agent): client (local) pentru posta
electronica
Ex: alpine, mutt, Mozilla Thunderbird, Kmail, Outlook etc.
– Agent de transfer (MTA – Mail Transport Agent)
responsabil cu comunicarea cu gazdele la distanta si cu
trimiterea/receptionarea de posta
(client & server) - sendmail, qmail
– Agent de distributie (MDA - Mail Distribution Agent sau LDA – Local
Delivery Agent) - directioneaza mesajele primite catre casuta postala a
utilizatorului; Ex: maildrop, Sieve, procmail
– Mail exchanger (MX) – gazda responsabila cu e-mail-urile unui domeniu
(masina intermediara)
E-mail
• Caracteristici
– Distinctia dintre plic si continut
• Plicul incapsuleaza mesajul, contine date necesare
pentru transportul mesajului: destinatar, adresa,
prioritate, securitate, …
• Plicul este folosit pentru dirijarea mesajului la destinatar
• Mesajul din plic contine un antet (date de control
pentru MUA) si un corp (date pentru utilizator)
– Fiecare utilizator este identificat printr-o adresa de e-mail:
cutie_postala@locatie (cont@adresaInternet)
E-mail|SMTP
• Componente:
– Plic (envelope)– folosit de MTA pentru livrare
Exemplu:
MAIL From: <adria@info.uaic.ro>
RCPT to: <adria@info.uaic.ro>
– Anteturi (headers) – folositi de MUA
Exemplu: Received, Message-ID, From, Date, Reply-To,
Subject,…
– Continut –ul mesajului (body) -
• Mecanism: MUA preia continutul, adauga anteturi si il
transmite la MTA; MTA adauga anteturi, adauga plicul si il
trimite la un alt MTA
E-mail|SMTP
• Comunicarea:
– Se realizeaza o conexiune TCP intre Sender SMTP si Receiver
SMTP (intre MTA-uri). Obs. Receiver SMTP poate fi
destinatia finala sau un intermediar (mail gateway)
– Clientul trimite comenzi SMTP, iar serverul raspunde cu
coduri de stare
– Mesajele de stare includ coduri numerice NNN si texte
explicative
– Ordinea comenzilor este importanta
– Se utilizeaza portul 25
• Comenzi uzuale:
– HELO: identifica gazda expeditoare
– MAIL FROM: porneste o tranzactie si identifica orginea email-ului
– RCPT TO: identifica recipientii individuali ai mesajului
(adrese de e-mail); pot exista comenzi RCPT TO: multiple
– DATA desemneaza o serie de linii text terminate cu \r\n,
ultima linie continind doar “.”
– QUIT
• Alte comenzi:
– VRFY: permite verificarea validitatii unui recipient
– NOOP: forteaza serverul sa raspunda cu un cod de OK (200)
– EXPN: expandeaza un grup de adrese (alias)
– TURN: interschimba destinatarul cu expeditorul fara a fi
necesara crearea unei noi conexiuni TCP
(sendmail nu suporta aceasta comanda)
– RSET abandoneaza tranzactia curenta
E-mail|SMTP
• RFC 822: SMTP este limitat la text ASCII pe 7 biti
• RFC 1521: defineste un standard care sa rezolve limitarile
anterioare -> MIME (Multipurpose Internet Mail Extensions)
– Standard de codificare a continutului mesajelor non-ASCII
• Limbi cu accente, cu alfabete non-latine, fara alfabet,
mesaje non-textuale
– Permite atasarea la e-mail a fisierelor de orice tip
– Se foloseste campul:
Content-Type: tip/subtip
Exemplu: Mime-Version: 1.0
Content-Type: TEXT/PLAIN
• Tipuri MIME principale:
application defineste aplicatiile client
(application/executable)
text defineste formatele text
(text/plain, text/html)
image specifica formatele grafice
(image/gif, image/jpeg)
audio specifica formatele audio (audio/basic)
video specifica formatele video (video/mpeg)
multipart utilizat pentru transportul datelor compuse
(multipart/mixed, multipart/alternative)
• POP (Post Office Protocol) – RFC 1939
• Utilizat la transferul de mesaje de pe un server de
posta la un MUA – portul 110
• Comenzile si raspunsurile sunt mesaje ASCII
• Raspunsurile incep cu +OK sau -ERR
[Retele de calculatoare –
curs 2007-2008, Sabin Buraga]
• Comenzi uzuale:
– USER specifica numele de cont
– PASS specifica parola
– STAT furnizeaza numarul de mesaje din cutia postala
(mailbox)
– LIST afiseaza lista de mesaje si lungimea, cate 1 pe linie
– RETR preia un mesaj
– DELE reseteaza tranzactia, iar orice marcaj de stergere este
eliminat
– QUIT sterge mesajele marcate si inchide conexiunea
• POP 3 - caracteristici:
– In general, daca utilizatorul schimba clientul el nu-si mai poate reciti
mailurile; Obs: Clienti cu optiunea: ‘keep a copy of the email on the
server’
– Foloseste mecanismul “download-and-keep”: copierea mesajelor pe
clienti diferiti
– POP3 este fara stare intre sesiuni
• Alte solutii:
IMAP (Interactive Mail Access Protocol) – RFC 1730
– Pastreaza toate mesajele intr-un singur loc: pe server
– Permite utilizatorului sa organizeze mesajele in directoare
– Pastreaza starea “utilizatorului” intre sesiuni
• Numele directoarelor si maparea dintre ID-urile mesajelor si
numele folderului
• TFTP (Trivial File Transfer Protocol) -> …Cursul 6 & RFC 1350
– utilizeaza UDP si portul 69
– utilizat deseori la initializarea statiilor de lucru fara disc sau a
altor dispozitive
– nu are mecanisme de autentificare si criptare => este utilizat in
retele locale
– RFC 1785, 2347, 2348, 2349
Transferul de fisiere|TFTP
• TFTP (Trivial File Transfer Protocol)
Implementarile TFTP utilizeaza comenzi de tipul:
– RFC 1785, 2347, 2348, 2349
[ TCP/IP Tutorial and Technical
Overview, IBM, 2006 ]
FTP – caracterizare
• Folosit atat interactiv, cat si de programe
• Asigura transferul sigur si eficient al fisierelor
• Se bazeaza pe modelul client/server
• FTP utilizeaza doua conexiuni TCP pentru transferul fisierelor:
– Conexiune de control
• folosita pentru trimiterea comenzilor si receptionarea codurilor de
stare
• Conexiunea de control utilizeaza portul 21
– Conexiunea de date
• folosita pentru transferul efectiv
• conexiunea de date foloseste portul 20
sau unul aleator (P > 1023)
• nu este obligatorie intr-o sesiune FTP 41
Transferul de fisiere|FTP
FTP – caracterizare
• Comenzile si raspunsurile sunt linii de text
• Obs. (FTP->)file transfer != file access (->NFS)
• Vezi si RFC 956, 1068, 2228, (FTP Security Extensions), 2428 (FTP Extensions
for IPv6 and NATs)
• Pentru interactivitate se foloseste protocolul TELNET
Tipuri de acces:
• Anonim (FTP anonymous) – RFC 1635
– Autentificare cu numele anonymous si drept parola o adresa de
e-mail
– Acces public la o serie de resurse (aplicatii, date, multimedia
etc.)
• Autentificat
– Necesita un nume de utilizator existent, insotit de o parola
valida
– Pentru transferul de date in/din contul personal 42
FTP – comenzi (protocol)
• Comenzi de control al accesului
– USER username, PASS password, QUIT, ChangeWorkingDir,…
• Comenzi de transfer a parametrilor
– PORT, TYPE, MODE
• Comenzi de realizarea a serviciilor FTP
– RETR filename, ABOR, STOR filename, LIST, PrintWorkingDir
Raspunsul de stare
Linie de text continind:
XYZ un cod de stare (utilizat de software) + un mesaj
explicativ (destinat oamenilor)
FTP – codul de stare (xyz)
Prima cifra semnifica:
1 replica pozitiva preliminara (“am indeplinit, dar
asteapta”)
2 replica pozitiva finala (“succes”)
3 replica pozitiva intermediara (“am nevoie si de alte
informatii”)
4 replica negativa tranzitorie (“eroare, incerc iar”)
5 replica negativa finala (“eroare fatala”)
Transferul de fisiere|FTP
FTP – codul de stare (xyz)
A doua cifra specifica grupuri de functii:
0 erori de sintaxa
1 informare (ajutor, informatii de stare)
2 referitor la conexiuni
3 privitor la autentificarea utilizatorului
4 nespecificat
5 referitor la sistemul de fisiere
FTP – codul de stare (xyz)
A treia cifra da informatii suplimentare asupra mesajelor de
eroare
Exemple:
125 Conexiune deschisa; transfer pornit
200 Comanda OK
226 Transfer complet
331 Nume utilizator OK, se cere parola
452 Eroare la scrierea fisierului
500 Eroare de sintaxa (comanda necunoscuta)
501 Eroare sintaxa (argumente invalide)
221 Goodbye /*rezultat al comenzii QUIT */
49
FTP – Moduri de transfer
- STREAM
- Fisierul este trimis ca un flux de octeti; sfirsitul transmisiei
este indicat de inchiderea normala a conexiunii;
- BLOCK
- Fisierul este transmis ca o serie de blocuri de date
precedate de antete continand contoare si descriptori de
bloc (e.g. End of data block)
- COMPRESSED
- Fisierele sunt compresate, conform unui algoritm de
compresare (e.g., gzip) si sunt trimise ca date binare
Active FTP – exemplu
- Clientul se conecteaza la un
server (85.122.23.145:21) de
la un port P > 1023
- Clientul trimite comanda
PORT 85.122.23.1.4.2
(4*256+2=1026) ce indica
Server-ului sa initieze o
conexiune cu clientul la portul
P+1
- Clientul asculta la P+1 si
primeste datele trimise de
server prin portul 20
Obs. Conexiunea initiata de server poata fi interpretata ca un potential atac de
firewall-ul clientului
Pasive FTP – exemplu
- La initierea unei conexiuni FTP
clientul foloseste doua porturi
(P>1023 si P+1)
- Clientul se conecteaza la un
server (85.122.23.145:21) de
la portul P si trimite comanda
PASV
- Serverul deschide un port PS >
1023 si trimite comanda
PORT PS clientului
- Clientul va initia o conexiune
(de la portul P+1) cu serverul
folosind portul primit (PS)
HTTP
• Hyper Text Transfer Protocol
– Protocol utilizat in Internet, bazat pe stiva TCP/IP
– Sta la baza comunicarii dintre serverele si clientii Web
• Client: in mod uzual poate fi un browser
• Server: server Web care trimite raspunsuri la cererile primite
– HTTP 1.0 - RFC 1945
– HTTP 1.1 - RFC 2616
– HTTP 1.1 revised - RFC 723X (https://www.w3.org/Protocols/)
Protocolul HTTPS – asigura comunicatii “sigure” HTTP via TLS (Transport
Layer Security):
– autentificare pe baza certificatelor digitale + criptare bidirectionala
– RFC 2818 – https://tools.ietf.org/html/rfc2818
– Protocolul SPDY – un experiment Google, disponibil ca
Internet Draft la care Google a renuntat in 2016
• Reducerea latentei incarcarii si cresterea securitatii
• https://www.chromium.org/spdy
• Implementari SPDY existau in : Chrome, Mozilla
Firefox, Opera, Amazon Silk, Internet Explorer
– Protocolul HTTP/2.0
• RFC 7540
• Extinde ideile SPDY, focalizat asupra performantei
• www.slideshare.net/mnot/what-http20-will-do-for-you
• Hyper Text Transfer Protocol
Mecanism general:
Clientul initiaza o conexiune TCP cu serverul
folosind portul 80
Serverul accepta conexiunea TCP
Are loc schimbul de mesaje HTTP intre
clientul HTTP (browser) si server-ul Web
Se inchide conexiunea TCP
• HTTP – nu se ocupa de partea de rutare sau verificarea cererilor
– ? Cine: TCP&IP
– HTTP lucreaza cu cereri la nivel inalt: Fetch IndexPage al https://www.google.com
– Live HTTP Headers (Firefox) ->
Detalii asupra portului: https://www.grc.com/port_8080.htm 56
Web Browser| Download
• Modul cum browserul reda un website este esential in procesul de optimizare
Exemplu: download resursa http://kernel.org
Web Browser| Download
• Pasii realizati de browser:
– Rezolvarea kernel.org folosind DNS pentru aflarea IP (primul segment)
– Al doilea segment indica incercarea de a crea o conexiune HTTP catre
kernel.org
– La inceputul celui de-al treilea segment, conexiunea TCP a fost creata si
browserul isi poate primi raspunsul; in cazul nostru poate datorita latentei
serverului, abia la la inceputul celui de-al patrulea segment serverul web
trimite continutul
– Total: 847 milisecunde (ms) – si documentul HTML a fost obtinut
• Obs. In general paginile web constau din legaturi catre foi de stiluri, imagini,
JavaScript etc.
– Imediat ce documentul HTML incepe sa vina, browserul incepe operatia de
fetch pe alta resursa (kernel.css in cazul nostru)
• Obs. De data aceasta nu mai sunt intarzieri datorate DNS lookup,
deoarece raspunsul anterior a fost plasat in cache-ul browserului
– Sunt intarzieri datorate initierii conexunii TCP catre server
• ? De ce exista o asa mare intarziere pentru cererea us.png?
– “Motiv istoric”: in exemplul nostru browserul downlodeaza
doar doua resurse in paralel de la acelasi host (cum s-a
terminat kernel.css, incepe us.png)
– Pentru resursele us.png si cele care urmeaza nu mai exista nici
un segment de conexiune TCP browserul reutilizeaza
conexiunea TCP existenta cu serverul => o optimizare (salveaza
0.1 secunde per cerere)
– Obs. Pentru resursele 1,5,12 timpul pentru descarcarea
resursei e jumatate din intregul timp de fetching a resursei; la
restul timpul de descarcare este insignifiant
Conexiuni persistente si Keep-Alive
– In HTTP 1.0 – comportamentul implicit era ca dupa fiecare obtinere de
resursa sa se inchida conexiunea
Efect => latenta in primirea raspunsului, utilizarea resurselor (CPU, RAM) la
nivel de client si server
Conexiuni persistente si Keep-Alive
• Problema a fost partial rezolvata prin introducerea lui Keep-Alive
– Clientul include in antetul cererii campul: Content: Keep-Alive
– Daca serverul suporta acest aspect, trimite inapoi un header cu aceeasi
valoare
• => conexiunea ramine deschisa pana cand una din parti decide
inchiderea ei
– ? Dar daca un client nu inchide conexiunea?
• Serverul este idle si consuma memorie
– Majoritatea serverelor web implementeaza un Keep-Alive timeout
– De asemenea serverele pot limita numarul de resurse care se cer
per o conexiune
Keep-Alive: timeout = 5, max 100
• Obs. Keep-Alive nu a fost oficial recunoscuta si nu era suportata de toti
clientii
Conexiuni persistente si Keep-Alive
• HTTP/1.1 a formalizat Keep-Alive => conexiuni persistente in mod implicit
• Daca un client|server nu doreste atunci poate utiliza un camp in antet:
Connection: close
• ? Cand comportamentul implicit al lui Keep-Alive nu este de dorit?
Download Paralel
• RFC 2616: “Clients that use persistent connections should limit the number of
simultaneous connections that they maintain to a given server. A single-user
client should not maintain more than 2 connections with any server or proxy….
These guidelines are intended to improve HTTP response times and avoid
congestion.”
• Scopul furnizorilor de clienti browser: cresterea gradului de interactiune cu
utilizatorul
– E problema serverelor web
HTTP
• Hyper Text Transfer Protocol
Conexiunile HTTP sunt persistente
Inchiderea si deschiderea a mai putine conexiuni TCP=> timp de
CPU este salvat in rutere si host-uri (clienti, servere, proxy, ...) si
se economiseste memoria folosita
Clientii pot face cereri multiple in cadrul aceleiasi conexiuni, fara
a astepta raspunsul pentru fiecare
Congestia in retea este redusa datorita numarului de pachete
mai mic
Cererile se desfasoara mai rapid deoarce nu mai este nevoie de
un handshake la fiecare cerere
');
INSERT INTO `cursuri` VALUES (10,'Curs 10
Paradigma P2P
Lenuta Alboaie (adria@info.uaic.ro)
Andrei Panu (andrei.panu@info.uaic.ro)
https://profs.info.uaic.ro/
~computernetworkscursullaboratorul.php
Cuprins
• Paradigma peer-to-peer (P2P)
– Preliminarii
–Definitii
– Caracterizare
– Tipuri de aplicatii
– Infrastructuri
– Instrumente
Definitii
Peer = one that is of equal standing with another
(conform Webster)
Peer-to-peer (P2P) = arhitectura de retea in care
nodurile sunt relativ egale
– In sensul ca fiecare nod este, in principiu, capabil sa
realizeze functii specifice retelei
Definitii
Sistemele P2P, in sens strict,
sunt sisteme complet distribuite
– Toate nodurile sunt total echivalente, in termeni de
functionalitate si a activitatilor pe care le pot desfasura
Obs.: Sistemele P2P pure sunt rare (de ex. Gnutella); majoritatea
sunt hibride, avand supernoduri sau servere cu diferite roluri
(de ex. cautare de date, control etc.)
Definitii
• “P2P este clasa de aplicatii care se bazeaza pe resursele (de
stocare, de procesare, continut, prezente umane) disponibile la
marginile (edges) Internet-ului
Edges of the Internet
(overlay networks)
“P2P is a class of applications that take advantage of resources –
storage, cycles, content, human presence – available at the
edges of the Internet. Because accessing these decentralized
resources means operating in an environment of unstable and
unpredictable IP addresses, P2P nodes must operate outside
the DNS system and have significant or total autonomy from
central servers”
“A distributed network architecture may be called a P2P network
if the participants share a part of their own resources. These
shared resources are necessary to provide the service offered
by the network. The participants of such a network are both
resource providers and resource consumers”
Caracterizare
Caracteristici definitorii:
– Partajarea resurselor computationale prin
interschimb direct si mai putin prin intermedieri
oferite de o autoritate centralizata (server)
• Serverele centralizate pot fi folosite insa pentru a
realiza activitati specifice (initializarea retelei P2P,
adaugarea de noi noduri in retea,…)
• Ideal, nodurile participa activ si unilateral la
realizarea de operatii ca localizarea & caching-ul
nodurilor/continutului, dirijarea informatiilor,
managementul resurselor transferate etc.
Caracteristici definitorii:
– Abilitatea de a trata instabilitatea si variatiile
conctivitatii retelei, adaptandu-se automat la
erorile survenite sau la dinamicitatea nodurilor
• Topologia retelei P2P e adaptiva si toleranta la
defecte, nodurile auto-organizandu-se in
vederea mentinerii conectivitatii si
performantei retelei
Reteaua P2P este una suprapusa (overlay) peste cea
fizica
– Se situeaza la nivelul aplicatie => flexibilitate
– Muchiile virtuale sunt conexiuni TCP sau pointeri la
adrese IP
– Mentinerea retelei P2P se face prin verificarea
periodica a conectivitatii (ping) ori a existentei
(mesaje “still alive?”)
– Cand un nod pica, sistemul P2P ar putea stabili noi
muchii
– Proximitatea (fizica) a nodurilor nu e importanta
– Reteaua P2P poate fi structurata sau nu
Scopuri si beneficii
• Utilizarea eficienta a resurselor
– Latimea de banda neutilizata, resurse de stocare, putere de procesare
disponibile la marginile (edges) retelei
• Scalabilitate
– Fara informatii centralizate, fara bottleneck-uri (de comunicare si de
calcul)
– Agregarea resurselor se face in mod natural odata cu utilizarea sistemului
• Siguranta (eng. reliability)
– Existenta de copii a datelor
– Distribuire geografica
– Nu mai exista “single point of failure”
• Administrare usoara
– Nodurile se auto-organizeaza
– Cresterea tolerantei la erori si a echilibrarii incarcarii
– Cresterea autonomiei
• Anonimitatea
– Greu de realizat intr-un sistem centralizat
• Dinamism
– Mediu dinamic
– Colaborare si comunicare ad-hoc 13
Dezavantaje/Probleme
– Arhitecturile P2P sunt probabilistice
• Localizare impredictibila a resurselor
• Resursele sunt volatile
– Inexistenta unui control centralizat
• Probleme privind impunerea unei autoritati asupra
aplicatiilor, continutului si utilizatorilor
• Dificultati in detectarea si identificarea utilizatorilor (aspecte
anti-sociale)
– Incurajarea folosirii sistemelor P2P in scop abuziv si ilegal (de ex.
drepturile de autor asupra continutului digital)
– Lipsa increderii la nivel comercial, de afaceri
– Probleme de securitate (curs viitor)
Tipuri de aplicatii
• Comunicare & colaborare
– Sisteme ce ofera o infrastructura pentru facilitarea comunicarii &
colaborarii directe, deseori in timp real, intre noduri
• Sisteme conversationale (chat, mesagerie instantanee):
IRC (Internet Relay Chat), ICQ (1996), YM!, MSN Messenger,
Skype, Sisteme multicast P2P (e.g. Cirrus – Adobe Flash
http://labs.adobe.com/technologies/cirrus/; WebRTC ), …
• Calcul distribuit
– Sisteme ce folosesc puterea computationala a nodurilor disponibile
(cicli de procesor)
• Rezolvarea unor probleme prin divide-et-impera: SETI@home
(Search for Extra-Terrestrial Intelligence-Berkeley),
genome@home
• Reteaua P2P reprezinta un gen de Grid computational (…curs
master) 16
Tipuri de aplicatii
• Sisteme de stocare (baze de date)
– Proiectare de sisteme de baze de date distribuite bazate pe infrastructuri
P2P
• PIER – motor scalabil de interogare distribuita
(http://pier.cs.berkeley.edu/)
• Edutella – proiect open-source pentru interogari si stocare de metadate (P2P pentru Semantic Web)
• Distribuire de continut digital
– Sisteme & infrastructuri pentru partajarea resurselor digitale (multimedia
si alte date) intre utilizatori
• Aplicatii pentru partajarea fisierelor (e.g. Napster, Gnutella, KaZaA,
Freenet, BitTorrent, eDonkey etc.)
• Medii de stocare distribuita pentru publicarea, organizarea,
indexarea, cautarea si regasirea datelor in maniera securizata &
eficienta
(PAST, Chord, Groove, Mnemosyne, Avalanche,…)
Tipuri de aplicatii
• Distribuire de continut prin P2P
– Sisteme P2P de “interschimb de fisiere”
• Nodurile transfera un fisier la un moment dat
• Se ofera facilitati pentru realizarea unei retele
P2P si pentru cautarea&transferul de fisiere
intre noduri
• Nu se ofera suport pentru securitate,
disponibilitate si persistenta
• Exemple: Napster, KaZaA, Gnutella
Tipuri de aplicatii
• Distribuire de continut prin P2P
– Sisteme P2P pentru publicarea & stocarea
continutului
• Utilizatorii pot publica, stoca si distribui
continut digital, pe baza unor drepturi de acces
(privilegii)
• Se focalizeaza asupra securitatii si persistentei
• Unele ofera si facilitati privind colaborarea intre
utilizatori
• Exemple: Scan, Groove, Freenet, MojoNation,
Tangler
Tipuri de aplicatii
• Distribuire de continut prin P2P
– Infrastructuri pentru:
• Dirijare & Localizare:
Chord, Can, Pastry, Tapestry, Kademila
• Anonimitate:
Onion Routing, ZeroKnowledge, Freedom,
Tarzan
• Managementul reputatiei:
Eigentrust, PeerTrust
Infrastruc.(localizare & dirijare)
• Mecanismele de localizare si dirijare ce pot fi
adoptate depind de:
– Topologia
– Structura
– Gradul de centralizare
ale retelei suprapuse, acoperitoare (overlay
network)
Infrastruc.(localizare & dirijare)
• Aspecte privind centralizarea
– Arhitecturi pur descentralizate: toate nodurile
realizeaza exact aceleasi activitati, jucand simultan
roluri de servere si clienti, fara a beneficia de o
coordonare centrala
• Nodurile se numesc servents (SERVers +
clieENTS)
Infrastruc.(localizare & dirijare)
• Aspecte privind centralizarea
– Arhitecturi partial centralizate: unele noduri au un rol mai
important (de ex. stocand indecsi locali pentru fisierele
partajate)
• Nodurile devin supernoduri conform politicilor fiecarui
sistem P2P
• Rolul de supernod este stabilit dinamic
– Arhitecturi descentralizate hibride: exista un server
central facilitand interactiunea intre noduri, mentinand
cataloage de meta-date ale fisierelor
• Serverele pot identifica si verifica nodurile de stocare
• Sistemele se mai numesc broker mediated
Infrastruc.(localizare & dirijare)
• Aspecte privind structura retelei:
– Nestructurata: plasarea continutului este complet
independenta de topologia retelei suprapuse
• Continutul trebuie localizat
• Strategii de cautare prin “forta bruta”: inundarea
retelei – cereri propagate via BFS/DFS
• Strategii mai sofisticate: drumuri aleatorii,
probabilistice etc.
– Slab structurata (loosely structured): desi localizarea
continutului nu e complet specificata, aceasta este
afectata de dirijare
• Categorie aflata intre retele structurate si cele
nestructurat
Infrastruc.(localizare & dirijare)
• Aspecte privind structura retelei:
– Structurata: topologia este controlata, iar fisierele (sau
pointerii la ele) sunt plasate in locatii precise
• Se realizeaza o asociere (mapping) intre continut
(identificatorul de fisier) si locatie (adresa nodului)
– In genul unei tabele de rutare distribuita
• Cautarile exacte (exact-match queries) pot fi realizate in
mod scalabil
• Structura folosita la dirijarea eficienta a mesajelor este
dificil de mentinut in cazul unor noduri tranziente, cu
rata mare de atasare si deconectare de la retea
Arhitecturi nestructurate
Descentralizate hibride
- Fiecare calculator client
stocheaza continut (fisiere)
partajat(e)
- Serverul central mentine o tabela
cu conexiunile utilizatorilor
inregistrati (IP, latime de
banda,…) + o tabela cu lista
fisierelor fiecarui utilizator
&meta-date
- Exemple: Napster, Publius
Napster
• 1999: Sean Fanning lanseaza Napster
• A atins cota de 1.5 milioane de utilizatori simultan
• Baza de date centralizata - operatii:
– Join: clientul contacteaza serverul central (via TCP)
– Publish: raportarea unei liste de fisiere serverului
central
– Search: interogarea serverului => se intoarce
cineva care stocheaza fisierul cerut
– Fetch: ia fisierul direct de la peer (cel cu cea mai
buna rata de transfer)
• Iulie 2001: Napster a fost inchis
Arhitecturi nestructurate
Napster: Publish Napster: Search
Discutii:
- Serverul face toate procesarile
- Avem “single point of failure”
- Probleme de scalabilitate, unele sisteme nu permit adaugarea altor servere
(lista serverelor disponibile este statica)
Arhitecturi nestructurate
Descentralizate pure
- Se construieste o retea acoperitoare (overlay) cu propriile mecanisme
de rutare prin IP
- Nu exista o coordonare centrala
- Utilizatorii se conecteaza via o aplicatie care are rol dublu – servent
- Comunicarea intre serventi se bazeaza pe un protocol la nivel de
aplicatie, cu 4 tipuri de mesaje:
- Ping – cere ca un nod sa se anunte
- Pong – replica la mesajul ping (IP, port, numarul & marimea
fisierelor)
- Query – cerere de cautare (sir de cautare + viteza minima de
transfer)
- Query hints – raspuns (IP, port, viteza, dim. fis., index fis.)
Arhitecturi nestructurate
Descentralizate pure
- Cautarea se realizeaza prin inundare (flooding)
- Daca nu ai fisierul dorit, intreaba pe n vecini
- Daca nici ei nu au fisierul, vor intreba pe vecinii lor in maxim
m hop-uri
- Pe calea de intoarcere se vor intoarce raspunsurile (nu
continutul fisierelor)
- Fiecare mesaj are un TTL atasat
- Exemplu: Gnutella
Gnutella
• 2000: L. Frankel si T. Pepper(Nullsoft) lanseaza Gnutella
• Apar clienti: Bearshare, Morpheus, LimeWire
• Query Flooding:
– Join: la intrare in sistem, clientul contacteaza cateva noduri
care devin “vecinii” sai
– Publish: nu este necesar
– Search: se intreaba vecinii, care isi intreaba vecinii lor, …
• Exista un TTL ce limiteaza propagarea
– Fetch: preia fisierul direct de la peer
Arhitecturi nestructurate
Gnutella
Aspecte:
• Timpul de cautare este… O(?)
• Nodurile pleaca adesea => reteaua instabila
Arhitecturi nestructurate
Arhitecturi nestructurate
Partial centralizate
- Folosesc conceptul de supernod: are activitati de servire a unei
sub-retele P2P (indexare, caching)
- Nodurile sunt alese automat ca fiind supernoduri daca au
suficienta latime de banda si putere computationala
- Toate cererile sunt trimise initial la supernoduri
- Avantaje: timpul descoperirii resurselor e mai redus +
eterogenitatea este exploatata
- Exemplu: KaZaA
KaZaA
• 2001: Se lanseaza KaZaA
• Apar clienti: Morpheus, giFT
• Se utilizeaza un mecanism de tip “smart” query flooding:
– Join: la intrare in sistem, clientul contacteaza un
“supernode” (poate deveni si el supernod la un moment
dat)
– Publish: trimite lista de fisiere supernodului
– Search: trimite interogarea supernodului, si supernodurile
se interogheaza intre ele
– Fetch: ia fisierul direct de la peer(s); poate prelua fisierul
simultan de la mai multe peer-uri
Arhitecturi nestructurate
KaZaA: Designul retelei
Arhitecturi nestructurate
KaZaA: Inserarea de Fisiere KaZaA: Cautarea de Fisiere
Discutii:
- Comportament similar cu Gnutella, dar mai eficient
- Nu este nici o garantie asupra timpului de cautare sau a
domeniului de cautare
Arhitecturi nestructurate
Arhitecturi nestructurate
Partial centralizate
- Software-ul KaZaA este proprietar
- Datele de control P2P sunt criptate
- Mesajele folosesc HTTP
- Un nod e fie un supernod, fie asignat unui supernod
- Un supernod are 100-150 noduri-copil
- O retea poate avea ~30000 supernoduri
- Fiecare supernod are conexiuni TCP cu 30-50 supernoduri
- Pentru fiecare fisier se mentin meta-date (nume, dimensiune,
content hash, descriptor de fisier)
- Content hash-ul este folosit pentru cautarea altei copii a unui
fisier partial transferat
- Varianta fara spyware si pop-up-uri: KaZaA-lite
Arhitecturi nestructurate
Skype
- Prima retea de telefonie p2p bazata
pe IP
- din Iunie 2014, Microsoft a anuntat
incompatibilitatea cu protocolul
anterior Skype
- foloseste Microsoft Notification
Protocol 24 (prima utilizare -> MSN
Messenger in 1999)
- arhitectura era similara cu KaZaA
http://www1.cs.columbia.edu/~salman/publications/skype1_4.pdf
Arhitecturi nestructurate
Skype
- Fiecare client mentinea un host
cache cu adresele IP si numerele de
port ale supernodurilor accesibile
- Orice client cu latime de banda (si
fara restrictii de firewall sau NAT)
putea deveni supernode
- din 2012, Microsoft a inceput
gazduirea supernodurilor in servere
din centrele sale de date
http://en.wikipedia.org/wiki/PRISM_%28surveillance_program%29
Arhitecturi nestructurate
Partial centralizate
- Daca un fisier este gasit pe mai multe noduri, transferul poate fi realizat in
paralel
- Copiile identice se identifica via content hash
- Diferite portiuni din fisier sunt transferate de pe noduri diferite
- Pentru transferurile intrerupte, se face o recuperare automata (automatic
recovery)
- Exemplu: BitTorrent
- In 2002, B. Cohen a lansat BitTorrent
- Si-a propus concentrarea pe problema legata de obtinerea eficienta a
resurselor (efficient fetching) si nu pe cautare (searching)
- Sustinatori inca de la aparitie
- Blizzard Entertainment folosea BitTorrent pentru distributia
versiunilor beta a noilor jocuri
Arhitecturi nestructurate
Partial centralizate
BitTorrent - arhitectura
Arhitecturi nestructurate
Partial centralizate
BitTorrent
- Se bazeaza pe mecanismul de swarming:
- Join: contacteaza un server centralizat (tracker) si obtine o lista
de peer-uri
- Publish: ruleaza un server tracker
- Search: de ex. foloseste Google pentru a gasi un tracker pentru
fisierul dorit
- Fetch: Preia bucati de fisiere de la peer-uri; incarca bucatile de
fisier pe care le ai
- Obs. Diferenta fata de Napster
- Downlod-ul de bucati (chunk) de fisiere
- Utilizarea strategiei “tit-for-tat”: daca A face download de la
alte noduri, atunci A trebuie sa permita si download-ul de la el
(free-rider problem)
Arhitecturi nestructurate
Probleme
- Noduri ale caror adrese IP sunt disponibile via NAT (cu restrictii)
- Nu pot fi servere TCP pentru reteaua P2P
- Solutie partiala: reverse call
- A vrea sa transfere de la B, iar B foloseste NAT
- A si B stabilesc conexiuni TCP cu serverul C (IP rutabil)
- A poate cere lui B, via C, sa realizeze o conexiune TCP de la B la A
- A poate trimite o cerere lui B, iar B ii ofera raspunsul
- Daca A si B utilizeaza NAT?
- Flash crowd: o crestere neasteptata de cereri pentru o anumita resursa
– Pentru continutul dorit nu exista suficiente copii incarcate
– Cat timp ia unui utilizator sa localizeze fisierul?
– Cate mesaje va primi un nod datorita cautarilor realizate de alte noduri?
– Se poate folosi un protocol de cautare generic, bazat pe TTL
Arhitecturi structurate
• Reprezinta solutia academica pentru P2P
• Scop:
– Cautare cu succes
– Timp de cautare in limite cunoscute
– Scalabilitate demonstrata
• Abordare: DHT (Distributed Hash Table)
– Se stocheaza perechi (key, value)
• Key – nume de fisiere
• Value – continut de fisier sau pointer la o locatie
– Fiecare peer stocheaza o multime de (key, value)
– Operatii: gaseste nodul responsabil cu un Key
• Mapare key – node
• Rutarea eficienta a cererilor de insert/lookup/delete asociate cu acest
nod
– Se permite o mare fluctuatie a nodurilor
Arhitecturi structurate
• Aspect de interes: localizarea continutului
• Idee: Responsabilitatea este distribuita mai multor noduri ale
retelei de acoperire, intr-un mod adaptiv
• Fiecarei resurse i se asociaza o cheie unica via o functie hash:
h(“Curs Retele”)->7929; Intervalul de valori ale functiei hash se
distribuie in reteaua P2P
• Fiecare nod trebuie sa “cunoasca” locatia macar a unei singure
copii a fiecarei resurse pentru care functia sa hash ia valori in
intervalul lui
• Nodurile pot mentine in cache-ul propriu o copie a fiecarei
resurse pe care trebuie sa o “cunoasca”
Arhitecturi structurate
• Aspect de interes: dirijarea
• Pentru fiecare resursa, un nod ce “cunoaste” resursa trebuie sa
fie accesat pe calea cea mai “scurta”
• Abordarile de sisteme P2P structurate difera prin strategia de
dirijare
• Nodurile din sistem formeaza o structura de date distribuita care
poate fi: inel, arbore, hypercub, skip list etc.
• Se ofera un API pentru tabelele distribuite de hash-uri (DHT –
Distributed Hash Table)
– Dand o cheie k, API-ul va returna adresa IP a nodului
responsabil pentru valoarea cheii k
Arhitecturi structurate
• Implementari
– Chord [MIT]
– Pastry [Microsoft Research UK, Rice University]
– Tapestry [UC Berkeley]
– Content Addressable Network (CAN) [UC Berkeley]
– SkipNet [Microsoft Research US, Univ. of
Washington]
– Kademlia [New York University]
– Viceroy [Israel, UC Berkeley]
– P-Grid [EPFL Switzerland]
Arhitecturi structurate
• Slab structurate
– Nodurile pot estima ce noduri stocheaza resursele cautate
• Se evita broadcasturile oarbe
• Se foloseste o propagare in lant (chain mode
propagation): fiecare nod ia decizii locale privitoare la
care va fi nodul urmator interogat
– Cautarea unui fisier presupune utilizarea unei chei si a unui
mecanism de timeout
– Exemplu: Freenet
');
INSERT INTO `cursuri` VALUES (11,'Curs 11
Paradigma RPC
Lenuta Alboaie (adria@info.uaic.ro)
Andrei Panu (andrei.panu@info.uaic.ro)
https://profs.info.uaic.ro/
~computernetworkscursullaboratorul.php
Cuprins
• Remote Procedure Call (RPC)
– Preliminarii
– Caracterizare
– XDR (External Data Representation)
– Functionare
– Implementari
–Utilizari
Preliminarii
• Proiectarea aplicatiilor distribuite
– Orientata pe protocol – socket-uri
• Se dezvolta protocolul, apoi aplicatiile care il
implementeaza efectiv
– Orientata pe functionalitate – RPC
• Se creeaza aplicatiile, dupa care se divid in
componente si se adauga protocolul de
comunicatie intre componente
RPC|Caracterizare
• Idee: In loc de accesarea serviciilor la distanta prin
trimiterea si primire de mesaje, clientul apeleaza o
procedura care va fi executata pe alta masina
• Efect: RPC “ascunde” existenta retelei de program
– Mecanismul de message-passing folosit in
comunicarea in retea este ascuns fata de
programator
– Programatorul nu trebuie sa mai deschida o
conexiune, sa citeasca sau sa scrie date, sa inchida
conexiunea etc.
• Este un instrument de programare mai simplu decat
interfata socket BSD
RPC|Caracterizare
• O aplicatie RPC va consta dintr-un client si un server,
serverul fiind localizat pe masina pe care se executa
procedura
• La realizarea unui apel la distanta, parametrii
procedurii sunt transferati prin retea catre aplicatia
care executa procedura; dupa terminarea executiei
procedurii rezultatele sunt transferate prin retea
aplicatiei client
• Clientul si serverul –> procese pe masini diferite
RPC|Caracterizare
• RPC realizeaza comunicarea dintre client si server prin socketuri TCP/IP (uzual, UDP), via doua interfete stub (ciot)
– Obs.: Pachetul RPC (client stub si server stub|skeleton)
ascunde toate detaliile legate de programarea in retea
• RPC implica urmatorii pasi:
1. Clientul invoca procedura remote
• Se apeleaza o procedura locala, numita client stub care
impacheteaza argumentele intr-un mesaj si il trimite
nivelului transport, de unde este transferat la masina
server remote
Marshalling (serializare) = mecanism ce include
codificarea argumentelor intr-un format standard si
impachetarea lor intr-un mesaj
RPC|Caracterizare
• RPC implica urmatorii pasi:
2. Server-ul:
• nivelul transport trimite mesajul catre server stub, care
despacheteaza parametrii si apeleaza functia dorita;
• dupa ce functia returneaza, server stub preia valorile
intoarse, le impacheteaza (marshalling) intr-un mesaj si
le trimite la client stub
• un-marshalling (deserializare) = decodificare
3. Client stub preia valorile primite si le returneaza aplicatiei
client
RPC|Caracterizare
• Interfetele ciot implementeaza
protocolul RPC
• Diferente fata de apeluri locale:
– Performanta poate fi afectata
de timpul de transmisie
– Tratarea erorilor este mai
complexa
– Locatia server-ului trebuie sa
fie cunoscuta (Identificarea si
accesarea procedurii la
distanta)
– Poate fi necesara
autentificarea utilizatorilor
[Retele de calculatoare –
curs 2007-2008, Sabin Buraga]
RPC|Caracterizare
• Procedurile ciot se pot genera automat, dupa care se
“leaga” de programele client si server
• Ciotul serverului asculta la un port si realizeaza
invocarea rutinelor printr-o interfata de apel de
proceduri locale
• Clientul si serverul vor comunica prin mesaje, printr-o
reprezentare independenta de retea si de sistemul de
operare:
External Data Representation (XDR)
RPC|Caracterizare
• External Data Representation (XDR)
XDR defineste numeroase tipuri de date si modul lor
de transmisie in mesajele RPC (RFC 1014)
– Tipuri uzuale:
• Preluate din C: int, unsigned int, float, double, void,…
• Suplimentare: string, fixed-length array, variable-length
array, …
– Functii de conversie (rpc/xdr.h)
• xdrmem_create() – asociaza unei zone de memorie un
flux de date RPC
• xdr_numetip() – realizeaza conversia datelor
RPC|Caracterizare
• External Data Representation (XDR)
Exemplu
RPC|Caracterizare
• External Data Representation (XDR)
– Poate fi vazut ca nivel suplimentar intre nivelul
transport si nivelul aplicatie
– Asigura conversia simetrica a datelor client si
server
[Retele de calculatoare –
curs 2007-2008, Sabin Buraga]
RPC|Caracterizare
External Data Representation (XDR)
• Activitatea de codificare/decodificare
• In prezent, poate fi inlocuit de reprezentari XMLRPC sau SOAP sau JSON-RPC (in contextul
serviciilor Web)
vezi cursul de Tehnologii Web!
RPC|Functionare
Context:
• Un serviciu de retea este identificat de portul la care exista un daemon
asteptand cereri
• Programele server RPC folosesc porturi efemere
De unde stie clientul unde sa trimita cererea?
Portmapper = serviciu de retea responsabil cu asocierea de servicii la diferite
porturi
=> Numerele de port pentru un anumit serviciu nu sunt fixe
• Este disponibil la portul 111 (well-known port)
RPC|Functionare
Mecanism
general
[Retele de calculatoare –
curs 2007-2008, Sabin Buraga]
RPC|Functionare
Mecanism general:
Pas 1: Se determina adresa la care serverul va oferi serviciul
– La initializare, serverul stabileste si inregistreaza via
portmapper portul la care va oferi serviciul (portul a)
Pas 2: Clientul consulta portmapper-ul de pe masina
serverului pentru a identifica portul la care trebuie sa
trimita cererea RPC
Pas 3: Clientul si serverul pot comunica pentru a realiza
executia procedurii la distanta
– Cererile si raspunsurile sunt (de)codificate prin XDR
RPC|Functionare
• Atunci cind un server
furnizeaza mai multe
servicii, este de obicei
folosita o rutina
dispatcher
• Dispatcher-ul
identifica cererile
specifice si apeleaza
procedura
corespunzatoare,
dupa care rezultatul
este trimis inapoi
clientului pentru a-si
[Retele de calculatoare – continua executia
curs 2007-2008, Sabin Buraga]
RPC|Functionare
• Transferurile de date RPC pot fi:
– Sincrone
– Asincrone
[Retele de calculatoare –
curs 2007-2008, Sabin Buraga]
RPC|Implementare
• Open Network Computing RPC (ONC RPC) - cea mai raspandita
implementare in mediile Unix (Sun Microsystems)
– RFC 1057
– Interfata RPC este structurata pe 3 niveluri:
• Superior: independent de sistem, hardware sau retea
– Exemplu: man rcmd -> routines for returning a stream to a
remote command ….
• Intermediar: face apel la functiile definite de biblioteca RPC:
– registerrpc() – inregistreaza o procedura spre a putea fi
executata la distanta
– callrpc() – apeleaza o procedura la distanta
– svc_run() – ruleaza un serviciu RPC
• Inferior: da posibilitatea de a controla in detaliu mecanismele RPC
(de ex. alegerea modului de transport al datelor etc.)
RPC|Implementare
• Open Network Computing RPC (ONC RPC)
– Procedurile la distanta se vor include intr-un program la distanta -
unitate software care se va executa pe o masina la distanta
– Fiecare program la distanta corespunde unui server: putand
contine proceduri la distanta + date globale; procedurile pot
partaja date comune;
– Fiecare program la distanta se identifica printr-un identificator unic
stocat pe 32 biti; Conform implementarii Sun RPC avem
urmatoarele valori ale identificatorilor:
• 0x00 00 00 00 – 0x1F FF FF FF – aplicatiile RPC ale sistemului
• 0x20 00 00 00 – 0x3F FF FF FF – programele utilizator
• 0x40 00 00 00 – 0x5F FF FF FF – identificatori temporari
• 0x60 00 00 00 – 0xFF FF FF FF – valori rezervate
– Fiecare procedura (din cadrul unui program) este identificata
printr-un index (1..n)
RPC|Implementare
• Open Network Computing RPC (ONC RPC)
Exemple:
• 10000 meta-serverul portmapper
• 10001 pentru rstatd care ofera informatii despre sistemul
remote; se pot utiliza procedurile rstat() sau perfmeter()
• 10002 pentru rusersd ce furnizeaza informatii despre
utilizatorii conectati pe masina la distanta
• 10003 serverul nfs – ce ofera acces la sistemul de fisiere in
retea NFS (Network File System)
RPC|Implementare
• Open Network Computing RPC (ONC RPC)
Fiecare program la distanta are asociat un numar de versiune
• Initial versiunea 1
• Urmatoarele versiuni se identifica in mod unic prin alte
numere de versiune
Se ofera posibilitatea de a schimba detaliile de
implementare sau extinderea capabilitatilor
aplicatiei fara a asigna un alt identificator unui program
Un program la distanta este un 3-uplu de forma:
<id_Program, versiune, index_procedura>
RPC|Implementare
• Open Network Computing RPC (ONC RPC)
Programare
de nivel
inalt:
Compilare: gcc prog.c – lrpcsvc –o prog
Executie: ./prog fenrir.infoiasi.ro
RPC|Implementare
• Open Network Computing RPC (ONC RPC)
Programare la nivel intermediar:
callrpc (char *host, /* numele serverului */
u_long prognum, /* numarul programului server */
u_long versnum, /* numarul de versiune a serv.*/
u_long procnum, /* numarul procedurii */
xdrproc_t inproc, /* fol. pentru codificare XDR*/,
char *in, /* adresa argumentelor procedurii*/,
xdrproc_t outproc, /* fol. pentru decodificare */,
char *out, /* adresa de plasare a rezultatelor*/
);
RPC|Implementare
• Open Network Computing RPC (ONC RPC)
Programare la nivel intermediar:
registerrpc(
u_long prognum /* numarul programului server */,
u_long versnum /* numarul de versiune a serv*/,
u_long procnum /* numarul procedurii */,
void *(*procname)*() /* numele functiei remote */,
xdrproc_t inproc /* fol. pt. decodificarea param. */,
xdrproc_t outproc /* fol. pt. codificarea result. */
);
RPC|Implementare
• Open Network Computing RPC (ONC RPC)
Programare la nivel intermediar:
svc_run ()
- Se asteapta venirea de cereri RPC, apoi se apeleaza folosinduse svc_getreq() procedura corespunzatoare
Obs.: Functiile de nivel intermediar utilizeaza doar UDP
Apelata de serverul RPC,
reprezinta dispatcher-ul
RPC|Implementare
• Open Network Computing RPC (ONC RPC)
Programare la nivel inferior:
[Retele de calculatoare –
curs 2007-2008, Sabin Buraga]
RPC|Implementare
• Open Network Computing RPC (ONC RPC)
Realizarea de aplicatii RPC cu rpcgen
• Se creeaza un fisier cu specificatii RPC (Q.x)
– Declaratii de constante utilizate de client si server
– Declaratii de tipuri de date globale
– Declaratii de programe la distanta, proceduri, tipuri
de parametri, tipul rezultatului, identificatorul unic
de program
• Programul server.c care contine procedurile
• Programul client.c care invoca procedurile
Pentru server: gcc server.c Q_svc.c Q_xdr.c –o server
Pentru client: gcc client.c Q_clnt.c Q_xdr.c –o client
RPC|Implementare
• Open Network Computing RPC (ONC RPC)
In implementarea unei aplicatii RPC se utilizeaza utilitarul rpcgen
[Retele de calculatoare –
curs 2007-2008, Sabin Buraga]
- Genereaza client
stub si server stub
- Generaza functiile
de codificare si
decodificare XDR
- Genereaza rutina
dispatcher
Client
Server
RPC|Implementare
• Alte implementari:
– DCE/RPC (Distributed Computing Environment/RPC)
• Alternativa la Sun ONC RPC
• Utilizat si de serverele Windows
– ORPC (Object RPC)
• Mesajele de cerere/raspuns la distanta se incapsuleaza in obiecte
• Descendenti directi:
• (D)COM (Distributed Component Object Model) & CORBA
(Common Object Request Broker Architecture)
• In Java: RMI (Remote Method Invocation)
• .Net Remoting , WCF
– SOAP (Simple Object Access Protocol)
• XML ca XDR, HTTP ca protocol de transfer
• Baza de implementare a unei categorii de servicii Web
RPC|Utilizari
• Accesul la fisiere la distanta NFS (Network File System)
– Protocol proiectat a fi independent de masina, sistem de operare si de
protocol – implementat peste RPC ( … conventia XDR)
– Protocol ce permite partajare de fisiere in retea => NFS ofera acces
transparent clientilor la fisiere
• Obs.: Diferit fata de FTP (vezi curs anterior)
– Ierarhia de directoare NFS foloseste terminologia UNIX (arbore, director,
cale, fisier etc.)
– NFS este un protocol => client - nfs , server –nfsd comunicand prin RPC
– Modelul NFS
• Operatii asupra unui fisier la distanta: operatii I/O,
creare/redenumire/stergere, stat, listarea intrarilor
• Comanda mount - specifica gazda remote, sistemul de fisiere ce
trebuie accesat si unde trebuie sa fie localizat in ierarhia locala de
fisiere
– RFC 1094
RPC|Utilizari
• Accesul la fisiere la distanta NFS (Network File System)
– Este transparent pentru utilizator
– Clientul NFS trimite o cerere RPC serverului RPC, folosind
TCP/IP
• Obs.: NFS a fost folosit predominant cu UDP
– Serverul NFS primeste cererile la portul 2049 si le trimite la
modulul de accesare a fisierelor locale
Obs.: Pentru deservirea rapida a clientilor, serverele NFS sunt in
general multi-threading sau pentru sisteme UNIX care nu sunt
multi-threading, se creeaza si raman in kernel instante multiple a
procesului (nfsd-uri)
RPC|Utilizari
• Accesul la fisiere la distanta NFS (Network File System)
– (0) este pornit portmapper–ul la boot-area sistemului
– (1) daemonul mountd este pornit pe server; creeaza end-point-uri
TCP si UDP, le asigneaza porturi efemere si apeleaza la portmapper
pentru inregistrarea lor
– (2) se executa comanda mount si se face o cerere la portmapper
pentru a obtine portul serverului demon de mount
– (3) portmapper–ul intoarce raspunsul
– (4) se creeaza o cerere RPC pentru montarea unui sistem de fisiere
– (5) serverul returneaza un file handle pentru sistemul de fisiere
cerut
– (6) Se asociaza acestui file handle un punct de montare local pe
client (file handle este stocat in codul clientului NFS si orice cerere
pentru sistemul de fisiere respectiv va utiliza acest file handle)
40
RPC|Utilizari
• Accesul la fisiere la distanta NFS (Network File System)
– Procesul de montare (protocolul mount)
• Pentru ca un client sa poata accesa fisiere dintr-un sistem
de fisiere, clientul trebuie sa foloseasca protocolul mount
');
COMMIT;
|
SELECT hkm.Ad,klk.Ad,seh.Ad,sob.Ad
FROM Elaveler elv
INNER JOIN Klinikalar klk ON elv.Klinika_Id=klk.Id
INNER JOIN Hekimler hkm ON klk.HekimId = hkm.Id
INNER JOIN Seherler seh ON elv.Seher_Id=seh.Id
INNER JOIN Sobeler sob ON elv.Sobe_Id=sob.Id
|
-- MySQL dump 10.13 Distrib 8.0.16, for Win64 (x86_64)
--
-- Host: localhost Database: vforum
-- ------------------------------------------------------
-- Server version 8.0.16
/*!40101 SET @OLD_CHARACTER_SET_CLIENT=@@CHARACTER_SET_CLIENT */;
/*!40101 SET @OLD_CHARACTER_SET_RESULTS=@@CHARACTER_SET_RESULTS */;
/*!40101 SET @OLD_COLLATION_CONNECTION=@@COLLATION_CONNECTION */;
SET NAMES utf8mb4 ;
/*!40103 SET @OLD_TIME_ZONE=@@TIME_ZONE */;
/*!40103 SET TIME_ZONE='+00:00' */;
/*!40014 SET @OLD_UNIQUE_CHECKS=@@UNIQUE_CHECKS, UNIQUE_CHECKS=0 */;
/*!40014 SET @OLD_FOREIGN_KEY_CHECKS=@@FOREIGN_KEY_CHECKS, FOREIGN_KEY_CHECKS=0 */;
/*!40101 SET @OLD_SQL_MODE=@@SQL_MODE, SQL_MODE='NO_AUTO_VALUE_ON_ZERO' */;
/*!40111 SET @OLD_SQL_NOTES=@@SQL_NOTES, SQL_NOTES=0 */;
--
-- Table structure for table `answers`
--
DROP TABLE IF EXISTS `answers`;
/*!40101 SET @saved_cs_client = @@character_set_client */;
SET character_set_client = utf8mb4 ;
CREATE TABLE `answers` (
`answerId` int(11) NOT NULL AUTO_INCREMENT,
`answerDescription` varchar(2000) DEFAULT NOT NULL,
`date` date DEFAULT NOT NULL,
`employeeId` int(11) DEFAULT NOT NULL,
`questionId` int(11) DEFAULT NOT NULL,
PRIMARY KEY (`answerId`),
KEY `employeeId` (`employeeId`),
KEY `questionId` (`questionId`),
CONSTRAINT `answers_ibfk_1` FOREIGN KEY (`employeeId`) REFERENCES `employee` (`employeeId`),
CONSTRAINT `answers_ibfk_2` FOREIGN KEY (`questionId`) REFERENCES `questions` (`questionId`)
) ENGINE=InnoDB AUTO_INCREMENT=2 DEFAULT CHARSET=utf8mb4 COLLATE=utf8mb4_0900_ai_ci;
/*!40101 SET character_set_client = @saved_cs_client */;
--
-- Dumping data for table `answers`
--
LOCK TABLES `answers` WRITE;
/*!40000 ALTER TABLE `answers` DISABLE KEYS */;
INSERT INTO `answers` VALUES (1,'it is a framework','2019-10-11',2,1);
/*!40000 ALTER TABLE `answers` ENABLE KEYS */;
UNLOCK TABLES;
--
-- Table structure for table `category`
--
DROP TABLE IF EXISTS `category`;
/*!40101 SET @saved_cs_client = @@character_set_client */;
SET character_set_client = utf8mb4 ;
CREATE TABLE `category` (
`categoryId` int(11) NOT NULL,
`categoryName` varchar(20) DEFAULT NOT NULL,
PRIMARY KEY (`categoryId`)
) ENGINE=InnoDB DEFAULT CHARSET=utf8mb4 COLLATE=utf8mb4_0900_ai_ci;
/*!40101 SET character_set_client = @saved_cs_client */;
--
-- Dumping data for table `category`
--
LOCK TABLES `category` WRITE;
/*!40000 ALTER TABLE `category` DISABLE KEYS */;
INSERT INTO `category` VALUES (1,'IT'),(2,'HR'),(3,'TECHNICAL'),(4,'GENERAL');
/*!40000 ALTER TABLE `category` ENABLE KEYS */;
UNLOCK TABLES;
--
-- Table structure for table `employee`
--
DROP TABLE IF EXISTS `employee`;
/*!40101 SET @saved_cs_client = @@character_set_client */;
SET character_set_client = utf8mb4 ;
CREATE TABLE `employee` (
`employeeId` int(11) NOT NULL,
`employeeName` varchar(30) DEFAULT NOT NULL,
`employeeDesignation` varchar(30) DEFAULT NOT NULL,
`employeeLocation` varchar(20) DEFAULT NOT NULL,
`username` varchar(20) DEFAULT NOT NULL,
`password` varchar(20) DEFAULT NOT NULL,
PRIMARY KEY (`employeeId`)
) ENGINE=InnoDB DEFAULT CHARSET=utf8mb4 COLLATE=utf8mb4_0900_ai_ci;
/*!40101 SET character_set_client = @saved_cs_client */;
--
-- Dumping data for table `employee`
--
LOCK TABLES `employee` WRITE;
/*!40000 ALTER TABLE `employee` DISABLE KEYS */;
INSERT INTO `employee` VALUES (1,'a','a','a','a','a'),(2,'b','b','b','b','b');
/*!40000 ALTER TABLE `employee` ENABLE KEYS */;
UNLOCK TABLES;
--
-- Table structure for table `questions`
--
DROP TABLE IF EXISTS `questions`;
/*!40101 SET @saved_cs_client = @@character_set_client */;
SET character_set_client = utf8mb4 ;
CREATE TABLE `questions` (
`questionId` int(11) NOT NULL AUTO_INCREMENT,
`questionDescription` varchar(2000) DEFAULT NOT NULL,
`date` date DEFAULT NOT NULL,
`employeeId` int(11) DEFAULT NOT NULL,
`categoryId` int(11) DEFAULT NOT NULL,
PRIMARY KEY (`questionId`),
KEY `employeeId` (`employeeId`),
KEY `categoryId` (`categoryId`),
CONSTRAINT `questions_ibfk_1` FOREIGN KEY (`employeeId`) REFERENCES `employee` (`employeeId`),
CONSTRAINT `questions_ibfk_2` FOREIGN KEY (`categoryId`) REFERENCES `category` (`categoryId`)
) ENGINE=InnoDB AUTO_INCREMENT=3 DEFAULT CHARSET=utf8mb4 COLLATE=utf8mb4_0900_ai_ci;
/*!40101 SET character_set_client = @saved_cs_client */;
--
-- Dumping data for table `questions`
--
LOCK TABLES `questions` WRITE;
/*!40000 ALTER TABLE `questions` DISABLE KEYS */;
INSERT INTO `questions` VALUES (1,'what is spring?','2019-10-11',1,1),(2,'what isspringboot','2019-10-11',2, 2);
/*!40000 ALTER TABLE `questions` ENABLE KEYS */;
UNLOCK TABLES;
/*!40103 SET TIME_ZONE=@OLD_TIME_ZONE */;
/*!40101 SET SQL_MODE=@OLD_SQL_MODE */;
/*!40014 SET FOREIGN_KEY_CHECKS=@OLD_FOREIGN_KEY_CHECKS */;
/*!40014 SET UNIQUE_CHECKS=@OLD_UNIQUE_CHECKS */;
/*!40101 SET CHARACTER_SET_CLIENT=@OLD_CHARACTER_SET_CLIENT */;
/*!40101 SET CHARACTER_SET_RESULTS=@OLD_CHARACTER_SET_RESULTS */;
/*!40101 SET COLLATION_CONNECTION=@OLD_COLLATION_CONNECTION */;
/*!40111 SET SQL_NOTES=@OLD_SQL_NOTES */;
-- Dump completed on 2019-10-11 22:43:50
|
select
state,
count(*) as count
from
current_state.prs
where
milestone='{{milestone}}'
and repo_name = 'kubernetes/kubernetes'
group by
state
order by
state
;
|
Create PROCEDURE sp_Delete_QuotationDetail(@QuotationID INT)
AS
Begin
DELETE FROM [QuotationItems] WHERE QuotationID = @QuotationID
DELETE FROM [QuotationMfrCategory] WHERE QuotationID = @QuotationID
DELETE FROM [QuotationUniversal] WHERE QuotationID = @QuotationID
DELETE FROM [QuotationCustomers] WHERE QuotationID = @QuotationID
DELETE FROM [QuotationMfrCategory_LeafLevel] where QuotationID = @QuotationID
End
|
create procedure sp_acc_retrieveinvoiceinfo(@invoiceid int)
as
select InvoiceType,PaymentMode
from InvoiceAbstract
where InvoiceID = @invoiceid
|
-- phpMyAdmin SQL Dump
-- version 4.6.6deb4
-- https://www.phpmyadmin.net/
--
-- Host: localhost:3306
-- Generation Time: Apr 27, 2017 at 06:20 PM
-- Server version: 5.7.17-0ubuntu1
-- PHP Version: 7.0.15-1ubuntu4
SET SQL_MODE = "NO_AUTO_VALUE_ON_ZERO";
SET time_zone = "+00:00";
/*!40101 SET @OLD_CHARACTER_SET_CLIENT=@@CHARACTER_SET_CLIENT */;
/*!40101 SET @OLD_CHARACTER_SET_RESULTS=@@CHARACTER_SET_RESULTS */;
/*!40101 SET @OLD_COLLATION_CONNECTION=@@COLLATION_CONNECTION */;
/*!40101 SET NAMES utf8mb4 */;
--
-- Database: `unzabeca`
--
-- --------------------------------------------------------
--
-- Table structure for table `committees`
--
--
-- Dumping data for table `committees`
--
INSERT INTO `committees` (`committee_id`, `committee_description`, `created_at`, `updated_at`) VALUES
('cmt-201', 'Alumna', NULL, NULL);
|
-- AlterTable
ALTER TABLE "Course" ALTER COLUMN "major" SET DEFAULT E'MIS';
|
-- sqlite3 schema
CREATE TABLE book (
id INTEGER PRIMARY KEY AUTOINCREMENT,
title VARCHAR(256) NOT NULL,
author VARCHAR(128) NOT NULL,
rating INTEGER NOT NULL
);
-- load some sample data
INSERT INTO book (title, author, rating) VALUES ('Harry Potter and the Goblet of Fire', 'J.K. Rowling', 5);
INSERT INTO book (title, author, rating) VALUES ('The Hunger Games', ' Suzanne Collins', 3);
INSERT INTO book (title, author, rating) VALUES ('A Song of Ice and Fire', ' George R. R. Martin', 4);
|
--
-- PostgreSQL database dump
--
-- Dumped from database version 12.3
-- Dumped by pg_dump version 12.3
-- Started on 2020-11-17 01:02:37
SET statement_timeout = 0;
SET lock_timeout = 0;
SET idle_in_transaction_session_timeout = 0;
SET client_encoding = 'UTF8';
SET standard_conforming_strings = on;
SELECT pg_catalog.set_config('search_path', '', false);
SET check_function_bodies = false;
SET xmloption = content;
SET client_min_messages = warning;
SET row_security = off;
SET default_tablespace = '';
SET default_table_access_method = heap;
--
-- TOC entry 207 (class 1259 OID 65576)
-- Name: categorias; Type: TABLE; Schema: public; Owner: postgres
--
CREATE TABLE public.categorias (
id integer NOT NULL,
denominacion character varying(60),
descripcion character varying(60)
);
ALTER TABLE public.categorias OWNER TO postgres;
--
-- TOC entry 206 (class 1259 OID 65574)
-- Name: categorias_id_seq; Type: SEQUENCE; Schema: public; Owner: postgres
--
CREATE SEQUENCE public.categorias_id_seq
AS integer
START WITH 1
INCREMENT BY 1
NO MINVALUE
NO MAXVALUE
CACHE 1;
ALTER TABLE public.categorias_id_seq OWNER TO postgres;
--
-- TOC entry 2858 (class 0 OID 0)
-- Dependencies: 206
-- Name: categorias_id_seq; Type: SEQUENCE OWNED BY; Schema: public; Owner: postgres
--
ALTER SEQUENCE public.categorias_id_seq OWNED BY public.categorias.id;
--
-- TOC entry 203 (class 1259 OID 65547)
-- Name: cliente; Type: TABLE; Schema: public; Owner: postgres
--
CREATE TABLE public.cliente (
id integer NOT NULL,
nombre character varying(60),
apellido character varying(60),
tipo_cliente_id integer,
documento integer NOT NULL
);
ALTER TABLE public.cliente OWNER TO postgres;
--
-- TOC entry 202 (class 1259 OID 65545)
-- Name: cliente_id_seq; Type: SEQUENCE; Schema: public; Owner: postgres
--
CREATE SEQUENCE public.cliente_id_seq
AS integer
START WITH 1
INCREMENT BY 1
NO MINVALUE
NO MAXVALUE
CACHE 1;
ALTER TABLE public.cliente_id_seq OWNER TO postgres;
--
-- TOC entry 2859 (class 0 OID 0)
-- Dependencies: 202
-- Name: cliente_id_seq; Type: SEQUENCE OWNED BY; Schema: public; Owner: postgres
--
ALTER SEQUENCE public.cliente_id_seq OWNED BY public.cliente.id;
--
-- TOC entry 209 (class 1259 OID 65584)
-- Name: producto; Type: TABLE; Schema: public; Owner: postgres
--
CREATE TABLE public.producto (
id integer NOT NULL,
categoria integer,
nombre character varying(60),
descripcion character varying(60),
precio integer
);
ALTER TABLE public.producto OWNER TO postgres;
--
-- TOC entry 208 (class 1259 OID 65582)
-- Name: producto_id_seq; Type: SEQUENCE; Schema: public; Owner: postgres
--
CREATE SEQUENCE public.producto_id_seq
AS integer
START WITH 1
INCREMENT BY 1
NO MINVALUE
NO MAXVALUE
CACHE 1;
ALTER TABLE public.producto_id_seq OWNER TO postgres;
--
-- TOC entry 2860 (class 0 OID 0)
-- Dependencies: 208
-- Name: producto_id_seq; Type: SEQUENCE OWNED BY; Schema: public; Owner: postgres
--
ALTER SEQUENCE public.producto_id_seq OWNED BY public.producto.id;
--
-- TOC entry 205 (class 1259 OID 65563)
-- Name: tipo_cliente; Type: TABLE; Schema: public; Owner: postgres
--
CREATE TABLE public.tipo_cliente (
id integer NOT NULL,
nombre character varying(60),
descripcion character varying(60)
);
ALTER TABLE public.tipo_cliente OWNER TO postgres;
--
-- TOC entry 204 (class 1259 OID 65561)
-- Name: tipo_cliente_id_seq; Type: SEQUENCE; Schema: public; Owner: postgres
--
CREATE SEQUENCE public.tipo_cliente_id_seq
AS integer
START WITH 1
INCREMENT BY 1
NO MINVALUE
NO MAXVALUE
CACHE 1;
ALTER TABLE public.tipo_cliente_id_seq OWNER TO postgres;
--
-- TOC entry 2861 (class 0 OID 0)
-- Dependencies: 204
-- Name: tipo_cliente_id_seq; Type: SEQUENCE OWNED BY; Schema: public; Owner: postgres
--
ALTER SEQUENCE public.tipo_cliente_id_seq OWNED BY public.tipo_cliente.id;
--
-- TOC entry 2707 (class 2604 OID 65579)
-- Name: categorias id; Type: DEFAULT; Schema: public; Owner: postgres
--
ALTER TABLE ONLY public.categorias ALTER COLUMN id SET DEFAULT nextval('public.categorias_id_seq'::regclass);
--
-- TOC entry 2705 (class 2604 OID 65550)
-- Name: cliente id; Type: DEFAULT; Schema: public; Owner: postgres
--
ALTER TABLE ONLY public.cliente ALTER COLUMN id SET DEFAULT nextval('public.cliente_id_seq'::regclass);
--
-- TOC entry 2708 (class 2604 OID 65587)
-- Name: producto id; Type: DEFAULT; Schema: public; Owner: postgres
--
ALTER TABLE ONLY public.producto ALTER COLUMN id SET DEFAULT nextval('public.producto_id_seq'::regclass);
--
-- TOC entry 2706 (class 2604 OID 65566)
-- Name: tipo_cliente id; Type: DEFAULT; Schema: public; Owner: postgres
--
ALTER TABLE ONLY public.tipo_cliente ALTER COLUMN id SET DEFAULT nextval('public.tipo_cliente_id_seq'::regclass);
--
-- TOC entry 2850 (class 0 OID 65576)
-- Dependencies: 207
-- Data for Name: categorias; Type: TABLE DATA; Schema: public; Owner: postgres
--
COPY public.categorias (id, denominacion, descripcion) FROM stdin;
7 dfr asd
8 trrr yui
\.
--
-- TOC entry 2846 (class 0 OID 65547)
-- Dependencies: 203
-- Data for Name: cliente; Type: TABLE DATA; Schema: public; Owner: postgres
--
COPY public.cliente (id, nombre, apellido, tipo_cliente_id, documento) FROM stdin;
3 Esteban Dalbano 1 3159318
4 pedro mazs 1 123
6 Cristian Quevedo 1 12334411
7 Cristian2 Monaca 1 1234444
8 pepito mengano 2 34555
9 erefe fdfdf 2 23232
\.
--
-- TOC entry 2852 (class 0 OID 65584)
-- Dependencies: 209
-- Data for Name: producto; Type: TABLE DATA; Schema: public; Owner: postgres
--
COPY public.producto (id, categoria, nombre, descripcion, precio) FROM stdin;
\.
--
-- TOC entry 2848 (class 0 OID 65563)
-- Dependencies: 205
-- Data for Name: tipo_cliente; Type: TABLE DATA; Schema: public; Owner: postgres
--
COPY public.tipo_cliente (id, nombre, descripcion) FROM stdin;
1 Asociado del gremio camioneros
2 Proveedor frutos secos
\.
--
-- TOC entry 2862 (class 0 OID 0)
-- Dependencies: 206
-- Name: categorias_id_seq; Type: SEQUENCE SET; Schema: public; Owner: postgres
--
SELECT pg_catalog.setval('public.categorias_id_seq', 8, true);
--
-- TOC entry 2863 (class 0 OID 0)
-- Dependencies: 202
-- Name: cliente_id_seq; Type: SEQUENCE SET; Schema: public; Owner: postgres
--
SELECT pg_catalog.setval('public.cliente_id_seq', 9, true);
--
-- TOC entry 2864 (class 0 OID 0)
-- Dependencies: 208
-- Name: producto_id_seq; Type: SEQUENCE SET; Schema: public; Owner: postgres
--
SELECT pg_catalog.setval('public.producto_id_seq', 1, false);
--
-- TOC entry 2865 (class 0 OID 0)
-- Dependencies: 204
-- Name: tipo_cliente_id_seq; Type: SEQUENCE SET; Schema: public; Owner: postgres
--
SELECT pg_catalog.setval('public.tipo_cliente_id_seq', 2, true);
--
-- TOC entry 2714 (class 2606 OID 65581)
-- Name: categorias categorias_pkey; Type: CONSTRAINT; Schema: public; Owner: postgres
--
ALTER TABLE ONLY public.categorias
ADD CONSTRAINT categorias_pkey PRIMARY KEY (id);
--
-- TOC entry 2710 (class 2606 OID 65552)
-- Name: cliente cliente_pkey; Type: CONSTRAINT; Schema: public; Owner: postgres
--
ALTER TABLE ONLY public.cliente
ADD CONSTRAINT cliente_pkey PRIMARY KEY (id);
--
-- TOC entry 2716 (class 2606 OID 65589)
-- Name: producto producto_pkey; Type: CONSTRAINT; Schema: public; Owner: postgres
--
ALTER TABLE ONLY public.producto
ADD CONSTRAINT producto_pkey PRIMARY KEY (id);
--
-- TOC entry 2712 (class 2606 OID 65568)
-- Name: tipo_cliente tipo_cliente_pkey; Type: CONSTRAINT; Schema: public; Owner: postgres
--
ALTER TABLE ONLY public.tipo_cliente
ADD CONSTRAINT tipo_cliente_pkey PRIMARY KEY (id);
--
-- TOC entry 2718 (class 2606 OID 65590)
-- Name: producto fk_categoria; Type: FK CONSTRAINT; Schema: public; Owner: postgres
--
ALTER TABLE ONLY public.producto
ADD CONSTRAINT fk_categoria FOREIGN KEY (categoria) REFERENCES public.categorias(id);
--
-- TOC entry 2717 (class 2606 OID 65569)
-- Name: cliente fk_tipo_cliente; Type: FK CONSTRAINT; Schema: public; Owner: postgres
--
ALTER TABLE ONLY public.cliente
ADD CONSTRAINT fk_tipo_cliente FOREIGN KEY (tipo_cliente_id) REFERENCES public.tipo_cliente(id);
-- Completed on 2020-11-17 01:02:38
--
-- PostgreSQL database dump complete
--
|
/*
Navicat MySQL Data Transfer
Source Server : root
Source Server Version : 80017
Source Host : localhost:3306
Source Database : mydb01
Target Server Type : MYSQL
Target Server Version : 80017
File Encoding : 65001
Date: 2019-10-12 18:01:45
*/
SET FOREIGN_KEY_CHECKS=0;
-- ----------------------------
-- Table structure for `tb_user`
-- ----------------------------
DROP TABLE IF EXISTS `tb_user`;
CREATE TABLE `tb_user` (
`username` varchar(50) CHARACTER SET utf8 COLLATE utf8_general_ci NOT NULL,
`email` varchar(50) CHARACTER SET utf8 COLLATE utf8_general_ci DEFAULT NULL,
`userid` bigint(20) DEFAULT NULL,
PRIMARY KEY (`username`),
UNIQUE KEY `username` (`username`) USING BTREE
) ENGINE=InnoDB DEFAULT CHARSET=utf8 COMMENT='用户表';
-- ----------------------------
-- Records of tb_user
-- ----------------------------
INSERT INTO `tb_user` VALUES ('CarryZhang', '15848@163.com', '1');
INSERT INTO `tb_user` VALUES ('RobinQueue', '1135@qq.com', '2');
|
CREATE TABLE `clientes` (
`c_id` int(3) NOT NULL AUTO_INCREMENT PRIMARY KEY,
`c_nom` varchar(45) NOT NULL,
`c_mail` varchar(60) NOT NULL,
`c_psswd` varchar(9) NOT NULL
) ENGINE=InnoDB DEFAULT CHARSET=latin1;
--
-- Volcado de datos para la tabla `clientes`
--
INSERT INTO `clientes` (`c_id`, `c_nom`, `c_mail`, `c_psswd`) VALUES
(NULL, 'Abril Garcia', 'abrilgarcia@gmail.com', '930137298'),
(NULL,'Amparo Gonzalez', 'amparogonzalez@gmail.com', '939458713'),
(NULL,'Dolores Fernandez', 'doloresfernandez@gmail.com', '937946380'),
(NULL,'Pedro Martinez', 'pedromartinez@gmail.com', '930000343'),
(NULL,'Ramona Brochas', 'ramonabrochas@gmail.com', 'ABCDEfghi'),
(NULL,'Patricio Ruiz', 'esponja@gmail.com', '934242480'),
(NULL,'Tecla Mouse', 'teclamaouse@gmail.com', '645CDEfghi'),
(NULL,'Cargador Pantalla', 'cargadorpantalla@gmail.com', 'CDEf9365');
-- --------------------------------------------------------
--
-- Estructura de tabla para la tabla `autor`
--
CREATE TABLE `autor` (
`a_id` int(3) NOT NULL AUTO_INCREMENT PRIMARY KEY ,
`a_nombre` varchar(45) NOT NULL,
`a_dir` varchar(45) NULL
) ENGINE=InnoDB DEFAULT CHARSET=latin1;
--
-- Volcado de datos para la tabla `autor`
--
INSERT INTO `autor` (`a_nombre`, `a_dir`) VALUES
('Tolkien', 'Barcelona'),
('Borges', 'Bahamas'),
('Kafka', 'Japon'),
('Maxwell', 'Burgos');
-- --------------------------------------------------------
--
-- Estructura de tabla para la tabla `catalogo`
--
CREATE TABLE `catalogo` (
`ca_id` int(3) NOT NULL AUTO_INCREMENT PRIMARY KEY ,
`ca_libro` varchar(45) NOT NULL,
`a_nombre` varchar(45) NOT NULL,
`ca_precio` int(255) NOT NULL,
`ca_stock` int(255) NOT NULL
) ENGINE=InnoDB DEFAULT CHARSET=latin1;
ALTER TABLE `catalogo`
ADD KEY (`a_nombre`);
--
-- Volcado de datos para la tabla `catalogo`
--
INSERT INTO `catalogo` (`ca_libro`, `a_nombre`, `ca_precio`, `ca_stock`) VALUES
('Las ilusiones perdidas', 'Tolkien', 37, 500),
('Cepillo de dientes eléctrico', 'Borges', 40, 1500),
('Un cuento perfecto', 'Kafka', 17, 1000),
('Mascarillas voladoras', 'Maxwell', 6, 4000),
('Zapatos sin planos', 'Maxwell', 30, 150),
('Smart y smartos', 'Kafka', 35, 280);
-- --------------------------------------------------------
--
-- Estructura de tabla para la tabla `pedidos`
--
CREATE TABLE `pedidos` (
`p_id` int(3) NOT NULL AUTO_INCREMENT PRIMARY KEY ,
`c_id` int(3) NOT NULL,
`ca_id` int(3) NOT NULL,
`f_pedido` date NULL
) ENGINE=InnoDB DEFAULT CHARSET=latin1;
ALTER TABLE `pedidos`
ADD KEY (`p_id`);
--
-- Volcado de datos para la tabla `pedidos`
--
INSERT INTO `pedidos` (`c_id`, `ca_id`, `f_pedido`) VALUES
(2, 2, null),
(3, 3, '2020-08-19'),
(3, 4, null),
(4, 2, null),
(5, 2, '2020-08-19'),
(6, 3, null),
(5, 4, null),
(6, 2, '2020-08-19');
-- --------------------------------------------------------
--
-- Estructura de tabla para la tabla `factura`
--
CREATE TABLE `factura` (
`fact_id` int(3) NOT NULL AUTO_INCREMENT PRIMARY KEY ,
`p_id` int(3) NOT NULL,
`libroPedido` int(3) NOT NULL,
`cantidad` int(255) NOT NULL
) ENGINE=InnoDB DEFAULT CHARSET=latin1;
ALTER TABLE `factura`
ADD KEY (`p_id`),
ADD KEY (`libroPedido`);
DELIMITER $$
CREATE TRIGGER restar_stock
after INSERT ON `factura` FOR EACH ROW
begin
UPDATE `catalogo`
SET ca_stock = ca_stock - NEW.cantidad
WHERE ca_id = NEW.libroPedido ;
END;
$$
DELIMITER ;
--
-- Volcado de datos para la tabla `factura`
--
INSERT INTO `factura` (`p_id`, `libroPedido`, `cantidad`) VALUES
(1, 3, 5),
(2, 6, 4),
(2, 2, 8),
(3, 1, 70),
(3, 5, 4),
(4, 6, 6),
(4, 3, 10),
(5, 4, 7),
(6, 1, 3),
(2, 2, 3),
(2, 4, 4),
(5, 5, 5),
(1, 4, 50),
(3, 2, 10),
(4, 1, 2),
(1, 2, 5),
(3, 4, 3),
(5, 2, 20);
--
-- Indices de la tabla `factura`
--
ALTER TABLE `factura`
ADD CONSTRAINT `fk_libroPedido ` FOREIGN KEY (`libroPedido`)
REFERENCES `catalogo` (`ca_id`) ON UPDATE CASCADE
ADD CONSTRAINT `fk_p_id ` FOREIGN KEY (`p_id`)
REFERENCES `pedidos` (`p_id`) ON UPDATE CASCADE;
--
-- Indices de la tabla `pedidos`
--
ALTER TABLE `pedidos`
ADD CONSTRAINT `fk_p_id` FOREIGN KEY (`p_id`)
REFERENCES `clientes` (`c_id`) ON UPDATE CASCADE;
|
create procedure mERP_SP_CLOCRNotesNotAdjusted @ActivityCode nvarchar(max)
AS
BEGIN
set dateformat dmy
Create table #CLOActivitycode(ID Int Identity(1,1), ActivityCode nVarchar(255) COLLATE SQL_Latin1_General_CP1_CI_AS)
Insert Into #CLOActivitycode
Select * from dbo.sp_SplitIn2Rows(@ActivityCode, ',')
Select CLO.ActivityCode,C.Company_Name as CustomerName ,CLO.CLOType, CLO.CLOMonth, CLO.CLODate , CLO.RefNumber, CR.Balance --Amount
,CLO.Category ,C.CustomerID ,CLO.CreditID
From CLOCrNote CLO
Join CreditNote CR On CR.CreditID = CLO.CreditID And CR.Balance > 0
Join Customer C on CLO.CustomerID = C.CustomerID and ActivityCode in
(select ActivityCode from #CLOActivitycode) And CLO.active= 1 and isnull(IsGenerated,0)=1
--And CreditID in (select CreditID from CreditNote where balance >0)
order by C.Company_Name
END
|
--修改时间：2013-01-30
--修改人：费滔
--修改原因：V10.4BUG,发现以下提醒没法通过参数是否启用控制控制
--银行借款提醒
DECLARE
VN_COUNT NUMBER;
BEGIN
SELECT COUNT(*)
INTO VN_COUNT
from SYS_SUBSCRIBE_RULES where Notice_Name = '银行借款提醒' and Sys_Code = 'cms';
IF VN_COUNT < 1 THEN
insert into SYS_SUBSCRIBE_RULES (ID, SYS_CODE, NOTICE_TYPE, NOTICE_NAME, PRE_DAYS, TITLE, CONTENT, TRIGGER_NAME, TRIGGER_CNDT, SHOW_TYPE, VALIDE_SIGN, CREATE_TIME, MODIFY_TIME)
values (29, 'cms', '29', '银行借款提醒', '10', '银行借款提醒', '您有${count}笔银行借款到期！', '', '', '2;', '1', sysdate, null);
END IF;
COMMIT;
END;
/
|
create or replace function SHOWREQEVENT(FSPONID IN NUMBER,COUNTER OUT NUMBER)
return NAMEARR
IS
NAM NAMEARR;
J NUMBER;
CURSOR SHOWN IS
SELECT NAME FROM FEST E,FESTSPONREQ F WHERE E.EXIST =1 AND F.SPONID=FSPONID AND F.FID=E.ID;
BEGIN
NAM :=NAMEARR();
J :=1;
FOR I IN SHOWN LOOP NAM.EXTEND;
NAM(J) :=I.NAME; J :=J+1;
END LOOP;
COUNTER :=J-1;
return nam;
END; |
/*
SQLyog Community v13.1.2 (64 bit)
MySQL - 10.3.15-MariaDB : Database - studentapp
*********************************************************************
*/
/*!40101 SET NAMES utf8 */;
/*!40101 SET SQL_MODE=''*/;
/*!40014 SET @OLD_UNIQUE_CHECKS=@@UNIQUE_CHECKS, UNIQUE_CHECKS=0 */;
/*!40014 SET @OLD_FOREIGN_KEY_CHECKS=@@FOREIGN_KEY_CHECKS, FOREIGN_KEY_CHECKS=0 */;
/*!40101 SET @OLD_SQL_MODE=@@SQL_MODE, SQL_MODE='NO_AUTO_VALUE_ON_ZERO' */;
/*!40111 SET @OLD_SQL_NOTES=@@SQL_NOTES, SQL_NOTES=0 */;
CREATE DATABASE /*!32312 IF NOT EXISTS*/`studentapp` /*!40100 DEFAULT CHARACTER SET utf8 */;
USE `studentapp`;
/*Table structure for table `predmet` */
DROP TABLE IF EXISTS `predmet`;
CREATE TABLE `predmet` (
`sifra` varchar(20) NOT NULL,
`naziv` varchar(50) DEFAULT NULL,
`brojESPB` int(3) DEFAULT NULL,
PRIMARY KEY (`sifra`)
) ENGINE=InnoDB DEFAULT CHARSET=utf8;
/*Data for the table `predmet` */
insert into `predmet`(`sifra`,`naziv`,`brojESPB`) values
('111EKO','Ekonomija',6),
('111MAT','Matematika',8),
('111STA','Statistika',7);
/*Table structure for table `prijava` */
DROP TABLE IF EXISTS `prijava`;
CREATE TABLE `prijava` (
`brojIndeksa` varchar(20) NOT NULL,
`sifraPredmeta` varchar(20) NOT NULL,
`datum` date NOT NULL,
`ocena` int(2) DEFAULT NULL,
PRIMARY KEY (`brojIndeksa`,`sifraPredmeta`,`datum`),
KEY `sifraPredmeta` (`sifraPredmeta`),
KEY `brojIndeksa` (`brojIndeksa`),
CONSTRAINT `prijava_ibfk_1` FOREIGN KEY (`brojIndeksa`) REFERENCES `student` (`brojIndeksa`) ON UPDATE CASCADE,
CONSTRAINT `prijava_ibfk_2` FOREIGN KEY (`sifraPredmeta`) REFERENCES `predmet` (`sifra`) ON UPDATE CASCADE
) ENGINE=InnoDB DEFAULT CHARSET=utf8;
/*Data for the table `prijava` */
insert into `prijava`(`brojIndeksa`,`sifraPredmeta`,`datum`,`ocena`) values
('0001/2019','111EKO','2019-12-28',8),
('0001/2019','111MAT','2019-12-29',9),
('0002/2019','111EKO','2019-12-28',9),
('0002/2019','111STA','2019-12-28',10),
('0003/2019','111MAT','2019-12-27',10),
('0003/2019','111STA','2019-12-29',9);
/*Table structure for table `student` */
DROP TABLE IF EXISTS `student`;
CREATE TABLE `student` (
`brojIndeksa` varchar(20) NOT NULL,
`ime` varchar(50) DEFAULT NULL,
`prezime` varchar(50) DEFAULT NULL,
PRIMARY KEY (`brojIndeksa`)
) ENGINE=InnoDB DEFAULT CHARSET=utf8;
/*Data for the table `student` */
insert into `student`(`brojIndeksa`,`ime`,`prezime`) values
('0001/2019','Ana','Anic'),
('0002/2019','Sanja','Sanjic'),
('0003/2019','Marko','Markovic');
/*!40101 SET SQL_MODE=@OLD_SQL_MODE */;
/*!40014 SET FOREIGN_KEY_CHECKS=@OLD_FOREIGN_KEY_CHECKS */;
/*!40014 SET UNIQUE_CHECKS=@OLD_UNIQUE_CHECKS */;
/*!40111 SET SQL_NOTES=@OLD_SQL_NOTES */;
|
ALTER TABLE integra_recibo ADD COLUMN numbanco varchar(50) default null;
ALTER TABLE integra_recibo ADD COLUMN numdoc_new integer;
UPDATE integra_recibo
SET numdoc_new = numdoc::integer;
ALTER TABLE integra_recibo DROP COLUMN numdoc;
ALTER TABLE integra_recibo RENAME COLUMN numdoc_new TO numdoc;
ALTER TABLE integra_cad_config ADD COLUMN faixa_inicial_numbanco integer;
ALTER TABLE integra_cad_config ADD COLUMN faixa_final_numbanco integer;
CREATE UNIQUE INDEX integra_recibo_cod_barras_in ON integra_recibo(cod_barras);
CREATE UNIQUE INDEX integra_recibo_numdoc_in ON integra_recibo(numdoc);
CREATE UNIQUE INDEX integra_recibo_numbanco_in ON integra_recibo(numbanco);
|
Subsets and Splits
No community queries yet
The top public SQL queries from the community will appear here once available.