Looking through the blog as well as the Jam.py v7 documentation to get started with V7, I came across some interesting things:
- The V7 has been changed much more than I expected.
- The work now looks like a classic go web app with an included http script, only that script is not visible here, as in go, but it functions in the same way.
- RPC is only a consequence of the overall handling of requests and responses.
- Introducing fixed (on_api) and dynamic (on_ext) routing brings Jam.py closer to REST API waters.
- Now it is a very complex framework, which knows how to route, which knows how to call remote functions via the rpc interface, which knows how to communicate with REST API routed parts of the application, which knows how to do validation in a serious way, which is event-driven, which is data-driven and which has a solved internationalization, at least in half of the general meaning of the word.
What was my task?
To verify that all of this works in one standard environment without errors or with easily fixable errors.
In order to check it, it is necessary to check:
- work with small lookups (relation 1:n, where n > 0, usually up to 10)
- work with large lookups (relation 1:n, where n >> 0)
- work with small n:m relations (the so-called inline)
- work with large n:m relations (with assoc table)
Behavior of systems without foreign keys
- One of the advantages is the easy restructuring of the db
- System behavior with and without the "deleted" field
- Behavior of child records
"Virtual tables" behavior as one of the possible solutions for working with stored procedures.
Radosav