Daily Target of 0 differentiated from an unset Target, unset targets should be NULL

I've seen a fair amount of questions about tracking nutrients where you have an affirmed target of 0 as well as a Max Threshold of whatever.

This comes up with Alcohol, Trans Fat, Sat. Fats, Added Sugars, Oxalates, Cholesterol, etcetera. So it is a big issue for many users.

From the official replies I've seen, it seems that Cronometer is not making a distinction between situations where a target has affirmatively been set to 0, and where a target has not been set and should therefore be NULL.

Recognizing the distinction between 0 and Null is pretty common in database work. Following this database practice would seem to solve a lot of the problems and problematic workarounds, for tracking nutrients that definitely have a maximum threshold, but in no way have a minimum daily intake.

Many thanks to everybody on the Cronometer team. This is an amazing help.
Best regards,
Kim

Welcome!

It looks like you're new here. Sign in or register to get started.

Welcome!

It looks like you're new here. Sign in or register to get started.