There certainly are advantages. I've done things like code something I thought would work. Then go out to the sheep and try it out and then come back in and recode it. My golden rule of software development on LambTracker is that "No code survives first contact with the sheep." ditto for the first hardware designs. Sheep can be amazingly destructive to computers and lamb slime , snow and sheep nose prints can do very bad things to the code when they are pressing buttons because you set the tablet down to fish out a lamb and other sheep got curious.I would give an ear to work on something I was actually using myself.
Correct. Heck I can't even guarantee I will have cell phone coverage or electricity in some use cases so the mobile/handheld version has to be completely self contained.Normally you would host the db and hit it through an api, but are you keeping the sqllite on the phone to avoid the need for data connection?
Web app possible but a totally separate user and use cases. I loathe mixing languages so I'd rather just stick with Python.Why not build a webapp? These days with modern browser apis you can even design the thing to operate offline.
There are, they're called hierarchical databases but they have all sorts of other issues and problems and are much harder to normalize. One simple example is that it's very hard to dynamically extend a hierarchical databse structure without affecting everything else. In a nice relational db like SQLite or SQL if I suddenly decide I need a whole new function, tracking show class entries and winners for example. I can create a few more tables, link to the existing sheep tables using foreign keys and be off and running. None of it will affect existing code and all I have to do is add the new show class code. If those tables are empty they won't affect the functionality at all of other parts. My big database redesign I finished last year was mostly to take the LambTracker database much further along on the normalization path to make it even easier to expand as needed. That DID break code but mostly just my queries and that was/is relatively easy to fix. Had to join a lot more tables.I wonder if there aren't DB's that natively store as a tree so you don't have to reinvent that in sql.
LambTracker was on github originally and an older version is still there but once Microsoft bought it I bailed out for my current and updated stuff.I took a brief look at your gitlab (which why not github? just curious)