Muezz04/28/2022, 11:31 AM
will do what I am trying to do. But nothing appears in the console log. I also tried
and that works but the problem with that is that the function stops because of that exception. I found this stackoverflow question where the anser for this is:
I have gone through the settings and I cannot find any option to toggle this to
Check the value for "client_min_messages" in your session - it should be "NOTICE" or later to see notices.
Needle04/28/2022, 11:31 AM
command! We have solved your problem? Click the button below to archive it.
garyaustin04/28/2022, 12:46 PM
Needle04/28/2022, 12:46 PM
chipilov04/28/2022, 12:52 PM
without any config changes - it should show in the console but will NOT terminate your transaction
Muezz04/28/2022, 12:55 PM
and that is working.... The warning does not show up in the vs code debug console. It shows up in the postgres logs. Its better than nothing but it would have been more convenient if it was it vs code. For context,
shows up in the vs code debug console.
garyaustin04/28/2022, 1:17 PM
Muezz04/28/2022, 1:21 PM
is working though. IS there a way to make this appear inside vs code?
garyaustin04/28/2022, 1:34 PM
I've only ever used logs since only on hosted.
begin raise log 'TEST NOTICE'; end;
chipilov04/28/2022, 1:51 PM
Muezz04/28/2022, 2:07 PM
, that exception shows up inside my vs code debug console (and the function stops at that exception obviously) I am using
like you suggested so that the function completes. This warning only shows up in the postgres logs and it is a hassle to swtch between the SQL editor and the postgres logs. It would be convenient if these warnings showed up in the debug console like the exception. I hope that explains it.
chipilov04/28/2022, 2:12 PM
Muezz04/28/2022, 2:22 PM
. If I try to add a row with a column name that does not exist, I get smth like this
. At this point, I think it might just be a "feature" of the
"column" does not exist for relation "table_name"
chipilov04/28/2022, 2:37 PM
Muezz04/28/2022, 2:43 PM