SVN branching and Mapping summary and database preliminary use

SVN uses a summary of commonly used such as checkout, Update,add will not say.

1. Create a branch -----New Branch directory, and import the project folder under the Branch folder. The branch does not affect the trunk trunk code and can be modified arbitrarily.

2. SVN shared mapping -----Create a new shared folder, check out the directory locally, select Show Properties in the shared folder in the Project browser, click New in the Url;property to fill in the Svn:externals, Value fill in your URL address link, followed by each link with the name of the directory you want to create. A file modification of a shared map affects the original file and is carefully modified and uploaded. 3. Putty is a very useful tool, directly in this tool using Linux and SVN shortcut keys can easily upload and manage their own files. SVN's common commands are actually so much, the link database summary is currently using the phpMyAdmin visualization tool to operate the database, the establishment of data tables need to implement the table of the field and primary key, or later modification is cumbersome. The current project is a team resource sharing site that needs to separate the data and code from the original code. 1. Create a new database, set up a data table, and fill in the data table with some data. 2. Modify part of PHP code, remove duplicate code, and output the same code in a loop. 3. Upload the resources, only need to fill in the database and copy files. 4. The database is more simple than I thought, and the data can be displayed in a perfect display with various operations on the database. It is also true that the release of a database and PHP. 5.php processing logic is sometimes troublesome, need to take into account the different levels, different headings and so on the relationship, pending further study.

SVN branching and Mapping summary and database preliminary use