Can I use Postgres JSON column types with Loopback?

[Mark L]

I am starting a new project with a postgresql backend. I am evaluating loopback as a potential API server. I know that I will need to embed JSON objects into records and plan to use the native JSON and JSONB column types available in postgres. I noticed in the online docs that there is no reference to these 2 column types (here: http://docs.strongloop.com/display/public/LB/PostgreSQL+connector). 

Is it possible to create to use the column types? if so, how would I do that? If not, is this a planned change?

thanks,

Mark

[jmls]

I've asked this before - it would be useful to know ... 

[Mark L]

Yes, it would be useful...

[Omid S]

I'm also interested in this! 

[Líus Fontenelle Carneiro]

I'm using json and jsonb types with LB without problems. Postgres connector supports json type by serialising it using JSON.stringify when defined on model as a object or array of object. I'm also using with embedsMany relationship.

Best Regards,

Líus

[Omid S]

Based on the Type mapping tables in http://docs.strongloop.com/display/public/LB/PostgreSQL+connector, JSON is mapped to VARCHAR2 in Postgres. As you said, LB stringifies the objects and then stores them as text. But doing things this way, you would miss the benefits of native JSON column types in Postgres.

[Líus Fontenelle Carneiro]

Take a look directly on the source. Also, you can use jsonb and take advantage of more features, using the same string-serialization communication. In the end of day, this is the interface postgresql uses to handle json/jsonb types on queries.

[Omid S]

Thanks, looking at the source is the way to go!