Update PostgresStorageAdapter.js

[vitaly-t]

Improving use of the await/async notation in relation to pg-promise, and in general.

[codecov]

Codecov Report

Merging #6275 into master will increase coverage by <.01%.
The diff coverage is 80%.

@@            Coverage Diff             @@
##           master    #6275      +/-   ##
==========================================
+ Coverage   93.81%   93.82%   +<.01%     
==========================================
  Files         169      169              
  Lines       11564    11564              
==========================================
+ Hits        10849    10850       +1     
+ Misses        715      714       -1

Impacted Files	Coverage Δ
...dapters/Storage/Postgres/PostgresStorageAdapter.js	97.01% <80%> (ø)	⬆️
src/RestWrite.js	93.42% <0%> (-0.33%)	⬇️
src/Adapters/Storage/Mongo/MongoStorageAdapter.js	93.44% <0%> (+0.7%)	⬆️

---

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 4f1d3b0...7d6adfd. Read the comment docs.

[dplewis]

@vitaly-t Thanks for the PR, it looks good to me. Is there a reason why this is an improvement? I always use async / await like this.

[vitaly-t]

@dplewis The initial idea was to improve methods such as createClass and createTable, to stop returning things that are not needed, but I could not finish in the end, because the dependent tests are incorrect, and would need to be updated also.

Methods such as those, resolve with null or undefined, representing nothing. The tests should verify that the method resolves, and not test what it returns, or expect undefined. Then the methods can be corrected. There is no point testing the first methods returning [null, null, null] from a batch, or just null in other cases (from result of method .one).

[dplewis]

Oh I see, you are right they shouldn't return.

The adapter should conform to the StorageAdapter

[dplewis]

LGTM!