loopback postgresql connector neq with null check issue

[gopalakrishnan-subramani]

We have an critical issue, we could not filter not null values neq using postgresql with loopback find methods.

This is show stopper for our entire application, we need soft delete features based on timestamp data.
{ deleted_at: {neq: null} }

Any workaround possible without hitting DB performance? or if you could show a possible place to fix the bug, we will fix and contribute back with pull request.

[bajtos]

Hi @gopalakrishnan-subramani, thank you for reporting the issue. Please create a small application reproducing the issue, see https://loopback.io/doc/en/contrib/Reporting-issues.html#loopback-4x-bugs.

I suspect the problem may be in the connector, here is the relevant code:

• SQLConnector.prototype.buildSelect
• PostgreSQL.prototype.escapeValue
• PostgreSQL.prototype._buildWhere

[bajtos]

I see that we already have an issue reported in our postgresql connector, let's move the discussion there.

loopbackio/loopback-connector-postgresql#340