M
martinz
Guest
Hi, Many of our customers do ETL on our databases. In order to optimize/minimize the number of records loaded and scanned, it would be handy to have a field in each table that gets updated on every change. We could add a timestamp field and modify it using database triggers, however that has some drawbacks: we'd need create and write triggers on each table that has such a field these triggers would only be fired when updates are performed through ABL, not SQL these triggers will be executed in the clients session. As our applications are largely C/S, that wouldn't be optimal. What we really need is the ability to denote a field as a (timestamp based) rowversion field and have that updated (by the database engine) on every modification of a record. Probably the only case when it should not be updated is when doing a (binary) load of a table. When doing a ascii load, it could maybe be an option to enable or disable rowversioning. - Martin
Continue reading...
Continue reading...