start new:
tmux
start new with session name:
tmux new -s myname
| DELIMITER $$ | |
| DROP PROCEDURE IF EXISTS add_email_address_column_to_customers_table $$ | |
| -- Create the stored procedure to perform the migration | |
| CREATE PROCEDURE add_email_address_column_to_customers_table() | |
| BEGIN | |
| -- Add the email_address column to the customers table, if it doesn't already exist | 
It seems that it does not matter what timezone is on the server as long as you have the time set right for the current timezone, know the timezone of the datetime columns that you store, and are aware of the issues with daylight savings time.
On the other hand if you have control of the timezones of the servers you work with then you can have everything set to UTC internally and never worry about timezones and DST.
Here are some notes I collected of how to work with timezones as a form of cheatsheet for myself and others which might influence what timezone the person will choose for his/her server and how he/she will store date and time.
| # Auto detect text files and perform LF normalization | |
| * text=auto | |
| # Documents | |
| *.doc diff=astextplain | |
| *.DOC diff=astextplain | |
| *.docx diff=astextplain | |
| *.DOCX diff=astextplain | |
| *.dot diff=astextplain | |
| *.DOT diff=astextplain | 
using mocha/chai/sinon for node.js unit-tests? check out my utility: mocha-stirrer to easily reuse test components and mock require dependencies