honzo@4gl.UUCP (Honzo Svasek) (12/12/88)
From article <13235@ncoast.UUCP>, by allbery@ncoast.UUCP (Brandon S. Allbery): > As quoted from <560@4gl.UUCP> by honzo@4gl.UUCP (Honzo Svasek): > +--------------- > | From article <7222@charlie.OZ>, by root@charlie.OZ (Just call me SUPER): > | > ... request for audit trail facilities > | > | We have developed a utility that reads the Unify transactie log file > | and converts it into ASCII. As it also translates the 'field numbers' > | into field names, so it is not effected by database configurations. > | > | The only problem is that it is a commercial product and I cannot post it. > | A source licence is not that expensive though, please mail me for more info. > +--------------- > > May I suggest that this is rather trivial, So we thought, and that is exactly how this became a 'product'. It looks trivial, and the final source code is not that long. It took far to long to develop it though. One of the problems is that there is no easy way to find out what the next field is in a combined key. Unify in holland 'suggested' a routine for this, which worked only on new databases where the datadictionairy still is in order. As soon as someone added or deleted a field from a combined key, we got problems (core dumps). We finally ended up building a in core list of all fields in proper order from unify.db (the datadictionairy). In short: * to build this for a specific database is trivial. * to build this so that it works for any database is less easy. (but the info given above helps) honzo