Ok i did undertsand why it is doing like this i guess. this is the correct way of doing things. esp in the case if I am trying to retreieve a revision within the audit table it has to look in the audit table of the refered entity as well as that will also be part of the history..
yeah It makes sense,
Sorry for the late reply, but yes, things need to be audited. If you have existing data, you can "bootstrap" them by copying all data to the _AUD tables, adding revtype ADD, revision 1 and creating one entry in the rev entity.