Click here to Skip to main content
15,118,172 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:01
MemberSouthmountain28-Aug-21 11:01 
GeneralRe: I got a set of Microsoft Visual C++ 6.0 MFC library reference yesterday Pin
Shao Voon Wong27-Aug-21 19:43
mvaShao Voon Wong27-Aug-21 19:43 
GeneralRe: I got a set of Microsoft Visual C++ 6.0 MFC library reference yesterday Pin
Southmountain28-Aug-21 11:02
MemberSouthmountain28-Aug-21 11:02 
GeneralRe: I got a set of Microsoft Visual C++ 6.0 MFC library reference yesterday Pin
RickZeeland27-Aug-21 21:28
mveRickZeeland27-Aug-21 21:28 
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 
I thought this might stir up a few of the 'traditionalists' on here! Big Grin | :-D Rather than answer the many comments individually, I'll try to respond with this single post.

I had spent nearly 5 years developing COBOL applications before our boss told us about the Pick database that we were going to be moving to. To be honest, I couldn't see how it could possibly work and raised the same concerns that have been posted here today. There are a couple of common observations:

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.

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. Also, indexing data does not have a performance hit. And the greater the volume of data, the more confident I would be that performance would be better.
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 
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 

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.