Gregory's Server@rrwo @szescstopni @Threadbane @blacklight There are many cases where NoSQL is only sensible choice. NoSQL has been around longer than SQL, nearly as long as Voyagers which don't use SQL either. There is a narrow range of cases where SQL is appropriate usually some business context at a certain limited scale. It has nothing to do with your resume. Not only this just because business apps and web apps are shitty does not mean kids in critical systems engineering are not killing it, they are.
|
18 comments
 @blacklight @rrwo @szescstopni @Threadbane NoSQL is even older than that. As for SQL sadly I have used most of them. SQL has its place, like anything. The key difference between the way say some webshit like facebook is built and Voyager comes down to the way the project is managed. There is no move fast and break things with a nuclear power plant. It's the old school SSADM with endless reams of docs, specs, ERDs and dusty old process Very high detail, labor intense, expensive software cycle.  @nf3xn @blacklight @rrwo @szescstopni @Threadbane I agree. In the old days I worked coding assembly language for medical instruments that would be in the field for decades. Certainly compared to today a lot of care was put into 64k. But as you say that's more about problem domain than technology (I have also spun up MySQL instances for really trivial things, like organizing files at home.) @nf3xn @blacklight @rrwo @szescstopni @Threadbane Ha! I remember one of the last times I used a SQL database for a trivial purpose .. garage temperature recording. I guess it cracked me up at that point how ridiculous it was to have a full unix(ish) stack and SQL to run a thermometer. As an added bonus this pi zero and the one in the kitchen communicated, doing data replication for fault tolerance. It's still funny to me.  @John @nf3xn @blacklight @rrwo @szescstopni @Threadbane ah yes, for my first temperature measurement I also used a Zero W with a Postgres db and a pythons script writing to it every minute. Now I use an RPi Pico sending data by MQTT to a server which ingests those messages to InfluxDb, which is read by Grafana. @stfn @nf3xn @blacklight @rrwo @szescstopni @Threadbane That sounds cool and much more modern. My boards answered my questions, which were basically about how the temperature cycle looked in my house with no heat or cooling (not present anyway) running. Before running the test I had not really internalized that the coldest part of the night is not midnight ;-)  @blacklight @John @stfn @nf3xn @rrwo @szescstopni @Threadbane sqlite has triggers. @John this is a very interesting project: do you have some links or details about hardware and software that you have used to achieve it? @seblm I think my method was a little idiosyncratic. If I remember correctly I used a DHT11 temperature sensor, and wrote c code to take a reading and insert it in the database. I just set that c code up as a cron job. I used shell scripts and cron jobs to do my data replication, database dumps and rsyncs if I remember correctly. There are lots of ways to skin the cat, and if you search for raspberry pi DHT11 (or DHT22) there will be lots of examples.  @John @nf3xn @blacklight @rrwo @szescstopni @Threadbane @nf3xn @blacklight @rrwo @szescstopni Ouch, yeah. I came in at the start of the floppy era. Before that we actually shipped clinical instruments with ROM boards only, and updates were shipping a new board. Part of our department was still doing that. There was this big consciousness that, even with floppies, you never knew they would reach their destination, and out of date software might live for many many years.  I wasn't taught SQL in my comp sci database courses in 1981, just hierarchical databases, because "relational is cool theory but not practical for commercial apps". Ironically, I never used a hierarchical database but 5 years later, got a contract writing parsers for IMS, COBOL and PL/1 to generate SQL DDL and migrate data to DB2. I was part of an OO Centre of Competence in the mid-1990s. I wasn't writing much code by then, mostly design and team leader. But I remember a developer telling another that I was an expert in C++, even though I had only read the manual (which I still have). I think it was because I knew how to write compilers and read the book critically through that lens, so was figuring out the point of each feature as I read about it. @EricLawton @blacklight @nf3xn @rrwo @szescstopni @Threadbane much the same in my database class in 1989, I think. SEQUEL got a passing mention in the textbook, but that was about it. :) I know relational theory was discussed, but I long ago chucked the proper terms in favor of SELECT, FROM, WHERE, etc. :)  @nf3xn @rrwo @szescstopni @Threadbane @blacklight @nf3xn @rrwo @szescstopni @blacklight But do they have to use an IBM 029 card punch, carry trays of punch cards to the big mainframe on base to compile (ready the next day)!? Do they have to toggle switches on the PDP-11 front panel to load the jmp instruction and then the address of the ISR that loads in the bootstrap loader from paper tape that then reads the hard disk for the big boot? Do they have to code without an onscreen editor!? HUH!? HUH!? HUH!? |
@nf3xn @rrwo @szescstopni @Threadbane SQL has been around since Codd's original paper in 1974, so it's a couple of years older than Voyager :)
As an SQL and relational algebra geek there's nothing worse I could hear than "SQL has only a limited range of applications". Both relational and non-relational databases can be amazing tools for storing data - when used properly for the right use case.