Type 'double precision' mapped to String

[ataft]

On line 144, dataType "real" and "double precision" are changed to "float", but buildPropertyType has no case for "FLOAT":
https://github.com/strongloop/loopback-connector-postgresql/blob/master/lib/discovery.js#L144

This change simply adds a case statement for 'FLOAT'

[slnode]

Can one of the admins verify this patch? To accept patch and trigger a build add comment ".ok\W+to\W+test."

[dhmlau]

@ataft, thanks for your contribution.
Could you please fix the commit message? Looks like line 3 of the commit message is longer than 72 characters.

**************************************************
**
**  Linting commit logs
**
**  1 problems found:
**    962fa56 - Type 'double precision' is mapped to String: line 3 longer than 72 characters.
**
**************************************************

Also, could you please add some test cases as well? Thanks.

[ataft]

@dhmlau I'm not so great with git and don't know how to change the commit message.

With regards to the tests, also not my strong suit, but the current "postgresql.discover.test.js" should cover this the 'double precision' type:
https://github.com/strongloop/loopback-connector-postgresql/blob/master/test/postgresql.discover.test.js#L113

[dhmlau]

@ataft, see if you can follow this instruction to change the commit message https://help.github.com/articles/changing-a-commit-message/. If not, don't worry, I can modify it for you.

Thanks for pointing out the existing test.

[dhmlau]

Let's get the commit message fixed so that CI can run successfully first. Thanks!

[ataft]

Please modify, I cannot figure it out since I just made the change in the browser (not using command line). Can you also modify my other PR #347? Thanks!

[dhmlau]

@slnode test please

[dhmlau]

The change looks reasonable to me. But would like to get at least another review.

[b-admike]

LGTM

[dhmlau]

Thanks @ataft. Your PR has landed. Thanks for the contribution!