Excellent Database table design...

Yikes!

LOL

hoho, they're really begging for inconsistent data

Fd (Foolish design)

It is a bug. They didn't add Moonroof columns

Sometimes I dont understand people..

++Yes: True
++No: False
--Yes: False
--No: True

Is it a schrödingers cat problem if both are set to yes?

Golden

I worked at a company where the fields were just a letter and a number 'a42' sure, it'll go fine in o'l 'a42' 😱

Hahaha 😅

Oh good gods....

Triggered

Quantum computing.

Haha, two columns for a single boolean.

Maybe they used to be accountants? Double entry bookkeeping

I have worked with automotive data and car dealer APIs for 7 years... but this one pretty much stands out :) and believe me, I have seen my fair share of BS stuff

Where are the fields "Sunroof" (with value "False") and "SunroofYesOrNo" (with value "No")? It's incomplete...

Uhm maybe its "Big Data" ^^

The irony is just a few weeks back we were taught to do this in college, our teacher claimed this is what a binary data set is 😂

This may be because S/he implicitly one-hot encoded the data, It's a common problem when you prepare your training set.. Converting categorical features into numerical/boolean features. S/he have manually replaced the labels into numerical features. MAYBE
😅

maybe they hate using 'else'

Maybe if both are set to True it means the sunroof is optional? If that was the case, it would only be an issue of stupid labeling rather than stupid Database design.

WTF?! JUST NO! D: seems like a future painful rework :s