It lets multiple developers, programers and project managers all work on the source code for a project with minimal stepping on each others toes. The workflow we use is as follows.
We keep the a Git repository in the cloud, typically in Bitbucket.
Each developer then keeps a local copy of the repository. The developer can then create a new feature branch to work on an issue. More than one developer can work on a project at a time, and multiple branches can co-exist at the same time. This allows for more concurrent effort to be deployed.
(This image from the git-guide linked below)
Typically then the QA will pull that feature branch to a test server and test the new feature/issue for completeness/quality.
If they are happy with the quality of work, they can then merge that feature/issue branch into the master branch.
Then on the production server we can pull the master branch and deploy it in production.
We link the bitbucket repository with JIRA and Confluence so that features, issues and bugs can be more easily tracked and discussed.
For more information on how to use git, see the git-guide.
Using SugarCRM (this client is using Enterprise 6.5.15) and we want the last two hundred items in the tracker table. The problem is that the `tracker`.`date_modified` field is in UTC time, not the local time zone, which is +10:00.
The solution is to use the CONVERT_TZ MySQL command, as shown in the example below. It will convert between timezones for you.
SELECT `users`.`user_name` AS "User",
`tracker`.`module_name` AS "Module",
`tracker`.`item_summary` AS "Summary",
`tracker`.`action` AS "Action",
CONVERT_TZ(`tracker`.`date_modified`,'+00:00','+10:00') AS "Modified"
INNER JOIN `tracker` ON
`users`.`id` = `tracker`.`user_id`
WHERE `tracker`.`deleted` = 0
ORDER BY `tracker`.`date_modified` DESC
Spent some time today working with DATEDIFF, DATE_ADD and all kinds of horrid looking code before realising that to do a MySQL query to get records where the date is in the past or the next x months all I need is the following.
WHERE t_position_cstm.review_date_c <= DATE_ADD(DATE(now()), INTERVAL 6MONTH)
You can change the 6 to whatever appropriate value you have, and you can change MONTH to a variety of other values, for me the two I used today was MONTH and DAY.
I’m using this on a SugarCRM MySQL database with a custom module of Position (the actual table name is t_position).