Re: History functionality
Date: Wed, 10 Mar 2004 23:45:45 GMT
Message-ID: <JMN3c.193226$Hy3.165315_at_edtnps89>
Daniel Morgan wrote:
> Harald Maier wrote:
>
>> Daniel Morgan <damorgan_at_x.washington.edu> writes: >> >> >>> Philipp Gath wrote: >>> >>> >>>> Hi, >> >> >> >>>> i'm currently working on a little Database project for my >>>> diploma. Now i need to have a history funtionality for a few of my >>>> tables. This must include the old values, time and date of change >>>> and user who changed the value. Has anyone an idea how to realize >>>> such a functionality in an "as intelligent as possible" way? Or >>>> maybe a good tip for literatur regarding this problem? Thanks in >>>> advance. >>> >>> >>> In addition to triggers look at the LT package, usually accessed >>> using the DBMS_WM synonym. >> >> >> >> Hello Daniel, >> >> what does the abbreviation LT mean? >> >> Harald
>
>
> It means the development team used the initials LT and that later on
> there was so much code referring to it no one wanted to change it to
> something more meaningful.
>
> Likely no one but the developers and a handful of people in Redwood
> Shores know.
The 'Long Transaction' support was introduced in Oracle 8.1.6 as a supplement to Spatial option to support Transactions that needed to survive but remain 'uncommitted' across user/session log-off. (The term Long Transaction referred to the temporal aspect.)
In Oracle 8.1.7 this formed the core to Workspace Management, and were documented as part of the Spatial option doc set. During this time, there was considerable discussion about the application of Long Transactions outside of the Spatial area and several examples of use as general workspace and 'data versioning' were presented.
Can you give me any example of initials being used in a package or feature name? I can't think of any off-hand.
HTH
/Hans
Received on Thu Mar 11 2004 - 00:45:45 CET