Win a copy of Svelte and Sapper in Action this week in the JavaScript forum!
  • Post Reply Bookmark Topic Watch Topic
  • New Topic
programming forums Java Mobile Certification Databases Caching Books Engineering Micro Controllers OS Languages Paradigms IDEs Build Tools Frameworks Application Servers Open Source This Site Careers Other all forums
this forum made possible by our volunteer staff, including ...
  • Campbell Ritchie
  • Ron McLeod
  • Paul Clapham
  • Bear Bibeault
  • Junilu Lacar
  • Jeanne Boyarsky
  • Tim Cooke
  • Henry Wong
Saloon Keepers:
  • Tim Moores
  • Stephan van Hulst
  • Tim Holloway
  • salvin francis
  • Frits Walraven
  • Scott Selikoff
  • Piet Souris
  • Carey Brown

WMB ESQL and DB question

Posts: 1
  • Mark post as helpful
  • send pies
  • Quote
  • Report post to moderator
I am intentionally trying to insert on top of a previously entered
row to see how to handle exceptions

I sent the following command in ESQL

This works the first time, but the second time through the code
throughs an exception, and goes out the Failure terminal, where I
can see it in the Trace node

When I UN-CHECK the "Throuw exception on Database error", the flow
no longer throws an error, the output routes through the "Out" terminal

The first time through (on an empty table, successfull insert, the
trace shows:

On the second time through (bad insert cmd trying to overwrite a record),
it agains goes through the 'out' terminal, and the trace node shows:

In the first case I see a local env, but not the "Ret" I was trying to
write to

In the second case I do not see a local env of any sort

SInce both cases do not show a RET, I can not test ret inside of ESQL to
determine if the INSERT completed successfully

How can I do this ?
Don't get me started about those stupid light bulbs.
    Bookmark Topic Watch Topic
  • New Topic