Home > Database > Mysql Tutorial > Mysql series (8) writing scripts

Mysql series (8) writing scripts

黄舟
Release: 2017-01-22 16:56:18
Original
3277 people have browsed it

First steps (generally can be omitted):
Start the MySQL service (the default is to run automatically when booting):
Control Panel-->Management Tools-->Services, find the name inside For mysql items, double-click to see whether its service status is started or stopped, and set it to start

Connect to mysql:
Enter mysql -h localhost -u root -p at the command line and press Enter , and then enter the password; or directly run the connection tool that comes with mysql, and then enter the password.

1. Write the sql script, assuming the content is as follows:

create database dearabao;
  use dearabao;
  create table niuzi (name varchar(20));
Copy after login

Save the script file, Suppose I save it in the hello world directory of drive F, so the path of the file is: F:/hello world/niuzi.sql



2. There are two ways to execute the sql script:
The first method:
In the command line (not connected to the database), enter mysql -h localhost -u root -p123456 < F:/hello world/niuzi .sql (note that the path does not need to be quoted!!) Just press Enter.
Second method:
In the command line (the database is connected, the prompt at this time is mysql>), enter source F :/hello world/niuzi.sql (note that the path does not need to be quoted) or /. F:/hello world/niuzi.sql (note that the path does not need to be quoted) and press Enter

SQL writing specifications

1. Writing format
Sample code:

Example of stored procedure SQL writing format

select 
        c.dealerCode,
        round(sum(c.submitSubletAmountDLR + c.submitPartsAmountDLR + c.submitLaborAmountDLR) / count(*), 2) as avg, 
        decode(null, &#39;x&#39;, &#39;xx&#39;, &#39;CNY&#39;) 
from ( 
        select 
                a.dealerCode,
                a.submitSubletAmountDLR, 
                a.submitPartsAmountDLR, 
                a.submitLaborAmountDLR 
        from SRV_TWC_F a
        where (to_char(a.ORIGSUBMITTIME, &#39;yyyy/mm/dd&#39;) >= &#39;Date Range(start)&#39; 
        and to_char(a.ORIGSUBMITTIME, &#39;yyyy/mm/dd&#39;) <= &#39;Date Range(end)&#39;   
        and nvl(a.deleteflag, &#39;0&#39;) <> &#39;1&#39;) 
        union all 
        select 
                b.dealerCode,
                b.submitSubletAmountDLR, 
                b.submitPartsAmountDLR, 
                b.submitLaborAmountDLR 
        from SRV_TWCHistory_F b
        where (to_char(b.ORIGSUBMITTIME, &#39;yyyy/mm/dd&#39;) >= &#39;Date Range(start)&#39; 
        and to_char(b.ORIGSUBMITTIME,&#39;yyyy/mm/dd&#39;) <= &#39;Date Range(end)&#39;   
        and nvl(b.deleteflag,&#39;0&#39;) <> &#39;1&#39;)
) c
group by c.dealerCode 
order by avg desc;
Copy after login

SQL characters in Java source String writing format example

strSQL = "insert into Snd_FinanceHistory_Tb "    
+ "(DEALERCODE, "   
 + "REQUESTSEQUECE, "   
  + "HANDLETIME, "    
  + "JOBFLAG, "    
  + "FRAMENO, "    
  + "INMONEY, "   
   + "REMAINMONEY, "   
   + "DELETEFLAG, "   
    + "UPDATECOUNT, "   
     + "CREUSER, "    
     + "CREDATE, "    
     + "HONORCHECKNO, "    
     + "SEQ) "    
     + "values (&#39;" + draftInputDetail.dealerCode + "&#39;, "   
      + "&#39;" + draftInputDetail.requestsequece + "&#39;, "    
      + "sysdate, "    + "&#39;07&#39;, "    + "&#39;" + frameNO + "&#39;, "    
      + requestMoney + ", "    + remainMoney + ", "    + "&#39;0&#39;, "    + "0, "   
       + "&#39;" + draftStruct.employeeCode + "&#39;, "    + "sysdate, "    
       + "&#39;" + draftInputDetail.honorCheckNo + "&#39;, "    + index + ")";
Copy after login

1). Indentation
For stored procedure files, the indentation is 8 spaces
For SQL strings in Java source, there is no indentation. That is, each line of string cannot start with a space

2). Line break
1>.Select/From/Where/Order by/Group by and other clauses must be written on another line
2>.If there is only one item in the Select clause, write
along with Select 3>.If there is more than one item in the Select clause, each item should occupy a separate line, and indent 8 to the right based on the corresponding Select spaces (Java source has no indentation)
4> If there is only one item in the From clause, write it along with From
5> If there is more than one item in the From clause, each item occupies its own line , indent 8 spaces to the right based on the corresponding From (Java source has no indentation)
6>.If there are multiple conditions in the Where clause, each condition occupies one line, starts with AND, and has no indentation Enter
7>.(Update)Set clause content Each item occupies a separate line, no indentation
8>.Insert clause content Each table field occupies a separate line, no indentation; values ​​​​each item Occupy one line by itself, no indentation
9>.No blank lines are allowed in the middle of the SQL text
10>.The single quotation mark in Java source must be on the same line as the SQL clause to which it belongs, and the connector ("+" ) must be at the beginning of the line

3). Space
1>.The two elements connected by the arithmetic operator and logical operator in SQL must be separated by a space
2>.Must be followed by a comma Follow a space
3>. There must be a space between keywords, reserved words and left brackets

2. It does not mean uniform use of "<>"
Oracle believes that "!=" are equivalent to "<>" and both represent the meaning of unequal. For the sake of unification, it does not mean that "<>" is always used

3. Use the alias of the table
For database query, you must use the alias of the table

4.SQL text to match the table fields Extended compatibility
When using Select * in Java source, it is strictly prohibited to obtain query results in the form of getString(1). The form of getString("field name") must be used.
When using Insert, the inserted value must be specified. Field name, it is strictly prohibited to directly insert values ​​without specifying a field name

5. Reduce the use of subqueries
In addition to poor readability, subqueries also affect SQL operating efficiency to a certain extent
Please Minimize the use of subqueries and replace them with other more efficient and readable methods

6. Add indexes appropriately to improve query efficiency
Adding indexes appropriately can greatly improve the retrieval speed
Please refer to the ORACLE SQL Performance Optimization Series

7. Special requirements for database table operations
This project also has the following special requirements for database table operations:

1). Replace physical deletion with logical deletion
Note: There is no physical deletion of data in the database table, only logical deletion
Use the deleteeflag field as the deletion flag, deleteeflag='1' means that this record has been logically deleted, so when querying the data The factor of deleteflag must be considered
The standard query condition for deleteflag: NVL(deleteflag, '0') <> '1'

2). Add a record status field
Each record in the database The table basically has the following fields: DELETEFLAG, UPDATECOUNT, CREDATE, CREUSER, UPDATETIME, UPDATEUSER
Please note that the following fields must be considered when performing benchmark operations

插入一条记录时要置DELETEFLAG='0', UPDATECOUNT=0, CREDATE=sysdate, CREUSER=登录User
查询一条记录时要考虑DELETEFLAG,如果有可能对此记录作更新时还要取得UPDATECOUNT作同步检查
修改一条记录时要置UPDATETIME=sysdate, UPDATEUSER=登录User, UPDATECOUNT=(UPDATECOUNT+1) mod 1000,
删除一条记录时要置DELETEFLAG='1'

3).历史表
数据库里部分表还存在相应的历史表,比如srv_twc_f和srv_twchistory_f
在查询数据时除了检索所在表之外,还必须检索相应的历史表,对二者的结果做Union(或Union All)

8.用执行计划分析SQL性能
EXPLAIN PLAN是一个很好的分析SQL语句的工具,它可以在不执行SQL的情况下分析语句
通过分析,我们就可以知道ORACLE是怎样连接表,使用什么方式扫描表(索引扫描或全表扫描),以及使用到的索引名称

按照从里到外,从上到下的次序解读分析的结果
EXPLAIN PLAN的分析结果是用缩进的格式排列的,最内部的操作将最先被解读,如果两个操作处于同一层中,带有最小操作号的将首先被执行

目前许多第三方的工具如PLSQL Developer和TOAD等都提供了极其方便的EXPLAIN PLAN工具
PG需要将自己添加的查询SQL文记入log,然后在EXPLAIN PLAN中进行分析,尽量减少全表扫描


ORACLE SQL性能优化系列

1.选择最有效率的表名顺序(只在基于规则的优化器中有效)
ORACLE的解析器按照从右到左的顺序处理FROM子句中的表名,因此FROM子句中写在最后的表(基础表driving table)将被最先处理
在FROM子句中包含多个表的情况下,必须选择记录条数最少的表作为基础表
当ORACLE处理多个表时,会运用排序及合并的方式连接它们
首先,扫描第一个表(FROM子句中最后的那个表)并对记录进行排序;
然后扫描第二个表(FROM子句中最后第二个表);
最后将所有从第二个表中检索出的记录与第一个表中合适记录进行合并
例如:
表 TAB1 16,384 条记录
表 TAB2 5 条记录
选择TAB2作为基础表 (最好的方法)
select count(*) from tab1,tab2 执行时间0.96秒
选择TAB2作为基础表 (不佳的方法)
select count(*) from tab2,tab1 执行时间26.09秒

如果有3个以上的表连接查询,那就需要选择交叉表(intersection table)作为基础表,交叉表是指那个被其他表所引用的表
例如:
EMP表描述了LOCATION表和CATEGORY表的交集

  SELECT * 
       FROM LOCATION L,
       CATEGORY C,
       EMP E
       WHERE E.EMP_NO BETWEEN 1000 AND 2000
       AND E.CAT_NO = C.CAT_NO
       AND E.LOCN = L.LOCN
Copy after login

将比下列SQL更有效率

  SELECT * 
       FROM EMP E ,
       LOCATION L ,
       CATEGORY C
       WHERE E.CAT_NO = C.CAT_NO
       AND E.LOCN = L.LOCN
       AND E.EMP_NO BETWEEN 1000 AND 2000
Copy after login

2.WHERE子句中的连接顺序
ORACLE采用自下而上的顺序解析WHERE子句
根据这个原理,表之间的连接必须写在其他WHERE条件之前,那些可以过滤掉最大数量记录的条件必须写在WHERE子句的末尾
例如:
(低效,执行时间156.3秒)

    SELECT *
       FROM EMP E
       WHERE SAL > 50000
       AND JOB = &#39;MANAGER&#39;
       AND 25 < (SELECT COUNT(*) FROM EMP WHERE MGR=E.EMPNO);
Copy after login

(高效,执行时间10.6秒)

     SELECT *
       FROM EMP E
       WHERE 25 < (SELECT COUNT(*) FROM EMP WHERE MGR=E.EMPNO)
       AND SAL > 50000
       AND JOB = &#39;MANAGER&#39;;
Copy after login

3.SELECT子句中避免使用'*'
当你想在SELECT子句中列出所有的COLUMN时,使用动态SQL列引用'*'是一个方便的方法,不幸的是,这是一个非常低效的方法
实际上,ORACLE在解析的过程中,会将'*'依次转换成所有的列名
这个工作是通过查询数据字典完成的,这意味着将耗费更多的时间

4.减少访问数据库的次数
当执行每条SQL语句时,ORACLE在内部执行了许多工作:解析SQL语句,估算索引的利用率,绑定变量,读数据块等等
由此可见,减少访问数据库的次数,就能实际上减少ORACLE的工作量
例如:
以下有三种方法可以检索出雇员号等于0342或0291的职员
方法1 (最低效)

   SELECT EMP_NAME, SALARY, GRADE      FROM EMP      WHERE EMP_NO = 342;
      SELECT EMP_NAME, SALARY, GRADE      FROM EMP      WHERE EMP_NO = 291;
Copy after login

方法2 (次低效)

   DECLARE
      CURSOR C1 (E_NO NUMBER) IS
      SELECT EMP_NAME,SALARY,GRADE
      FROM EMP
      WHERE EMP_NO = E_NO;
      BEGIN
      OPEN C1(342);
      FETCH C1 INTO …,…,…;
      …
      OPEN C1(291);
      FETCH C1 INTO …,…,…;
      …
      CLOSE C1;
      END;
Copy after login

方法2 (高效)

  SELECT A.EMP_NAME, A.SALARY, A.GRADE,
             B.EMP_NAME, B.SALARY, B.GRADE
      FROM EMP A, EMP B
      WHERE A.EMP_NO = 342
      AND B.EMP_NO = 291;
Copy after login

5.使用DECODE函数来减少处理时间
使用DECODE函数可以避免重复扫描相同记录或重复连接相同的表
例如:

    SELECT COUNT(*), SUM(SAL)    FROM EMP    WHERE DEPT_NO = &#39;0020&#39;    AND ENAME LIKE &#39;SMITH%&#39;;
    SELECT COUNT(*), SUM(SAL)    FROM EMP    WHERE DEPT_NO = &#39;0030&#39;    AND ENAME LIKE &#39;SMITH%&#39;;
Copy after login

你可以用DECODE函数高效地得到相同结果

SELECT COUNT(DECODE(DEPT_NO, &#39;0020&#39;, &#39;X&#39;, NULL)) D0020_COUNT,
    COUNT(DECODE(DEPT_NO, &#39;0030&#39;, &#39;X&#39;, NULL)) D0030_COUNT,
    SUM(DECODE(DEPT_NO, &#39;0020&#39;, SAL, NULL)) D0020_SAL, 
    SUM(DECODE(DEPT_NO, 0030, SAL, NULL)) D0030_SAL
    FROM EMP
    WHERE ENAME LIKE &#39;SMITH%&#39;;
Copy after login

'X'表示任何一个字段
类似的,DECODE函数也可以运用于GROUP BY和ORDER BY子句中

6.用Where子句替换HAVING子句
避免使用HAVING子句,HAVING只会在检索出所有记录之后才对结果集进行过滤,这个处理需要排序、统计等操作
如果能通过WHERE子句限制记录的数目,那就能减少这方面的开销
例如:
低效

SELECT REGION, AVG(LOG_SIZE)
    FROM LOCATION
    GROUP BY REGION
    HAVING REGION REGION != &#39;SYDNEY&#39;
    AND REGION != &#39;PERTH&#39;
Copy after login

高效

SELECT REGION, AVG(LOG_SIZE)
    FROM LOCATION
    WHERE REGION REGION != &#39;SYDNEY&#39;
    AND REGION != &#39;PERTH&#39;
    GROUP BY REGION
Copy after login

7.减少对表的查询
在含有子查询的SQL语句中,要特别注意减少对表的查询
例如:
低效

   SELECT TAB_NAME
    FROM TABLES
    WHERE TAB_NAME = (SELECT TAB_NAME 
                      FROM TAB_COLUMNS
                      WHERE VERSION = 604)
    AND DB_VER = (SELECT DB_VER
                  FROM TAB_COLUMNS
                  WHERE VERSION = 604)
Copy after login

高效

SELECT TAB_NAME
    FROM TABLES
    WHERE (TAB_NAME, DB_VER) = (SELECT TAB_NAME, DB_VER
                                FROM TAB_COLUMNS
                                WHERE VERSION = 604)
Copy after login

Update多个Column例子:
低效

    UPDATE EMP    SET EMP_CAT = (SELECT MAX(CATEGORY)           
             FROM EMP_CATEGORIES),     
             SAL_RANGE = (SELECT MAX(SAL_RANGE)                 
              FROM EMP_CATEGORIES)    
              WHERE EMP_DEPT = 0020;
Copy after login

高效

 UPDATE EMP
    SET (EMP_CAT, SAL_RANGE) = (SELECT MAX(CATEGORY), MAX(SAL_RANGE)
                                FROM EMP_CATEGORIES)
    WHERE EMP_DEPT = 0020;
Copy after login

8.使用表的别名(Alias)
当在SQL语句中连接多个表时,请使用表的别名并把别名前缀于每个Column上
这样可以减少解析的时间并减少那些由Column歧义引起的语法错误

9.用EXISTS替代IN
在许多基于基础表的查询中,为了满足一个条件,往往需要对另一个表进行联接
在这种情况下,使用EXISTS(或NOT EXISTS)通常将提高查询的效率
低效

  SELECT *
    FROM EMP (基础表)
    WHERE EMPNO > 0
    AND DEPTNO IN (SELECT DEPTNO
                   FROM DEPT
                   WHERE LOC = &#39;MELB&#39;)
Copy after login

高效

    SELECT *
    FROM EMP (基础表)
    WHERE EMPNO > 0
    AND EXISTS (SELECT &#39;X&#39;
    FROM DEPT
    WHERE DEPT.DEPTNO = EMP.DEPTNO
    AND LOC = &#39;MELB&#39;)
Copy after login

10.用NOT EXISTS替代NOT IN
在子查询中,NOT IN子句将执行一个内部的排序和合并
无论在哪种情况下,NOT IN都是最低效的,因为它对子查询中的表执行了一个全表遍历
为了避免使用NOT IN,我们可以把它改写成外连接(Outer Joins)或NOT EXISTS
例如:

SELECT …
    FROM EMP
    WHERE DEPT_NO NOT IN (SELECT DEPT_NO
                          FROM DEPT
                          WHERE DEPT_CAT = &#39;A&#39;);
Copy after login

为了提高效率改写为
高效

  SELECT …
    FROM EMP A, DEPT B
    WHERE A.DEPT_NO = B.DEPT(+)
    AND B.DEPT_NO IS NULL
    AND B.DEPT_CAT(+) = &#39;A&#39;
Copy after login

最高效

SELECT …
    FROM EMP E
    WHERE NOT EXISTS (SELECT &#39;X&#39;
                      FROM DEPT D
                      WHERE D.DEPT_NO = E.DEPT_NO
                      AND DEPT_CAT = &#39;A&#39;);
Copy after login

11.用表连接替换EXISTS
通常来说,采用表连接的方式比EXISTS更有效率
例如:

SELECT ENAME
    FROM EMP E
    WHERE EXISTS (SELECT &#39;X&#39;
                  FROM DEPT
                  WHERE DEPT_NO = E.DEPT_NO
                  AND DEPT_CAT = &#39;A&#39;);
Copy after login

更高效

 SELECT ENAME
    FROM DEPT D, EMP E
    WHERE E.DEPT_NO = D.DEPT_NO
    AND DEPT_CAT = &#39;A&#39;;
Copy after login

12.用EXISTS替换DISTINCT
当提交一个包含多表信息(比如部门表和雇员表)的查询时,避免在SELECT子句中使用DISTINCT,一般可以考虑用EXIST替换
例如:
低效

 SELECT DISTINCT DEPT_NO, DEPT_NAME
    FROM DEPT D, EMP E
    WHERE D.DEPT_NO = E.DEPT_NO
Copy after login

高效

SELECT DEPT_NO, DEPT_NAME
    FROM DEPT D
    WHERE EXISTS (SELECT &#39;X&#39;
                  FROM EMP E
                  WHERE E.DEPT_NO = D.DEPT_NO);
Copy after login

EXISTS使查询更为迅速,因为RDBMS核心模块将在子查询的条件一旦满足后,立刻返回结果

13.用索引提高效率
索引是表的一个概念部分,用来提高检索数据的效率。实际上,ORACLE使用了一个复杂的自平衡B-tree结构
通常,通过索引查询数据比全表扫描要快。当ORACLE找出执行查询和Update语句的最佳路径时,ORACLE优化器将使用索引
同样,在联结多个表时使用索引也可以提高效率。另一个使用索引的好处是,它提供了主键(primary key)的唯一性验证

除了那些LONG或LONG RAW数据类型,你可以索引几乎所有的列
通常在大型表中使用索引特别有效,当然,在扫描小表时,使用索引同样能提高效率

虽然使用索引能得到查询效率的提高,但是我们也必须注意到它的代价
索引需要空间来存储,也需要定期维护,每当有记录在表中增减或索引列被修改时,索引本身也会被修改
这意味着每条记录的INSERT、DELETE、UPDATE将为此多付出4、5次的磁盘I/O
因为索引需要额外的存储空间和处理,那些不必要的索引反而会使查询反应时间变慢

ORACLE对索引有两种访问模式:
1).索引唯一扫描(INDEX UNIQUE SCAN)
大多数情况下, 优化器通过WHERE子句访问INDEX
例如:
表LODGING有两个索引:建立在LODGING列上的唯一性索引LODGING_PK和建立在MANAGER列上的非唯一性索引LODGING$MANAGER

   SELECT *
      FROM LODGING
      WHERE LODGING = &#39;ROSE HILL&#39;;
Copy after login

在内部,上述SQL将被分成两步执行:
首先,LODGING_PK索引将通过索引唯一扫描的方式被访问,获得相对应的ROWID;然后通过ROWID访问表的方式执行下一步检索
如果被检索返回的列包括在INDEX列中,ORACLE将不执行第二步的处理(通过ROWID访问表)
因为检索数据保存在索引中,单单访问索引就可以完全满足查询结果

2).索引范围查询(INDEX RANGE SCAN)
适用于两种情况:
1>.基于唯一性索引的一个范围的检索
2>.基于非唯一性索引的检索
例1

  SELECT LODGING
      FROM LODGING
      WHERE LODGING LIKE &#39;M%&#39;;
Copy after login

WHERE子句条件包括一系列值,ORACLE将通过索引范围查询的方式查询LODGING_PK
由于索引范围查询将返回一组值,它的效率就要比索引唯一扫描低一些

例2

SELECT LODGING
      FROM LODGING
      WHERE MANAGER = &#39;BILL GATES&#39;;
Copy after login

这个SQL的执行分两步,LODGINGMANAGER的索引范围查询(得到所有符合条件记录的ROWID),通过ROWID访问表得到LODGING列的值由于LODGINGMANAGER的索引范围查询(得到所有符合条件记录的ROWID),通过ROWID访问表得到LODGING列的值由于LODGINGMANAGER是一个非唯一性的索引,数据库不能对它执行索引唯一扫描

WHERE子句中,如果索引列所对应的值的第一个字符由通配符(WILDCARD)开始,索引将不被采用

    SELECT LODGING
    FROM LODGING
    WHERE MANAGER LIKE &#39;%HANMAN&#39;;
Copy after login

在这种情况下,ORACLE将使用全表扫描

14.避免在索引列上使用计算
WHERE子句中,如果索引列是函数的一部分,优化器将不使用索引而使用全表扫描
例如:
低效

   SELECT …
    FROM DEPT
    WHERE SAL * 12 > 25000;
Copy after login

高效

SELECT …
    FROM DEPT
    WHERE SAL > 25000/12;
Copy after login

请务必注意,检索中不要对索引列进行处理,如:TRIM,TO_DATE,类型转换等操作,破坏索引,使用全表扫描,影响SQL执行效率

15.避免在索引列上使用IS NULL和IS NOT NULL
避免在索引中使用任何可以为空的列,ORACLE将无法使用该索引
对于单列索引,如果列包含空值,索引中将不存在此记录;
对于复合索引,如果每个列都为空,索引中同样不存在此记录。如果至少有一个列不为空,则记录存在于索引中

如果唯一性索引建立在表的A列和B列上,并且表中存在一条记录的A,B值为(123,null),
ORACLE将不接受下一条具有相同A,B值(123,null)的记录插入
如果所有的索引列都为空,ORACLE将认为整个键值为空,而空不可能等于空,因此你可以插入1000条具有相同键值的记录,当然它们都是空!
因为空值不存在于索引列中,所以WHERE子句中对索引列进行空值比较将使ORACLE停用该索引

低效(索引失效)
SELECT …
FROM DEPARTMENT
WHERE DEPT_CODE IS NOT NULL

16.使用UNION-ALL和UNION
当SQL语句需要UNION两个查询结果集合时,这两个结果集合会以UNION-ALL的方式被合并,然后在输出最终结果前进行排序
如果用UNION ALL替代UNION,这样排序就不是必要了,效率就会因此得到提高

需要注意的是,UNION ALL将重复输出两个结果集合中相同记录,因此还是要从业务需求分析使用UNION ALL的可行性


关于索引下列经验请参考:
1).如果检索数据量超过30%的表中记录数,使用索引将没有显著的效率提高
2).在特定情况下,使用索引也许会比全表扫描慢,但这是同一个数量级上的差距;而通常情况下,使用索引比全表扫描要快几倍乃至几千倍!

其他具体内容请参考《ORACLE SQL性能优化系列》

17.使用PrepareStatement
在同一个方法中,当循环使用SQL文时,为了提高性能,
请使用PreparedStatement。注意,
仅限使用于少数的模块。
方法如下:

? PreparedStatement stmt   = conn.prepareStatement("select a from TABLE_A where b=? c=?");
 for(?? ){???? stmt.setInt(1, varB);     ???? stmt.setString(2, varC);     
 ?   ResultSet rst = stmt.executeQuery();
 }
Copy after login

以上就是Mysql系列 (八) 编写脚本的内容,更多相关内容请关注PHP中文网(m.sbmmt.com)!

Related labels:
source:php.cn
Statement of this Website
The content of this article is voluntarily contributed by netizens, and the copyright belongs to the original author. This site does not assume corresponding legal responsibility. If you find any content suspected of plagiarism or infringement, please contact admin@php.cn
Popular Tutorials
More>
Latest Downloads
More>
Web Effects
Website Source Code
Website Materials
Front End Template