At the very least I’d try to clean up that fuzzy condition on behavior to anticipate any bad or inconsistent data entry.
WHERE UPPER(TRIM(behavior)) = ‘NICE’
Depending on the possible values in behavior, adding a wildcard or two might be useful but would need to know more about that field to be certain. Personally I’d rather see if there was a methodology using code values or existing indicators instead of a string, but that’s often just wishful thinking.
Edit: Also, why dafuq we doing a select all? What is this, intro to compsci? List out the values you need, ya heathen ;)
Honest question, which ones wouldn’t it work with? Most add a semicolon to the end automatically or have libraries and interfaces saved me a million times?
I’m not sure how including a final semicolon can protect against an injection attack. In fact, the “Bobby Tables” attack specifically adds in a semicolon, to be able to start a new command. If inputs are sanitized, or much better, passed as parameters rather than string concatenated, you should be fine - nothing can be injected, regardless of the semicolon. If you concatenate untrusted strings straight into your query, an injection can be crafted to take advantage, with or without a semicolon.
You need semicolons if it is a script with multiple commands to separate them. It is not needed for a single statement, like you would use in most language libraries.
The only people I know who actually call it ess queue ell are either too new to know the “sequel” pronunciation, or the type of person you generally smell before you see.
Here in Germany everyone I know pronounces the letters individually – as German letters that is, which means the Q is pronounced “coo” rather than “cue”. I don’t mind it, it’s not quite as clunky as in English.
I say ess cue ell for the sake of uniformity because it’s not Mysequel nor Postgresequel and the language changed from Sequel to the acronym SQL in the 70s so not really in the “too new” ballpark anymore.
I think those make sense as deviations. I’ve heard “my sequel” but you’re absolutely right about postgresql.
The name is kinda irrelevant like hard vs soft g in gif. People know what you mean when you say either.
But in that same vein, the creator of the “graphics interchange format” says the pronunciation is soft g, but basically everyone says hard g… So “official” pronunciation is kinda irrelevant.
I don’t judge anyone who uses whichever term they want, but I’ve just noticed the general trend in my smallish interaction bubble.
I’m neither, I refuse to pronounce acronyms if it doesn’t make sense to do so.
Same thing with ‘gooey’ for GUI, except I hate that even more because that straight up elicits feelings of disgust, I don’t want anything gooey anywhere near any electronics
The princess is saved, but all you can think about is rescuing another, with an entirely different plan. Which is just as well because you have no fucking idea how to explain the one you just wrote and executed.
You have rust, you decide to rewrite the C plan but the only library that supports it uses unsafe code so you go back and rewrite it. Wait what were you working on?
Git is a distributed version control system for software development^1.
Version control allows you to manage code versions and changes to code. You take snapshots, so to speak, of every change you make.
Distributed, in this context, means multiple developers can write code on each of their development computers and merge the changes, usually to a centralized git server.
GitHub runs a web-based git server at GitHub.com so teams can store their code in a central location on the internet.
Ok, technically, even though It’s often used for software source code, it can be used for any set of files and directories.
I don’t see anything you said that it isn’t quite right.
Porn is a distributed form of entertainment.
Porn allows you to get your rocks off. You take views, so to speak and do your thing.
Distributed, in this context, means multiple enjoyers can watch porn on each of their entertainment computers and share the videos, usually to a centralized porn server.
PornHub runs a web-based porn server at pornhub.com so viewers can store their porn in a central location on the internet.
It’s not, though. Git is a means of distributing content, not the content itself. The thing analogous to PornHub’s porn on GitHub is the source code in the repos hosted there, not Git itself.
Depends on to whom. If you’re explaining to your grandma, a small child, a co-worker, or a student under your tutelage, you probably don’t want an explanation that relies on reference to a porn site.
And if you’re explaining to a novice developer or to an IT person who sometimes might have to work with Git, they deserve an explanation that leaves them with a basic understanding (or at least the names) of the kinds of things Git and GitHub are (VCSes and SCM forges, respectively), not just an inkling that GitHub is not unique in being ‘a place to host (some?) Git, whatever that is’.
So… if you don’t mind that it suggests ‘GitHub is for uploading Git(s)’, that line is an okay way to teach ‘the difference between Git and GitHub’ to non-technical, non-elderly adults who don’t really need to know what Git is (and don’t work with you or study under you).
That’s an explanation of pretty damn narrow usefulness, to put it generously.
I agree that porn is a nsfw way to explain something in a lot of scenarios but I disagree about people needing to know at least the names of a technology from an explanation.
Most people don’t need to know or care about the names to understand or use them. Knowing the names after I learnt the commands did not give me greater insight into how the tool works.
If they are just being introduced to git and github then they are likely new to programming and have much more important things to care about like learning their first programming language or understanding how their teams project actually works.
A place to host gits is a perfectly good explanation for anyone who is new to it.
Git is a DVCS. GitHub is a place where DVCS repositories are hosted. There are many other places where DVCS repositories can be hosted, but GitHub is the most famous one… Porn is a type of content. PornHub is a place where porn is hosted. There are many other places where porn can be hosted, but PornHub is the most famous one. It’s a pretty good analogy.
Sure… and you could pass around porn on thumb drives. But, having a central website where you can browse public repos and clone the interesting ones is a pretty key part of Open Source / Free Software development.
How many people use Github for discovery though? I usually find interesting projects through a search engine, through word of mouth, through posts on here, etc. at which point it doesn’t really matter where the repo is hosted. A lot of the useful projects I use aren’t even on Github.
As far as I know, Gitea is current working on federation support, which will be great. It’d be like Lemmy where you can browse repos, submit issues, etc from one instance even if the repo is hosted at a different one. Git was really designed for a model like that, not for a centralized one.
How many people use Pornhub for discovery though? I usually find interesting content through a search engine, through word of mouth, through posts on here, etc. at which point it doesn’t really matter where the porn is hosted. A lot of the useful content I use aren’t even on Pornhub.
Seriously though, I agree with you, githubs value to open source is not it’s discover-ability. Personally I think its value comes from the stability, as much as I’m an advocate for self-hosting I know from the amount of dead links on the internet that we could have lost a lot of projects or at least they would move about as hosts went down.
I quite like the idea of federated gitea, although technically there is already a federated platform for porn if you count Lemmy and/or mastadon.
Git is a program your computer runs to have a single folder have source control. It does all the hashing and commit chaining that you’re used to, branches, that sort of thing.
But if you want it to be on more than one computer, you need to do this complicated “Bare” repository setup on a server computer to do the “git push” stuff you’re used to.
Most people, being too lazy to learn bare repositories and the general sysadmin necessary to host a git server themselves, instead just use Microsoft’s Github which is a web interface for the server use of git the program.
Microsoft then proceeded with their classic mantra of “Embrace, Extend, Extinguish” and started slapping on more and more features that are incompatible with any other git hosting service: actions, CI, their web VSCode instances, etc. That’s all in GitHub too. But it’s all just web interface for git the open source program, at the end of the day.
I like shitting on M$FT as much as the next bloke but if you believe Github started being evil when Microsoft entered the picture then your memory is pretty awful.
From it’s inception github pushed proprietary tagging and issue numbers that have no meaning outside their platform and a difficult export process to trap projects - especially commercial ones - on their platform.
I was being diplomatic because I was uncertain how people felt about the issue and PR tracking, considering how Bitbucket and GitLab replicate it. Felt simpler to focus on the since-M$ft egregious steps.
I remember moving a project from github to gitlab years ago (before MS) and the process to move all the non-git data from github was just as easy as moving the git repo itself. Thanks to gitlab’s efforts perhaps, but I didn’t expect github to have made it difficult for them based on the experience I ended up having.
Just a few comments on this. Most people aren’t “lazy”, they just understand that the effort to run a bare repository is greater than basically any other solution. Also your incompatible features list implies that other git repo sites (gitlab, codecommit, bitbucket, etc) don’t have their own form of proprietary stuff that you have to learn. In fact the newest version of gitlab actually changes their web ide into vscode web, because of the obvious, it is much better than their old ide.
Only C and Lisp actually completed the initial task of getting the princess free, and Author clearly favors C over the drooling and homeless lisp hacker. Also, turns out, C greatest weakness helped to save not only the princess but everything she ever possessed! How convenient!
programmer_humor
Hot
This magazine is from a federated server and may be incomplete. Browse more on the original instance.