v3.2.0

am jumping am jumping!
db Query and new config structure

- coming up new db and sync `engines`
honest typo
config is where it all happens
dbengine2 is looking good --- i think
test ground
am just committing this just to make sure my streak continues

#amDesperate
dbEngine2 GET sync in place

- dbEngine2 GET sync looks good and `generic`
- upsetting a couple of `control` keys before execution saves us a heap
of trouble
- no timezone --- all is in one, i think...
- latest moment 2.7.0
query good!

- query is looking good
- same deal as get --- looking for the timestamp difference n' stuff
dbEngine2

- this is the time we're waiting for...proofread this sob and move on to
syncEngine2
introducting syncMode

introducing syncMode, this rootScope variable is used to `force` the db
engine to fetch from the local db

if syncMode is true, dbEngine will fetch from the local db even if
there's a connection with the server

PS:
syncMode by default is set to false, only when called from the
syncEngine it should be set to true and set back to false after we're
done with it
syncMode introduced

- using syncmode we can *forcefully* tell dbEngine to fetch from the
local db
syncEngine2 looks good

- only proof reading remains!
API url
sync cleanup
cleand up

- am taking that next big step
more!
cooler message
am human

- forgot to *link* up with WebSQL config
syncEngine