Loopback-next: Debug mode like in Loopback3 (DEBUG=loopback:datasource node .)

Created on 1 Jun 2019  路  10Comments  路  Source: strongloop/loopback-next

Description / Steps to reproduce / Feature proposal

The are any command to show what sql are executed?

Like in LB3:
DEBUG=loopback:datasource node .

question

Most helpful comment

try loopback:connector:*

All 10 comments

Juggler is the same as lb3.

If i use this command I do not see the sql:
DEBUG=loopback:datasource node .

try loopback:connector:*

@pookdeveloper, is this issue good to close? Thanks.

Hello @dhmlau @raymondfeng i try:
set DEBUG=loopback:connector:* npm start
or
set DEBUG=loopback:connector:* node .
and not work.

image

What happen ? Thanks

I try this
set DEBUG=loopback:connector:<my-connector-name>
but the same, it dosen't work

Any solution ? Thanks

@pookdeveloper, sorry that I don't have access to a Windows machine for now. On mac, that's what I did, and I think it should be the same for Windows. Could you please try it out?

DEBUG=loopback:connector:* npm start

Then I got something like:

Server is running at http://[::1]:3000
Try http://[::1]:3000/ping
  loopback:connector:postgresql Settings {"name":"ds","connector":"postgresql","url":"","host":"localhost","port":5432,"user":"xxx","password":"xxx","database":"testdb","debug":false} +0ms
  loopback:connector:postgresql SQL: SELECT "id","name" FROM "public"."dianatest" ORDER BY "id" +22ms
  loopback:connector:postgresql:data {"command":"SELECT","rowCount":0,"oid":null,"rows":[],"fields":[{"name":"id","tableID":24577,"columnID":1,"dataTypeID":25,"dataTypeSize":-1,"dataTypeModifier":-1,"format":"text"},{"name":"name","tableID":24577,"columnID":2,"dataTypeID":25,"dataTypeSize":-1,"dataTypeModifier":-1,"format":"text"}],"_parsers":[null,null],"_types":{"_types":{"arrayParser":{}},"text":{},"binary":{}},"RowCtor":null,"rowAsArray":false} +0ms

Thanks it works using:
DEBUG=loopback:connector:* npm start
image

I using now a mac

Thanks!

When you are using Windows and VSCode, you are using PowerShell so you need follow PS commands for environment vars https://docs.microsoft.com/en-us/powershell/module/microsoft.powershell.core/about/about_environment_variables?view=powershell-7

Was this page helpful?
0 / 5 - 0 ratings