Click here to Skip to main content
15,122,487 members

Welcome to the Lounge

   

For discussing anything related to a software developer's life but is not for programming questions. Got a programming question?

The Lounge is rated Safe For Work. If you're about to post something inappropriate for a shared office environment, then don't post it. No ads, no abuse, and no programming questions. Trolling, (political, climate, religious or whatever) will result in your account being removed.

 
GeneralRe: Imposing data type and length restrictions at the database level is stupid! - Part II Pin
Eddy Vluggen27-Aug-21 17:00
professionalEddy Vluggen27-Aug-21 17:00 
GeneralRe: Imposing data type and length restrictions at the database level is stupid! - Part II Pin
obermd27-Aug-21 18:17
Memberobermd27-Aug-21 18:17 
GeneralRe: Imposing data type and length restrictions at the database level is stupid! - Part II Pin
5teveH28-Aug-21 4:16
Member5teveH28-Aug-21 4:16 
GeneralRe: Imposing data type and length restrictions at the database level is stupid! - Part II Pin
RickZeeland27-Aug-21 21:49
mveRickZeeland27-Aug-21 21:49 
GeneralRe: Imposing data type and length restrictions at the database level is stupid! - Part II Pin
5teveH28-Aug-21 4:10
Member5teveH28-Aug-21 4:10 
GeneralRe: Imposing data type and length restrictions at the database level is stupid! - Part II Pin
RickZeeland28-Aug-21 4:17
mveRickZeeland28-Aug-21 4:17 
GeneralRe: Imposing data type and length restrictions at the database level is stupid! - Part II Pin
5teveH28-Aug-21 4:58
Member5teveH28-Aug-21 4:58 
GeneralRe: Imposing data type and length restrictions at the database level is stupid! - Part II Pin
Sander Rossel28-Aug-21 0:56
professionalSander Rossel28-Aug-21 0:56 
5teveH wrote:
I thought this might stir up a few of the 'traditionalists' on here! Big Grin | :-D
I love this.
I think my post was one of the few that wasn't upvoted because I partially agreed with you Laugh | :laugh:

I'd never heard of Pick.
Doesn't seem like something I'd want to use.
The Wiki page has some interesting facts about it though...
"Pick was originally implemented as the Generalized Information Retrieval Language System (GIRLS) on an IBM System/360 in 1965" (who said developers don't get the girls!? Laugh | :laugh: )
"It is named after one of its developers, Richard A. (Dick) Pick." (seriously, Dick Pick!? Laugh | :laugh: )

On a serious note, Pick seems to pre-date SQL and before SQL the only thing you had was NoSQL.
Then after some thirty years of everything SQL, NoSQL gained popularity again.
NoSQL didn't come back because SQL was so good at everything and speed and scalability were two of the main bottlenecks.
Updating a SQL database schema is also generally a hassle, with large tables taking hours to update.
No such thing in schemaless databases, just update the software and you're good to go!
It's fun that we're all using "schemaless" REST services and no one bats an eye, but do the same for a database and everyone loses their minds.
That said, SQL adapted and NewSQL databases now combine some of the speed and flexibility of NoSQL with the safety of SQL.
I've found people are very defensive of SQL and very afraid of NoSQL (to the point of people becoming insulting and personal when someone, mostly me, mentions NoSQL).
People don't like to get out of their comfort zones and they'll fight to stay there Sigh | :sigh:

GeneralRe: Imposing data type and length restrictions at the database level is stupid! - Part II Pin
5teveH28-Aug-21 4:02
Member5teveH28-Aug-21 4:02 
GeneralRe: Imposing data type and length restrictions at the database level is stupid! - Part II Pin
Member 798912228-Aug-21 5:54
MemberMember 798912228-Aug-21 5:54 
GeneralRe: Imposing data type and length restrictions at the database level is stupid! - Part II Pin
Gerry Schmitz28-Aug-21 5:47
mveGerry Schmitz28-Aug-21 5:47 
GeneralRe: Imposing data type and length restrictions at the database level is stupid! - Part II Pin
englebart28-Aug-21 6:04
professionalenglebart28-Aug-21 6:04 
GeneralRe: Imposing data type and length restrictions at the database level is stupid! - Part II Pin
Eddy Vluggen28-Aug-21 9:56
professionalEddy Vluggen28-Aug-21 9:56 
GeneralRe: Imposing data type and length restrictions at the database level is stupid! - Part II Pin
5teveH29-Aug-21 21:56
Member5teveH29-Aug-21 21:56 
GeneralRe: Imposing data type and length restrictions at the database level is stupid! - Part II Pin
Eddy Vluggen30-Aug-21 16:42
professionalEddy Vluggen30-Aug-21 16:42 
GeneralRe: Imposing data type and length restrictions at the database level is stupid! - Part II Pin
Asday30-Aug-21 7:56
MemberAsday30-Aug-21 7:56 
GeneralRe: Imposing data type and length restrictions at the database level is stupid! - Part II Pin
jschell5-Sep-21 9:31
Memberjschell5-Sep-21 9:31 
GeneralThought of the Day Pin
OriginalGriff27-Aug-21 5:09
mveOriginalGriff27-Aug-21 5:09 
GeneralRe: Thought of the Day Pin
Mike Hankey27-Aug-21 5:59
professionalMike Hankey27-Aug-21 5:59 
GeneralRe: Thought of the Day Pin
Kschuler27-Aug-21 6:01
MemberKschuler27-Aug-21 6:01 
GeneralRe: Thought of the Day Pin
User 991608027-Aug-21 6:10
professionalUser 991608027-Aug-21 6:10 
GeneralRe: Thought of the Day Pin
jeron127-Aug-21 6:26
Memberjeron127-Aug-21 6:26 
GeneralRe: Thought of the Day Pin
Slacker00727-Aug-21 7:02
professionalSlacker00727-Aug-21 7:02 
GeneralRe: Thought of the Day Pin
Member 1532961327-Aug-21 7:24
MemberMember 1532961327-Aug-21 7:24 
GeneralRe: Thought of the Day Pin
DRHuff27-Aug-21 9:04
MemberDRHuff27-Aug-21 9:04 

General General    News News    Suggestion Suggestion    Question Question    Bug Bug    Answer Answer    Joke Joke    Praise Praise    Rant Rant    Admin Admin   

Use Ctrl+Left/Right to switch messages, Ctrl+Up/Down to switch threads, Ctrl+Shift+Left/Right to switch pages.