I think the reason they have not been automatically removed is exactly
that... they might have been retired, but we don't want to remove just in
case you have something there of value... regarding all the tables, I don't
recognize all of them myself.. but translation has been replaced by other
Morten,
That is the dilemma - how do we know those tables are irrelevant? And if
they are - why doesn't the startup routines (tablealteror etc) remove them?
Regards
Calle
On Mon, 27 Aug 2018 at 13:12, Morten Olav Hansen wrote:
> Hi Calle
>
> I'm not going to start digging down in the HBM
Morten,
Sorry, I meant to say how do we know ALL of those tables are not relevant
any more? I agree with you that they most likely are, but it is preferable
to know for sure (and actually that such tables are automatically removed)
Regards
calle
On Mon, 27 Aug 2018 at 13:27, Calle Hedberg
Hi Calle
I'm not going to start digging down in the HBM history we have... but if
you see tables not relevant anymore, you can just delete them.. most of
this is not relevant anymore I'm sure
--
Morten Olav Hansen
Senior Engineer, DHIS 2
Team Integration Lead
University of Oslo
Hi,
Further to the list above, here are six additional tables we have in one
instance that do not exist in the standard current 2.28 data model:
*Query12*
table_name
importdatavalue
importobject
instanceconfig
metadatafilter
trackedentityattributegroup
translation
On Fri, 24 Aug 2018 at 13:48,
Devs,
While investigating the many duplicates and gaps found in many existing
2.28 instances - most of them created in version 2.18 - 2.22 and then
upgraded over time - we also found a number of tables (and at least one
field) that no longer exist in a "clean" 2.28 instance.
The single "missing"
6 matches
Mail list logo
