Unless the data model is either extremely clean or simple, users lacking deep context will struggle.
There are always tables for abstract concepts, code paths for legacy behavior, etc. Should we expect users to embed this internal business logic into their SQL queries? How do these users know when they need to change their embedded assumptions?
Unless the data model is either extremely clean or simple, users lacking deep context will struggle.
There are always tables for abstract concepts, code paths for legacy behavior, etc. Should we expect users to embed this internal business logic into their SQL queries? How do these users know when they need to change their embedded assumptions?