agreed.
But Switching on/off Journal by process every time you write ^EVENT seems rather uncomfortable.

though it's compact as you know exactly when you need it,
 

depending on the actual long time use you may of course also    
use ^mtemp.EVENT  (in IRISTEMP)    
instead of a journaled ^EVENT in your actual namespace to escape transactions

• LOCK would be indeed the best equivalent to Isolation Modes
• just IRISTEMP doesn't react to COMMIT or ROLLBACK  (there is no related Journal)
• so instead of writing to your ^EVENT Global you may write to a PPG ^||EVENT acting as your  private temp
• after Commit or Rollback you decide if you MERGE  ^||EVENT to public ^EVENT or not.
• from your description, I assume you do it anyhow  

did you check TIMESTAMPDIFF ??

there is an example in OEX 
https://openexchange.intersystems.com/package/db-migration-using-SQLgateway

It's for PostgreSQL but the difference is only the specific jdbc used

Congratulations to all the winners!
It was a great event and highly useful to follow.

PLEASE!
if you have a different question then PLEASE don't change the original content
this breaks the total information flow.
Existing replies will look like nonsense!

Thanks @Raj Singh  great input  !
I recently struggled with LOAD DATA and finally dropped it in favor
of an old-fashioned COS import for 2 reasons:

• installation of Java was a prerequisite (might be mentioned somewhere, not identified) not a default in community containers
• quality of data was POOR to express it politely e.g:
  • column expected to be DOUBLE   >> content was 
    • number 
    • $ number
    • some text
    • NULL
• date with any sick non -SQL format
• just empty lines by wild running \n

so some exception handling after validation would have been a great feature in my case
to filter out sick records.

The sick CSV is available on GitHub
 
 

By SQL priniciple:     
any straight name is meant to be a COLUMN of the actual table.  eg. Embeddings
but an external HostVariable is designated by an initial : (colon)  e.g.  : new_embedding_str or :params

This seems to be the deeper cause your problem

in addition I'd suggest to add  print(new_embedding_str)  to verify its format. (one of my problems.

Furthermore, take a closer look to this example:
iris-vector-search/blob/main/demo/sql_demo.ipynb

Sounds promising:
in my COS example, I had to use pure String parameters like  "0.54456,0.6987646,0.I123" 
happened by accident, more for reading and debugging

I use a similar setup in my example in OEX ,
Especially with TO_VECTOR() I ran into problems if I didn't add the explicit
type and size of the vector.  e.g. TO_VECTOR("..........",,DOUBLE,384)
as model all-MiniLM-L6-v2  produces exactly that type and size:

Don't ask for why. I just used the proposed example

- Thank you @Andrew Wardly:
Your observation is pretty correct. It derives from a late Latin dialect spoken
around Locarno (today Switzerland) around 1600. Eventually starting with a very sharp S.
So the mental link to "Semper Fidelis" is pretty close and matches well.  

set x="1,4,6,8,9,12"
while x>0 {write +x,! set x=$piece(x,",",2,*) }

x only !

set X="1,4,6,8,9,12" for i=1:1:$L(X,",") set Y=$p(X,",",i) write Y,!