Memento | Memento is a simple note taking app for Android

Again, you're not drawing correctly. You are trying to render using a JPanel, cliente, that is never added to the GUI, and you're trying to use a Graphics object that is extracted from this unrendered component, making the Graphics object thus obtained short-lived and unstable.

Instead, do all drawing in the paintComponent method. You can use a BufferedImage and draw that in paintComponent if desired, especially if you want images with objects that show different colors, or you can use your List (here a LinkedList, but ArrayList will work) and draw in paintComponent. For instance, something simple like:

The reason why the program didn't work was because the functions were running in order. It worked when I ran the functions simultaneously using 'threading'.

I'm assuming that your input data is just several strings. You can convert them to Path objects which offer rich interactions:

I tried to look up serialization with ngrx entity collection service base but I didn't find anything letting me know how I could take some action on the data properties upon loading from http call

You can follow this steps in order to perform action on data properties upon api call:

app.component.ts:

in case anyone else hits this problem adding core-js before babel stand alone fixes it in ie11.

ManagedIdentityCredential only works in Azure. You could change it to use DefaultAzureCredential instead. It attempts multiple methods, including Managed Identity and Visual Studio authentication. So it'll work locally as well. Of course your user account does need to have the needed RBAC role as well.

According to this document you need to add freesolo

In order for autocomplete to work , you also need to pass on the InputProps down to custom textfield. So I would change your renderInput function like this:

There isn't a real generic answer to this question. It all depends on the structure of your database, span of the transactions across entities, distributed transactions, how much time/transactions are allowed to pass before your can revert the change, etc.

Memento Pattern is one of the possible approaches, however it needs to be modified due to the nature of the relational databases as follows:

1. You need to have transaction log table/list that will hold the information of the entities and attributes (tables and columns) that ware affected by the transaction with their primary key, the old and new values (values before the transaction had occurred, and values after the transaction) as well as datetimestamp. This is same with the command (memento) pattern.
2. Next you need a mechanism to identify the non-explicit updates that ware triggered by the stored procedures in the database as a consequence of the transaction. This is important, since a change in a table can trigger changes in other tables which ware not explicitly captured by the command.
3. Mechanism for rollback will need to determine if the transaction is eligible for roll-back by building a list of subsequent transactions on the same entities and determine if this transaction is eligible for roll-back, or some subsequent transaction would need to be rolled-back as well before this transaction can be rolled-back.
4. In case of a roll-back is allowed after longer period of time, or a near-realtime consumption of the data, there should also be a list of transaction observers, processes that need to be informed that the transaction is no longer valid since they already read the new data and took a decision based on it. Example would be a process generating a cumulative report. When transaction is rolled-back, the rollback will invalidate the report, so the report needs to be generated again.

For a short term roll-back, mainly used for distributed transactions, you can check the Microservices Saga Pattern, and use it as a starting point to build your solution.

Another approach is to keep incremental updates or also known as history tables. Where each update of the row will be an insert in the history table with new version. Similar to previous case, you need to decide how far back you can go in the history when you try to rollback the committed transaction.

Finally, when you work with business data such as invoice, inventory, etc. you also need to check what are the regulations related with the cancelation of committed transactions. As example, in the accounting systems, it's not allowed to delete data, rather a new row with the compensation is added (ex. removing product from shipment list will not delete the product, but add a row with -quantity to cancel the effect of the original row and keep audit track of the change at the same time.