Subject | Re: [firebird-support] Re: Historic tables design |
---|---|
Author | Lester Caine |
Post date | 2013-08-01T06:40:53Z |
Alexandre Benson Smith wrote:
Managing metadata should ALWAYS be detached from anything to do with data. In
fact the only metadata changes to our historic data over the years has been the
addition of a few extra fields.
And Aldo's comment about 'UNIQUE' constraint also applies.
--
Lester Caine - G8HFL
-----------------------------
Contact - http://lsces.co.uk/wiki/?page=contact
L.S.Caine Electronic Services - http://lsces.co.uk
EnquirySolve - http://enquirysolve.com/
Model Engineers Digital Workshop - http://medw.co.uk
Rainbow Digital Media - http://rainbowdigitalmedia.co.uk
> Em 31/7/2013 21:38, Iwan Cahyadi Sugeng escreveu:I'd second that ...
>>
>> I plan to check the historical table on system start and update the
>> metadata. I'm using n-tier solution, so my server application will do the
>> metadata update
>>
>
> I don't know your logic and perhaps this comment doesn't apply to your
> case, but anyway...
>
> I think it's better to check the metadata and stop/report about some
> misleading table information, it's not recommended to update metadata
> with the database in use.
Managing metadata should ALWAYS be detached from anything to do with data. In
fact the only metadata changes to our historic data over the years has been the
addition of a few extra fields.
And Aldo's comment about 'UNIQUE' constraint also applies.
--
Lester Caine - G8HFL
-----------------------------
Contact - http://lsces.co.uk/wiki/?page=contact
L.S.Caine Electronic Services - http://lsces.co.uk
EnquirySolve - http://enquirysolve.com/
Model Engineers Digital Workshop - http://medw.co.uk
Rainbow Digital Media - http://rainbowdigitalmedia.co.uk