I have a database with a report table. This table represents report data, and has constraints. Now the application is used by firemen, and they might have to run off and put
Go with the simple solution: create a View which is just a union of the two tables (which should be fairly straight forward as they I assume they both have (almost) identical structures) and then run searches on that as the source if they want to include both.
I wouldn't actually merge the complete and draft data at any point: the potential for error and accidental use of unvalidated data seems huge.
You wouldn't be working on an interface for the IRS in the UK at the moment, would you? If not, sounds like DK have gone for a similar (in principle) solution to this problem (I used to work for a UK Fire and Rescue Service).