The solution was to connect using the portal's "SQL Gateway Connections" with JDBC (Figure 1). After configuring this connection, it was possible to link the table within CACHÉ in the SQL area using "Wizards -> Link Table" (Figure 2). The table to be linked must have a sequence.
Figure 1..png)
Figure 2.png)
Thanks for the mention! I'm from Brazil. 😅
Very good!
Thank you! Another question that arose with this example is whether it's possible to apply a singleton pattern? Well, I understand that the discard was instantaneous.
Correct! I just want to know if I need to manage the disposal of this temporary or if the class itself does it for me.
Reading the class implementation, you can see that it does not write to memory, but in ^CacheStream, my concern is how this allocation is managed.
Thank you very much. I had already read the document, but I had the feeling that with a gateway/reverse proxy layer managing the requests in front of the portal's http (57772), it would be a good idea.
Returns successful connection even with incorrect data.
ERROR #6022: Gateway failed: DSN/User Connect.
Thank you very much for the explanation. And what would be the correct way to work on this separation between front-end and backend? An API written in Caché (cls backend) where there can be a front-end (nodeJS)?
The big question is this, I don't want to call a method, I want to render the entire CSP, an entire page.
I found! But now to call the page within CLS, just “write csp.package.page”?
Thank you very much for the clarification! Do you know where these CLS compiled through CSP are?
Do you understand that when I say CSP, I'm not referring to the %CSP.Page, but rather the .csp file?
Sorry, but I think it wasn't clear. I want to call CSP to render in CLS. In other words, I want to include the CSP method, but the entire CSP.