My company is working on implementing a new HR application that will unify our existing HR processes. We've run into a bit of a sticking point, though; according to business rules, the EmployeeID and SupervisorID columns in the Employee table cannot be null. However, the application requires these columns to be nullable, and won't synchronize the columns while they're set to disallow null.
The proposed solution was to create a view where the schema appeared to allow null values in a column, while leaving the table alone to prevent them from being entered into the data. I'm not entirely convinced this is possible, and I haven't been able to find a way to do it. Is this possible? If not, what is the best way to handle this situation?