Click here to Skip to main content
15,119,116 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: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 PinPopular
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 
GeneralRe: Imposing data type and length restrictions at the database level is stupid! - Part II Pin
Greg Utas27-Aug-21 15:21
mvaGreg 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 
5teveH wrote:
Including 'DB rules' in the code/UI. First of all, we already do this. I'm pretty sure most developers would define the MaxLength for a TextBox and use a Calendar Widget for date input. Secondly, validation logic should be developed as reusable code - which minimises the need for future developers to learn and re-code that logic.
Called SQL. The "S" standing for standard, and SQL92 still being supported.

5teveH wrote:
Performance. You are going to have to take my word for it, but I am 100% sure that with less disk, less CPU and less memory, I can deliver better performance than could be achieved using a traditional RDBMS.
I'll outpace you with a traditional RDBMS. I will take that bet for a banana (not allowed to bet more, but I owe over a trillion bananas now).

RDBMS is not optimized for speed, but rationality. It is an abstraction layer (what lots of us pretend to write) that abstracts away physicical storage. You no longer have to remember at what location a record begins, because the RDBMS handles that. The RDBMS was for years our Data Abstraction Layer (The DAL, which many a company asked money for, while doing one on one calls).

5teveH wrote:
Also, indexing data does not have a performance hit
"Almost" none; but there's a nice gain on retrieving the index. That's why indexes exist.

5teveH wrote:
And the greater the volume of data, the more confident I would be that performance would be better.
I'd be looking mostly at the capabilities of the dba.

Also; we restrict some things at db level because that's how it is done. Given a system, where some desktop and some phone app interact with a db, where do you put the restriction? Come on, we been doing this for 30 years Smile | :)

You don't need to use an RDMS, nor need to understand what BNF is. That's your choice Laugh | :laugh:
Bastard Programmer from Hell Suspicious | :suss:
"If you just follow the bacon Eddy, wherever it leads you, then you won't have to think about politics." -- Some Bell.

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 
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 

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.