Subject | Re: [firebird-support] Table information |
---|---|
Author | Thomas Steinmaurer |
Post date | 2014-03-11T07:36:03Z |
On 11.03.2014 08:09, Svein Erling Tysvær wrote:
There is also a gotcha I have seen in the field, where people maintain a
single table with one row per table and some sort of last changed field.
Or even worse a SINGLE record with a last updated timestamp field per table.
This results in a pure hotspot table (bottleneck) from a
concurrency/throughput POV.
This all would be a very nice use case for per-statement trigger instead
of per-row trigger, which Firebird doesn't support, unfortunately.
--
With regards,
Thomas Steinmaurer
http://www.upscene.com/
Professional Tools and Services for Firebird
FB TraceManager, IB LogManager, Database Health Check, Tuning etc.
>>> Is there a way to get information like last time the table wasRight. :-)
>>> updated/changed,
>>
>> No.
>
> 'No' as in no built-in support.
> It is easily doable by having a AFTER INSERT OR UPDATE trigger or add a field with CURRENT_TIMESTAMP as default. Though, of course, this will only help you get the last COMMITTED change of the table.Yes and it won't work for deletes.
There is also a gotcha I have seen in the field, where people maintain a
single table with one row per table and some sort of last changed field.
Or even worse a SINGLE record with a last updated timestamp field per table.
This results in a pure hotspot table (bottleneck) from a
concurrency/throughput POV.
This all would be a very nice use case for per-statement trigger instead
of per-row trigger, which Firebird doesn't support, unfortunately.
--
With regards,
Thomas Steinmaurer
http://www.upscene.com/
Professional Tools and Services for Firebird
FB TraceManager, IB LogManager, Database Health Check, Tuning etc.