There is absolutely no reason at all that using a Model View Controller architecture should say anything about your persistence layer.
Model View Controller is an abstraction for managing code that generates things that are put on a screen. It says that you should have code that represents underlying data separate from code that represents different ways to show the data to the user and also separate from code that represents different ways for the user to specify how they would like to view or modify the data.
The Model portion of MVC should entirely encapsulate whether you are using a relational database or a fucking abacus to store your state. Obviously serializing and deserializing to an Abacus will negatively impact user experience, but theoretically it may be a more reliable data store than something named after a Czech writer famous for his portrayl of Hofbureaucralypse Now .
Basically they aren't going to impress your non-technical boss who is your boss for some inexplicable reason. Postgres has been able to function as key value store(which is basically what most NoSQL "engines" basically are, write once append only key value stores) for quite a long time now.
Writing code to query your key-value store is another story.
The rest of my admittedly very snarky, but arguably highly accurate commentary on various veins of discussion on this topic will be left in a time capsule below for future generations of people who actually have a legitimate interest in computer programming to discover after the Taliban are driven out of the computer industry.
Theoretically you can replace hiring smart programmers with magical artificial intelligence that reads your mind and then uses the computer to bend the world to your iron will, but if someone else could produce such a magical artificially intelligent database why would they share it with you? Perhaps they are an omnipotent omnipresent omnibenevolent entity that loves you just a little bit more because of your good looks and high intelligence?
Is this different from wanting to do a persistent query? Basically, since you have a programmable computer that you can program to talk to the database program, you write a computer program that periodically queries the database and then takes the action when the condition is met.
SQL is an implementation of a mathematical descriptive language for relationships. The whole point is that temporal logic like "wait until this happens, then do this" can be kept somewhat separate from logic describing the data you are tracking.
You have SQL that describes what it is you want to store, and particular questions you want to ask about what it is you want to store, and then the job of the database program is to figure out how to store the data safely and efficiently and answer your questions quickly. How you write the SQL that describes the way you want to store the data depends some on what kind of questions you want to ask, and this is what an actually skilled "Database Application Programmer" can figure out for you.
Some proprietary(and probably also Postgres) databases do provide support for the kind of thing you are asking to do here in the form of what are called "Stored Procedures" . Your average corporation accumulates an utter shitload of these stored procedures that various non-technical technical question askers in different departments don't tell each other about and they are often doing the same thing in different ways at different times. Then later they crash the database and break the application itself because there is insufficient technical oversight and communication at the actual decision making levels of the corporate bureaucracy.
Long story short, do all of this stuff in persistent queries done outside of the database and tracked in a shared medium like a wiki page, or even better a physical notebook routinely reviewed as part of management actually doing some managing.
https://en.wikipedia.org/wiki/Gantt_chart
This is an indication that you are not using a Model View Controller approach to building your database client. There are some python ORMs that were doing this automatically correctly a decade ago, but there are presuambly still several corporations with hundreds of millions of dollars using Enterprise Java Beans in 2021, also maybe some people with nuclear arsenals as well so you shouldn't consider yourself too behind the times.
POSIX programs were portable enough that Microsoft had to become POSIX compliant before being granted the operating system monopoly rent by the free market.
If we can effectively radiocarbon date these fragments and prove that they are the oldest, then will they be a sure guide on where to build our ark bunker to survive the maskocalypse foretold by Ezekstradamus? Do you guys have enough viagra for the repopulation program?
Is this part of the overall shift of computer interfaces to borderline useless tools which are more focused on interrogating and manipulating computer users than actually getting some kind of work done on the computer or is it a different kind of police state metastiziation?
It's because the internet is a perfect sterling engine, guaranteeing that all eyeballs will be monotized in an adiabatic flow. It is know as "The Permanent November of ImaginosVictory Law" to those of us that have been using the internet since Salman Rushdie invented email, which is one of the best exemplars of a good protocol since Google Wave.
Look you don't need to learn any algorithms because SQL will allow the computer to algorithm for you. SQL will guarantee ACID properties and also BASE properties. You are going to be rich. Simply buy Larry Ellison a boat and a bunch of ads on the back of the economist to socially prove to the finance world and the folks from Dave Graeber's actually very good essay that has not yet been followed up with the great american novel, and you are gonna be rich with no algorithms not done by the computer.
Don't worry, the computer is gonna take care of it, you won't need handwriting or food.
Here is a link to Mr. Graeber's high quality novel, "On the phenomenon of bullshit jobs": https://www.theatlantic.com/magazine/archive/2004/07/i-agree...
It'd generally appear that most people under 80 want to keep the college experience going. I still haven't read this, and I strongly suspect that if I were to skim it I'd be less likely to read it, but it generally seems to almost be a pretty good cold read of most generations of modern americans since the boomers as we age rather than just specifically the boomers. It is shorter than Neal Stephenson's version though, I think. https://www.powells.com/book/boomeritis-9781570628016
I am one hundred percent certain that both the locatelli grocer that has almost nothing I want to eat in it ever and has nothing but mexican standoff intersections with people walking around really slow, and the 'california' grocery that I really have to work hard at not just eating all the food in inside the store are both heavily planned, in terms of where exactly they are and all of the ridiculously excessive lighting and product placement inside of the stores. There is some vague pretension to a capital market and some vague notion that some of the great many retail businesses which are essentialy a second form of rent extraction may go out of business, but by and large it would seem extremely clear that there is a great deal of planning going on with information that business people are not supposed to have access to. Whether or not there is a viable alternative to said situation is a more complicated question, but there is no question that there is not some kind of innovation() support system where if you just figure out how to build a better mousetrap or run a better grocery store or sandwich shop, you will succeed and grow.
This ditch full of sims, without a car in it is yours. There are meny like it, but this one is yours. Even though it is in the middle of a perhaps overbuilt desert where it really ought to not be as ridiculous to have a car as it is say in the urban east coast, where you just need a car to escape the retail trap that has replaced sensible urbanity, this ditch is yours. Now crawl in and die already, god damn it. https://www.youtube.com/watch?v=NmrOQ4BizCE
this problem where published science is often wrong and you don't need to actually be an engineer that history will not record the name of is completely new, and also, airplanes are impossible and where actually invented by The Wright Bros, because they had the Wright stuff, right?
technics were invented in 1979 by cool dj hercuhito. here is incontrovertible proof from an internet primary source. not to mention that the elamites had their own alphabet that still survives after they fled conquest of constantinopole and headed to india where it's relaxed and safe. https://happymag.tv/technics-sl-1200/#:~:text=Technics%20as%....
poppycock! the most precious resource is zement and wheat. Sheep and brick can be had anywhere, and longest road and biggest army are both like kick me zigns, yay unto the septenth generatzion. you gotta spend all your time trying to figure out how to translate numbers from aramaic!
The re-entrancy complaint seems legit if actually well founded, although I'd think that it probably says somewhere in Flex/bison docs that the generated parsers expect only to be entered from a single C process. It sounds to me like they were using Flex/Bison generated parsers inside of some huge messy corporate web codebase, probably for webscraping or some kind of semi-structured data cleaning, and the code clammed up in some way.
Okay, so yes it is good to note that the GNU lexical generator toolkit does not generate unicode parsers and isn't re-entrant.
In general, parsing the same text from multiple threads seems like it could probably lead to more problems than just the fact that the parser generator toolkit for compiler writers isn't re-entrant, but that sounds more like a problem for the 'design' of these folk's client's codebases than anything else to me.
It would be nice to see a simple LL(1) lexer/parser generator in C that handles unicode and re-entrancy, although again, the latter one seems like something of a complex concept to me. Having the library generate parsers which are stable across multiple threads using generated parsers to parse different things at once seems like the only stable notion that I'd care about, so I will assume that is what this fellow is talking about.