Work with V7

49 views
Skip to first unread message

r rad

unread,
Jun 7, 2026, 5:55:20 PMJun 7
to Jam.py Users Mailing List
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
Message has been deleted

r rad

unread,
Jun 8, 2026, 6:46:53 AMJun 8
to Jam.py Users Mailing List
I'm sorry, but I didn't feel or was informed by anyone that I was so necessary. 

In any case, the other maintainer, and my countryman, and not because of that, is an excellent developer, 
and he keeps Jam.py in his little finger, I would say. 

The only thing I don't understand is his rare appearance. Well, he would say that he is very busy with his duties, 
but then another maintainer is chosen, to whom Jam.py means a lot and who is willing to spend his time without
compensation. 

If you think I'm offering myself, that's not the case, because I don't satisfy the basic thesis - I don't know V7 almost 
at all, and besides, I want to enjoy my retirement without obligations and deadlines. 

Which doesn't mean I don't want to help. 

Greetings, Radosav

On Monday, 8 June 2026 at 04:34:49 UTC+2 Dean D. Babic wrote:
Simple, your task is two years late.

The task about two years ago was to get more people using Jam.
Reply all
Reply to author
Forward
0 new messages