Good Morning
-
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.
-
No need. It's the best DB... Until you need something portable
I'm running it on a raspberry pi, how much more portable could you need?
-
first thing i'd ask it is how to pronounce SQL
That's easy, but PostgreSQL is pronounced Postgres-Q-L.
-
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.
I just view it as a pointless 50 year old squabble, it's current name is SQL to me so S-Q-L it is, ig I didn't have "old timers" to corrupt me during the formative years of my career though so maybe that's why.
Regardless, my real beef in this is if someone makes hiring/firing/promotion decisions based on that. Like a fun office debate about it, cool, it's whatever. Choosing not to hire or promote someone over something so petty is asinine IMO
-
Mysql / Mari can handle it too! Just use BLOB
pg can actually query into json fields!
-
I just view it as a pointless 50 year old squabble, it's current name is SQL to me so S-Q-L it is, ig I didn't have "old timers" to corrupt me during the formative years of my career though so maybe that's why.
Regardless, my real beef in this is if someone makes hiring/firing/promotion decisions based on that. Like a fun office debate about it, cool, it's whatever. Choosing not to hire or promote someone over something so petty is asinine IMO
wrote last edited by [email protected]I just view it as a pointless 50 year old squabble, it's current name is SQL to me so S-Q-L it is, ig I didn't have "old timers" to corrupt me during the formative years of my career though so maybe that's why.
I mean hey, there ya go!
Regardless, my real beef in this is if someone makes hiring/firing/promotion decisions based on that. Like a fun office debate about it, cool, it's whatever. Choosing not to hire or promote someone over something so petty is asinine IMO
Oh I completely, 1 million percent agree, and that kind of bullshit was a huge factor in why I left MSFT and went to work for other places, rofl!
Way, waaaaay too many coked up MBAs with tiny small dick syndrome, who compensate by developing a god complex and constantly shaming people over not knowing all the latest buzzwords, which they often themselves just literally heard for the first time in their previous meeting.
-
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
As a complete newb to Postgres, I LOVE arrays.
Postgres feels like all of the benefits of a database and a document store.
-
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 used to agree, but recently tried out Clickhouse for high ingestion rate time series data in the financial sector and I’m super impressed by it. Postgres was struggling and we migrated.
This isn’t to say that it’s better overall by any means, but simply that I did actually find a better tool at a certain limit.
-
first thing i'd ask it is how to pronounce SQL
15 years ago I called it S-Q-L and then I was told that it's wrong and it's "Sequel", and they kept calling it Sequel in college so for the past 10 years I've called it Sequel, My-Sequel, Sequel-lite, Postgres, transact-sequel, etc. Now y'all are telling me it's not Sequel
-
forget PostgreSQL’s existence until data corruption.
Oh, so about 2 hours then LMAO
...ok, I'm morbidly curious. How did you manage to do that?
-
pg can actually query into json fields!
And you can add indexes on those JSON fields too!
-
first thing i'd ask it is how to pronounce SQL
wrote last edited by [email protected]Sequel with external collaborators.
Squeal with the homies.
-
Just if you need to be able to take it with you.
The whole point of a database is that you leave it where it is though
-
The whole point of a database is that you leave it where it is though
I think the OP is trying to talk about SQLite, so yeah, he could really be talking about carrying it on his phone.
But it's just such a weird word to use there that I can't really be sure.
-
The whole point of a database is that you leave it where it is though
Ohhhh right, that's the base part right?
-
I think the OP is trying to talk about SQLite, so yeah, he could really be talking about carrying it on his phone.
But it's just such a weird word to use there that I can't really be sure.
Or portable like on a USB stick that you can put in any computer instead of installed on a single system.
-
This post did not contain any content.
As a (data) scientist I am not super familiar with most databases, but duckdb is great for what I need it for.
-
I used to agree, but recently tried out Clickhouse for high ingestion rate time series data in the financial sector and I’m super impressed by it. Postgres was struggling and we migrated.
This isn’t to say that it’s better overall by any means, but simply that I did actually find a better tool at a certain limit.
If you can, share your experience!
I also do finance, so if there is anything more to explore, I'm here to listen and learn.
-
As a complete newb to Postgres, I LOVE arrays.
Postgres feels like all of the benefits of a database and a document store.
Yeah, that was the goal.
First make it feature-complete document-oriented database, then make if peroformant.
And you can feel the benefits in every step of the way. Things just work, features actually complement each other... and there's always a way to make any crazy idea stick.
-
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.
I have to admit though, I've never admined the Oracle DB, but I did talk a lot with people who did.
I remember over 10 years ago discussing transactional DDLs as I heard Oracle does it, too, just to listen to 5 minute lecture about how it's nowhere near as simple.
