New answers tagged

0

Dropping the column would remove all values from all rows of the table. If the change always to all rows that could be in the database this might be acceptable. If the model tables are for a base set of records, it is possible the DROP COLUMN would drop data from other records. The DDL (Data Definition Language): ALTER table DROP COLUMN re_added_column; ...


0

IMHO, no. Sometimes, a commit is just too large to be explained in enough detail in the message, for it not to require exploring the 'diff'. However, I would change the why to a what (described in broad strokes). This way, a developer can get a good idea of what was affected by that commit, and only have to explore the diff if they really want to go into ...


1

You seem to be trying to solve a problem created by mixing content and style together. Webpages (good ones anyway) solve this problem by using cascading style sheets to decide style while content is kept in html (or xml, or json, or...). By separating these two concerns they can change independent of each other. Indirection can also help. If the string ...


17

"Local", "centralized" and "distributed" are synonymous with "here", "there" and "both", respectively. The only thing that is neither here nor there, is nowhere. So I guess the only other type of version control is "Non-Existent VCS" which, unfortunately, is still quite prevalent in the industry.


2

Local VCS, Centralized VCS and Distributed VCS are various ways to set up version control infrastructure. Git specifically is a distributed version control system where every client contains an entire history of the project. Team Foundation Server and Subversion are examples of a centralized version control system, where a central server contains the ...



Top 50 recent answers are included