Click here to Skip to main content
15,166,724 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: I got a set of Microsoft Visual C++ 6.0 MFC library reference yesterday Pin
Southmountain28-Aug-21 11:05
MemberSouthmountain28-Aug-21 11:05 
GeneralRe: I got a set of Microsoft Visual C++ 6.0 MFC library reference yesterday Pin
Rick York27-Aug-21 22:00
mveRick York27-Aug-21 22:00 
GeneralRe: I got a set of Microsoft Visual C++ 6.0 MFC library reference yesterday Pin
Southmountain28-Aug-21 11:06
MemberSouthmountain28-Aug-21 11:06 
GeneralImposing data type and length restrictions at the database level is stupid! - Part II Pin
5teveH27-Aug-21 8:05
Member5teveH27-Aug-21 8:05 
GeneralRe: Imposing data type and length restrictions at the database level is stupid! - Part II Pin
PIEBALDconsult27-Aug-21 8:19
professionalPIEBALDconsult27-Aug-21 8:19 
GeneralRe: Imposing data type and length restrictions at the database level is stupid! - Part II Pin
Randor 27-Aug-21 10:03
professional Randor 27-Aug-21 10:03 
GeneralRe: Imposing data type and length restrictions at the database level is stupid! - Part II Pin
David O'Neil27-Aug-21 10:09
professionalDavid O'Neil27-Aug-21 10:09 
RantRe: Imposing data type and length restrictions at the database level is stupid! - Part II PinPopular
Mycroft Holmes27-Aug-21 13:24
professionalMycroft Holmes27-Aug-21 13:24 
I have worked with an organisation who catered to the vagaries of traders, who made them lots of money, the front end software allowed basically anything to be entered into a value field (many of them). The software sorted out how to deal with the garbage that was entered, the DB had no rules or definitions everything was a string (except dates, even they were not that stupid). So you would see 5.2m 300k 1.12b 3.3mill etc. Every time the system broke because some idjit entered new garbage the software company made $1000s to adjust the UI.

I was tasked with generating reports from such rubbish. Your premise sucks big grey donkey balls! Am I bitter and twisted after dealing with such garbage in, dammed right I am. I designed data structures that worked, were fast, efficient and anyone could use the data without knowing any arcane rules living in the UI.
Never underestimate the power of human stupidity -
RAH
I'm old. I know stuff - JSOP

GeneralRe: Imposing data type and length restrictions at the database level is stupid! - Part II Pin
Greg Utas27-Aug-21 15:21
mveGreg Utas27-Aug-21 15:21 
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 
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 

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.