finance | Simple Laravel app for tracking finances

The key points were:

1. When we scroll from n-1th to nth page,
   1. All indicators except nth need to be adjusted. The adjustment could be either of
      1. Shrink content+margin of all other indicators to 0 width. ( preferred )
      2. Move all indicators to left by calculated amount.
   2. The nth element should grow to occupy full width. The contents should also change opacity from 0 to 1.

With this points in mind, it should be easy to understand following changes in Paginator code.

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.

you can have log messages sent to the client:

PostgesOperator runs SQL. Your code is querying API, generate a CSV and loading it to the DB. You can not do that with PostgesOperator.

What you can do is to replace the usage of psycopg2 with PostgresHook. The hook is a wrapper around psycopg2 that expose you functions that you can interact with. This means that, for example, you don't need to handle how to connect to Postgres on your own. Simply define the connection in Admin -> Connections and reference the connection name in the hook:

You can consider splitting your case into separate ones and using array to collect them. Then you can use array_to_string to format:

1st solution: With your shown samples, with any awk, please try following. Simple explanation would be, using match function matching regex "[^"]*" to match from 1st occurrence of " to next occurrence of " and printing matched sub-string and next will skip all further statements. In case this condition is NOT TRUE then anyways usual way of printing 2nd field will work so printing $2 then.

In the predicate filter for the for-each:

No, this doesn't work. There is an open issue for this:

https://github.com/plotly/plotly.js/issues/4755

And it doesn't seem that this will come soon. You have to decide between your way and something like:

Consider the following changes.