transaction | Embedded database for accounts transactions | Database library

That error is clear. you do not have sufficient funds. This is how you are getting the account information:

It is not the same. It decides when errors are thrown.

You should always use SET XACT_ABORT ON, because it is more consistent; almost always, an error will stop execution and throw an error. Else, half things throw errors and the other half continue execution.

There is a great article about this whole subject on Erland Sommarskog's site, and if you go at this point you will see a table which describes this strange behaviour. In conclusion, I recommend the General Pattern for Error Handling, as it is very well documented as well as provide you the opportunity to tweak it according to its own documentation.

Having the same issue while working on the same course as you, maybe try using node 10 and redeploy everything.

Let me know if that works.

So i found a way to do this, it requires some cleanup and error handling but allows for a custom token transaction via @solana/wallet-adapter.

CTEs can break this down a little easier. In the code below, the payment_streak CTE is the key bit; the start_of_streak field is first marking rows that count as the start of a streak, and then taking the maximum over all previous rows (to find the start of this streak).

The last SELECT is only comparing these two dates, computing how many months are between them (excluding June/July), and then finding the best streak per customer.

Payment args in EGLD are auto-filled from the call value you've already specified in the transaction, so you do not need to pass them as argument.

Therefore, your call data in this case would be myEndpoint@aa, without the payment arg.

As a side note, if this would've been an endpoint accepting another token than EGLD, you would've had to specify the token and amount in the data field, like: ESDTNFTTransfer@TokenIdentifier_in_hex@TokenNonce_in_hex@TokenValue_in_hex@Contract_address_in_hex@myEndpoint_in_hex@aa.

The ESDTNFTTransfer function sends any type of ESDT token, with or without nonce. If the token doesn't have a nonce (fungible), you can either pass 00 as nonce or leave the nonce space empty, like @TokenName_in_hex@@TokenValue_in_hex. Mind the fact that in order to use this function, you would have to compose a transaction with the destination set as yourself. The actual address of the destination would be contained in the data field in place ofContract_address_in_hex, making it a parameter of the ESDTNFTTransfer function.

If the endpoint accepted two tokens for example, then you could've used MultiESDTNFTTransfer@Contract_address_in_hex@02@Token1Identifier_in_hex@Token1Nonce_in_hex@Token1Value_in_hex@Token2Identifier_in_hex@Token2Nonce_in_hex@Token2Value_in_hex@myEndpoint_in_hex.

And yeah, you can always check the Elrond docs on ESDT Tokens / NFT Tokens for more details.

You use str(0.05 * 10**18) to get the string for the value.

However, this actually outputs the value in scientific notation, which isn't what the blockchain expects.

You are better off avoiding serializable isolation level. The way the serializable guarantee is provided is often deadlock prone.

If you can't alter your stored procs to use more targeted locking hints that guarantee the results you require at a lesser isolation level then you can prevent this particular deadlock scenario shown by ensuring that all locks are taken out on ServiceChange first before any are taken out on ServiceChangeParameter.

One way of doing this would be to introduce a table variable in spGetManageServicesRequest and materialize the results of

Your title says you are using Java 9. With Activiti 6 you will have to use JDK 1.8 (Java 8).