PG: Add dates to group aggregate

[dplewis]

Closes #4546

Let me know if more tests are needed.

I didn't really know how to write a test case for createdAt / updatedAt.

Also, I don't think it_only_db('mongo') works anymore.

[codecov]

Codecov Report

Merging #4549 into master will increase coverage by 0.02%.
The diff coverage is 94.73%.

@@            Coverage Diff             @@
##           master    #4549      +/-   ##
==========================================
+ Coverage   92.88%   92.91%   +0.02%     
==========================================
  Files         118      118              
  Lines        8457     8491      +34     
==========================================
+ Hits         7855     7889      +34     
  Misses        602      602

Impacted Files	Coverage Δ
src/Adapters/Storage/Mongo/MongoStorageAdapter.js	95.54% <83.33%> (-0.26%)	⬇️
...dapters/Storage/Postgres/PostgresStorageAdapter.js	97.21% <96.87%> (+0.07%)	⬆️
src/RestWrite.js	93.46% <0%> (+0.18%)	⬆️

---

Continue to review full report at Codecov.

Legend - Click here to learn more
Δ = absolute <relative> (impact), ø = not affected, ? = missing data
Powered by Codecov. Last update 10eafe9...0311c64. Read the comment docs.

[dplewis]

@flovilmart I just realized that Postgres doesn't store dates as UTC like mongo. Is that proper functionality?

[flovilmart]

ALL dates should be UTC (that’s the expected behavior). If it isn’t, then... that’s quite problematic :/

[dplewis]

For instance the objects I just created on postgres look like 2018-02-07 20:58:31.512-06. That -06 is Central Time

[flovilmart]

ouch yeah all dates should be UTC, but becaut they have the TZ info, not all is lost :)

[dplewis]

@flovilmart should we convert them to UTC or leave them be?

[dplewis]

@flovilmart The PG date storage aside how does this look?

[flovilmart]

Looking good!

[dplewis]

@flovilmart Thanks. What about the node vulnerability?