updater | Autoupdate binaries with Docker Notary and TUF

Advice/opinion

A database is for persistent storage of numbers and text.

An app is for computing and deciding things.

That is, the complex business logic you describe may be more appropriately encoded in Java (or other app language). Meanwhile, the breakpoints, etc for interest rates should be stored in the database.

Phrased differently: "Business logic" belongs in the app, not the database. (There is, of course, a gray lines between them. For example, SQL is excellent at summing up all the data in a table; so, I would do that in SQL, not Java.)

Decimal

Banks have picky rules that may not be the same as what DECIMAL or DOUBLE provide -- in Java or MySQL or _any other computer language. Be careful of the rules that may be required. In particular, DECIMAL(10, 4) is unlikely to be adequate in your application. On the other hand, apy DECIMAL(4, 2) may be adequate if that is what is presented to the customer. But, again, beware of rounding rules when generating that number. You may be forced to enter that number manually.

Be aware of the difference in rounding characteristics between DECIMAL and DOUBLE.

Answer

If you choose to implement an algorithm in the database, then see CREATE STORED PROCEDURE and CREATE FUNCTION.

Stored Procs can be used to encapsulate a set of SQL statements. It can receive and send strings and numbers, but not arrays. It is capable of reading tables (hence "arrays" of a sort.)

Functions can be called anywhere an expression can occur. It can receive some numbers/strings and produce one number or string.

Array

I'm not clear on what is needed, but I envision a table of a few rows or a few dozen rows with each row saying "for values up to $xxx, use y.yy% interest rate".

Stored Procs have "cursors" and "loops" but they are clumsy; the app language is likely to have better code.

new_version: ^0.3.0

new_version

New Version Plugin 🎉 # A Flutter plugin that makes it possible to:

Check if a user has the most recent version of your app installed. Show the user an alert with a link to the appropriate app store page.

Update object, inside of the message field, has the from field which is a User Telegram object containing the user's ID.

Once you have the user's ID, you can use the sendMessage method in order to reply him easily.

To conclude, instead of:

The moveTo method belongs to Camera object. ref.

I don't have the environment setuped to test. The code will look something like this:

Add the code to shut down the main app in to the updater. You know the process name so it should be fairly easy. This way you can also check that the updater actually starts running before the main app is shut down.

Code below is borrowed from this answer: https://stackoverflow.com/a/49245781/3279876 and I haven't tested it my self.

I can't tell you why you're seeing the behaviour you're observing. I can reproduce the error with SBT 1.3.13. When I use SBT 1.4.9 the custom task only runs once as you would expect.

Remove the spaces in the Connection property Username-Password-Authentication. Since it's the name of the Auth0 Database, which cannot contain spaces.

Another issue can be that the password is not strong enough, check the internal server error of Auth0 in de log and the password rules for your application.

Uncaught TypeError: Cannot read properties of undefined (reading 'string')

I believe the issue is where you are declaring your proptypes for StarRating.

TL;DR: You can pass conflicts=proceed to the update_by_query API if you want it to continue working even when hitting conflicts.

More details: The update_by_query page explains:

When you submit an update by query request, Elasticsearch gets a snapshot of the data stream or index when it begins processing the request and updates matching documents using internal versioning. When the versions match, the document is updated and the version number is incremented. If a document changes between the time that the snapshot is taken and the update operation is processed, it results in a version conflict and the operation fails. You can opt to count version conflicts instead of halting and returning by setting conflicts to proceed.

So basically, your update and update_by_query are trying to update the same documents, conflicting with each other. Using conflicts=proceed makes that operation say "oh well, I'll just continue to update the other docs".