home bbs files messages ]

Forums before death by AOL, social media and spammers... "We can't have nice things"

   comp.databases.oracle      Overblown overpriced overengineered SHIT      2,288 messages   

[   << oldest   |   < older   |   list   |   newer >   |   newest >>   ]

   Message 1,130 of 2,288   
   Blueyonder to All   
   A design question   
   20 Feb 04 16:00:34   
   
   XPost: comp.databases.oracle.server   
   From: a@abc.com   
      
   This question is not strictly Oracle only but as I'm using Oracle 8i I   
   couldn't think of a better place to post it!   
      
   Anyway my problem/qustion is that I have a record that has in access of 200   
   fields - all the fields relate entirely to a record. Virtually all fields   
   are optional e.g NULL.   
      
   Just wondering is there is a better way to manage them as the users want an   
   audit log of changes so before every update the whole record has to written   
   to the audit table - this can happen if theres only one change. I know I   
   could work out a way to just write changed fields values but time is so   
   tight I have to write the entire record for now.   
      
   I could move blocks of fields in to other related tables but there will   
   ALWAYS be a one to one relationship so it seems wrong to me anyway to   
   separate them.   
      
   Any suggestions/ideas?   
      
   thanks   
      
   harry   
      
   --- SoupGate-Win32 v1.05   
    * Origin: you cannot sedate... all the things you hate (1:229/2)   

[   << oldest   |   < older   |   list   |   newer >   |   newest >>   ]


(c) 1994,  bbs@darkrealms.ca