November 21, 2013by Uri Margalit, Product Executive at dbMaestro
The Perforce motto is "Version Everything". But few people include database code in “everything”. That's why DBmaestro TeamWork™ and Perforce complement and complete each other.
Working with files and scripts is very different than working with a database. For example, a database is a centralized and shared resource that must be synchronized among the entire team. And database objects have their own syntax for creation and modification. These differences are quite important, and must be carefully considered.Posted In:
November 19, 2013by Russ Tremain, Engineer and Nellie LeMonier, User Experience Designer
November 15, 2013
by Natalie Estrada, Marketing Events Manager
Join us on Tuesday, November 19th for the latest DevTalk Webinar: "Avoid Git Bloat and Submodule Hell".
How do you avoid the burden of working with bloated, monolithic Git repositories and sidestep the complexity of submodules?Posted In:
November 14, 2013
by Bill Baffy, Software Engineer
Microsoft officially launched Visual Studio 2013 on November 13 and we are happy to be one of the Visual Studio Industry Partners to participate in the Sim-Ship of Visual Studio 2013 with our own Perforce Plugin for Visual Studio, P4VS 2013.3. This is the second Visual Studio Sim-Ship event we have participated in, having launched with the preview release of Visual Studio 2012 last year.Posted In:
November 14, 2013
by Matt Attaway, Open Source Community Manager (@p4mataway)Posted In:
November 12, 2013by Matt Attaway, Open Source Community Manager (@p4mataway)
I think 'p4 edit' is by far the most cursed Perforce command on Twitter. Folks coming from Subversion and Git are accustomed to an implicit checkout workflow, and being forced to ask the version control system for permission to change something is grating. Conveniently, Perforce supports implicit checkout as well! Let's take a look.
In Perforce your normal workflow for changing a file is: