Shubham P

It's not different from juggler, but this port is default for postgresql so it might be the case that you're missing out those config in the datasource. Similar to Below...

Currently url strings are not respected in the sequelize extension. I've noted down the issue and it'll be fixed in the upcoming releases. Meanwhile you can use the specific keys...

Sure here you go: https://github.com/shubhamp-sf/loopback4-sequelize-transaction-example

> does this work for postgres jsonb columns as well? This seems to a postgres specific type, and current release of [@loopback/sequelize](https://www.npmjs.com/package/@loopback/sequelize) doesn't address this type. Will raise a PR...

@nivruth-naka The reason it works with default juggler without specifying property as `object` is that they to do type-casting hack (see the `::TEXT` in your query logs). Which stringifies the...

@yhrchan `loopback:sequelize:queries` is used for that purpose. It's mentioned in the debug string ref [here](https://www.npmjs.com/package/@loopback/sequelize#debug-strings-reference).

`@loopback/sequelize` is meant to be used with SQL dialects, this option being only supported by LoopBack in its memory and MongoDB connectors is not expected to work correctly. Please use...

Thanks for reporting this @KalleV, It seems sequelize relies on the actual db column type for the parsing. As I tried it with postgres and as long as the datatype...

Also when you say: > I tried adding a getter to all entity JSON properties... Where did you add that in your LoopBack app?

While it wouldn't be the best solution but I could only think of running manual queries using the [`execute` method](https://loopback.io/doc/en/lb4/apidocs.repository.defaultcrudrepository.execute.html#defaultcrudrepositoryexecute-method) on the repository to which you can pass your intended...