Click here to Skip to main content
15,173,031 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: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 
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 
Hmmmm,

Many years ago I was tasked with writing a VDR[^] for the IMO[^] and the Det Norske Veritas[^] and most of the signals were coming in at around 10Hz and I was required to log them in 'real time'. Back then the IEEE defined 'real time' as 1.5 times the signal rate.

For performance reasons I chose SQLlite[^] and a single BLOB[^] in the voyage data recorder.

Worked great for a few years. Then we had two incidents, "incidents" in the maritime industry usually means millions of dollars of damage or greater. No problem I thought, let's pull the black box and see what happened!

The BLOB fields did not match the C++ structs we were using for logging the signals, something was off. After a lengthy forensics analysis we realized that the office in Norway was using a different build and the Norwegian C++ structs did not match with the U.S. code. They were somehow compiling the vessel navigation software with different signal headers.

The 'BLOB' field did not give us any evidence of what was different and we wasted an enormous amount of time investigating this. Also... these millions of dollars of damage were disputed between multiple nation states. In the maritime industry these judgements are decided by arbitrators rather than an actual legal system.

[cheers]

modified 28-Aug-21 5:48am.

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

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.