Re: Storing complete table rows in a single field

> Hmmm, without knowing which version of Oracle it's hard to recommend
> anything specific. So it has to be a general advice, or roll-your-own.
>
> O-Tables and ROWTYPE may come into it indirectly. Through PL/SQL.
> I'd look at triggers, with PL/SQL code to merge the data as one
> column only. You won't get it automatically generated, unless
> you roll your own PL/SQL code generator based on dictionary information
> for each table. I'd also be VERY careful with dumping the lot from
> multiple tables into a single audit table: great recipe for a HUGE
> bottleneck (or should I say a *small* bottleneck?).
>

It will need to work with Oracle 9i upwards. As I say, I have it working in SQL Server and since I need to impliment the same thing in Oracle I'd like them to be as similar as possible for code maintenance reasons (we have a lot of other stored procedures which we translate automatically into SQL Server SP's)
Each field in the "Audit" table should contain one complete row from one of many other tables.
We do need to store the complete record each time which is why we didn't go for the normal audit approach which seems to just record changes.
The database would not be undergoing an enormous amount of change so it is unlikely that this would end up dumping huge amounts of data into the "audit" table.

Ken Received on Fri Jan 23 2004 - 03:47:19 CST