Click here to Skip to main content
15,125,121 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
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 
I had my students develop the DB first; from that, one can easily build a web or desktop UI, independent from each other. Even other apps can access it, and when using a mainstream DB this decouples the data-layer from the rest.

5teveH wrote:
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.
The max length, as a simple example, does apply as much to the DB as the UI. Most generate their UI based on the restrictions provided by reflection.

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. 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.
You don't have to take mine; you gimme a model, I put it into 3BCNF and hand you the metrics. I do not ask for belief, I provide measurements.

Indexing data HAS a performance hit; the PC has to do something additional, how can you claim that the extra processing has no performance hit??
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
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 
GeneralRe: Thought of the Day Pin
Eddy Vluggen27-Aug-21 17:07
professionalEddy Vluggen27-Aug-21 17:07 
GeneralImposing data type and length restrictions at the database level is stupid! Pin
5teveH27-Aug-21 3:26
Member5teveH27-Aug-21 3:26 
GeneralRe: Imposing data type and length restrictions at the database level is stupid! PinPopular
Richard Deeming27-Aug-21 3:36
mveRichard Deeming27-Aug-21 3:36 
GeneralRe: Imposing data type and length restrictions at the database level is stupid! Pin
5teveH27-Aug-21 4:02
Member5teveH27-Aug-21 4:02 
GeneralRe: Imposing data type and length restrictions at the database level is stupid! Pin
obermd27-Aug-21 4:39
Memberobermd27-Aug-21 4:39 

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.