Save same class structure in two sets of tables with NHibernate?

The two sets of tables are there to support two different states (published/awaiting approval (or the like)).

The two sets of tables are there to support two different states (published/awaiting approval (or the like)). If possible, I recommend making this state explicit in your model, and save everything in the same table. The client of the published objects will then somehow have to exclude the non-published objects.

Yeah that's one option, but then as you say have to filter by this whenever you do a select for the published data. Also each object would have to know it's status, unless all queries link back to the parent entity that knows if it is published or just edit data. For editing this would be the case, but if I just wanted to pull out Customers or Notes I wouldn't necessarily want to join to Order.

For the moment going to try binary serializing the edit data. Although this has issues of it's own. – Ian Oct 16 '09 at 15:50.

I cant really gove you an answer,but what I can give you is a way to a solution, that is you have to find the anglde that you relate to or peaks your interest. A good paper is one that people get drawn into because it reaches them ln some way.As for me WW11 to me, I think of the holocaust and the effect it had on the survivors, their families and those who stood by and did nothing until it was too late.