Good Morning
-
This post did not contain any content.
No need. It's the best DB... Until you need something portable
-
This post did not contain any content.
first thing i'd ask it is how to pronounce SQL
-
first thing i'd ask it is how to pronounce SQL
Yup, and it's S-Q-L not sequel (
) -
Yup, and it's S-Q-L not sequel (
)squeal gang rise up!
-
No need. It's the best DB... Until you need something portable
What do you mean by "portable"?
-
No need. It's the best DB... Until you need something portable
My laptops runs postgres, but it is still pretty portable
-
This post did not contain any content.
This is literally me at every possible discussion regarding any other RDBMS.
My coworkers joked that I got paid for promoting Postgres.
Then we switched from Percona to Patroni and everyone agreed that... fuck yes, PostgreSQL is the best.
-
This post did not contain any content.wrote last edited by [email protected]
Things happen magically with docker. Container needs PostgreSQL? Expose the port, define a volume, username and password, connect service to that port, forget PostgreSQL’s existence until data corruption.
-
What do you mean by "portable"?
Just if you need to be able to take it with you.
-
Things happen magically with docker. Container needs PostgreSQL? Expose the port, define a volume, username and password, connect service to that port, forget PostgreSQL’s existence until data corruption.
forget PostgreSQL’s existence until data corruption.
Oh, so about 2 hours then LMAO
-
Things happen magically with docker. Container needs PostgreSQL? Expose the port, define a volume, username and password, connect service to that port, forget PostgreSQL’s existence until data corruption.
Not data corruption, but I replaced by mistake my .env file for authentik, containing the password for the postgresql database...
Cue a couple existential crisis for not having set up backups, thinking about nuking the whole installation, learning about postgresql, and finally managing to manually set another password.
Yeah, I feel several years older now...
-
This is literally me at every possible discussion regarding any other RDBMS.
My coworkers joked that I got paid for promoting Postgres.
Then we switched from Percona to Patroni and everyone agreed that... fuck yes, PostgreSQL is the best.
I have a colleague like that too, and then the other camp that loves MySQL.
Why do you like postgres
-
I have a colleague like that too, and then the other camp that loves MySQL.
Why do you like postgres
wrote last edited by [email protected]I made several lengthy presentations about many features, mainly those that are/were missing in MySQL.
In short, MySQL (has been) shit since its inception, with insane defaults and lacking SQL support.
After Oracle bought it, it got better, but it's catching up with stuff that Postgres has had for 20+ years (in some cases).
Also, fuck Oracle, it's a shit company.
Edit: if I had to pick the best features I can't live without, it would be 'returning', copy mode and arrays
-
Yup, and it's S-Q-L not sequel (
)wrote last edited by [email protected]?
I've been working on and with sql dbs since... 2011?
Earlier than that if you don't count professional work.
Always pronounced it Sequel, as has everyone I have worked with, at least of those who actually have some kind of software dev related role.
Its got two syllables.
Quicker and easier to say than three syllables.
-
This post did not contain any content.wrote last edited by [email protected]
What's that? Did you say you needed an RDBMS that can also handle JSON data? Well have I got good news for you!
-
This is literally me at every possible discussion regarding any other RDBMS.
My coworkers joked that I got paid for promoting Postgres.
Then we switched from Percona to Patroni and everyone agreed that... fuck yes, PostgreSQL is the best.
After having suffered with T SQL at MSFT for a number of years... yep, PostGres is almost always the best for almost any enterprise setup, despite what most other corpos seem to think.
Usually their reasons for not using it boil down to:
We would rather pay exorbitant licescing fees of some kind, forever, than rework a few APIs.
Those few APIs already having a fully compatible rewrite, done by me, working in test, prior to that meeting.
Gotta love corpo logic.
-
I made several lengthy presentations about many features, mainly those that are/were missing in MySQL.
In short, MySQL (has been) shit since its inception, with insane defaults and lacking SQL support.
After Oracle bought it, it got better, but it's catching up with stuff that Postgres has had for 20+ years (in some cases).
Also, fuck Oracle, it's a shit company.
Edit: if I had to pick the best features I can't live without, it would be 'returning', copy mode and arrays
wrote last edited by [email protected]Oracle:
Only the best in B2B marketing for our shit software.
EDIT:
hah ok, round two, more directly playing on the actual company name:
Oracle:
We tell you what you think you want to hear.
-
What's that? Did you say you needed an RDBMS that can also handle JSON data? Well have I got good news for you!
Mysql / Mari can handle it too! Just use BLOB
-
?
I've been working on and with sql dbs since... 2011?
Earlier than that if you don't count professional work.
Always pronounced it Sequel, as has everyone I have worked with, at least of those who actually have some kind of software dev related role.
Its got two syllables.
Quicker and easier to say than three syllables.
wrote last edited by [email protected]It isn't pronounceable as a word, it is an initialism because the letters that compromise it do not allow it to be pronounced as a word. Unlike something like NASA which is a full blown acronym because it can be pronounced
Do you say hetips for HTTPS?
The sequel thing didn't even start naturally, it picked up this sequel moniker because of some ancient trademark beef in the 70s between the original devs when it was named "Sequel" and some company (That isn't even in business anymore)
They renamed it SQL and out of protest against the company people continued to call it sequel even though it makes no sense and 50 damn years later here we are. Everybody involved with direct involvement is probably dead or longggg since retired. It wasn't termed because it was easier to say and it sure as hell wasn't termed because its proper.
If it was originally called SQL and the above never happened, I guarantee it would just be another DNS or HTTP and many many pointless debates about it would have never happened
Disclaimer, this doesn't apply to the MS product that is called sequel
-
It isn't pronounceable as a word, it is an initialism because the letters that compromise it do not allow it to be pronounced as a word. Unlike something like NASA which is a full blown acronym because it can be pronounced
Do you say hetips for HTTPS?
The sequel thing didn't even start naturally, it picked up this sequel moniker because of some ancient trademark beef in the 70s between the original devs when it was named "Sequel" and some company (That isn't even in business anymore)
They renamed it SQL and out of protest against the company people continued to call it sequel even though it makes no sense and 50 damn years later here we are. Everybody involved with direct involvement is probably dead or longggg since retired. It wasn't termed because it was easier to say and it sure as hell wasn't termed because its proper.
If it was originally called SQL and the above never happened, I guarantee it would just be another DNS or HTTP and many many pointless debates about it would have never happened
Disclaimer, this doesn't apply to the MS product that is called sequel
wrote last edited by [email protected]Do you say hetips for HTTPS?
No, because there isn't an easily pronouncable equivalent word that already exists in english.
The sequel thing didn't even start naturally, it picked up this sequel moniker because of some ancient trademark beef in the 70s between the original devs when it was named "Sequel" and some company (That isn't even in business anymore)
They renamed it SQL and out of protest against the company people continued to call it sequel even though it makes no sense and 50 damn years later here we are.
Yep, and I've worked with a bunch of old timers who were around when that happened, and picked up their pronunciation.
If it was originally called SQL and the above never happened, I guarantee it would just be another DNS or HTTP and many many pointless debates about it would have never happened.
I mean, I am not ... debating in the sense of 'my way is objectively correct and everyone ahould say it this way'.
Obviously I know what anyone means if they say S Q L and this does not bother me, I just am used to more commonly saying it as Sequel.
Though it is worth mentioning that... history did in fact happen, the original name was SEQUEL, for Structured English QUEry Language, and it had to be changed because a small aircraft company happened to already own the trademark for 'SEQUEL'.
Disclaimer, this doesn't apply to the MS product that is called sequel.
Ah, well perhaps that explains why I am so used to the Sequel pronunciation;
I used to work for MSFT, and a number of other Seattle area companies with siginifcant SQL database backends...
... and, given that Seattle was mainly known for Boeing before it was mainly known for Microsoft and Amazon and Starbucks, it does make sense that Seattle area old timers would get pissed over a rival, foreign aircraft company (Hawker Siddely, later merged into BAE) forcing a name change of the software they routinely use.
...
EDIT: So basically, it actually was originally an acroynm, and then got forced to become an initialism, and most the people I've worked with and learned from remember when it just was a pronouncable acronym.
