Re: [PROPOSAL] DataModel - Improve Internal Fields injection

[Michael Brohl]

I have not time to elaborate in-depth right now, but just a quick food for thought:

Regards,

Michael Brohl

ecomify GmbH - www.ecomify.de


Am 24.04.19 um 12:40 schrieb Pierre Smits:

Having these fields in every entity *by default* allows detailed tracking of users which might be unwanted. I know that this is a sensible topic in companies and affects privacy protection. I am not sure how the selection of entities with these fields was done, maybe others can add insights.

Thanks Michael,

So we should keep those *TxStamp fields.

But what about the second suggestion about having the  'createdByUserLogin'
and 'lastModifiedByUserLogin'  fields added to the internal fields set?

Best regards,

Pierre Smits

*Apache Trafodion <https://trafodion.apache.org>, Vice President*
*Apache Directory <https://directory.apache.org>, PMC Member*
Apache Incubator <https://incubator.apache.org>, committer
*Apache OFBiz <https://ofbiz.apache.org>, contributor (without privileges)
since 2008*
Apache Steve <https://steve.apache.org>, committer


On Wed, Apr 24, 2019 at 12:20 PM Michael Brohl <michael.br...@ecomify.de>
wrote:

These fields are not the same, they can differ. The TX fields mark the
transaction timestamp while the non TX fields mark the "real" update
time. You can see it when you watch closely in the database. All changes
made within an transaction have the same tx timestamp.

Regards,

Michael Brohl

ecomify GmbH - www.ecomify.de


Am 24.04.19 um 09:48 schrieb Pierre Smits:

Hi All,

Currently our functions inject following internal fields into the model

of

each entity:

     - createdStamp
     - createdTxStamp
     - lastUpdatedStamp
     - lastUpdatedTxStamp

All of the fields above are of the field type definition 'date-time',
giving for java: java.sql.Timestamp, and for sql: TIMESTAMP. This means
that the createdTxStamp is the same as createdStamp  and

lastUpdatedTxStamp

is the same as lastUpdatedStamp.

Should we get rid of the redundant fields?

Also, a lot of entity definitions in the various models have the
'createdByUserLogin' and 'lastModifiedByUserLogin' added.

Should we have these fields added to the internal fields set so that

these

are always injected into the model of each entity, and always filled?

Best regards,

Pierre Smits

*Apache Trafodion <https://trafodion.apache.org>, Vice President*
*Apache Directory <https://directory.apache.org>, PMC Member*
Apache Incubator <https://incubator.apache.org>, committer
*Apache OFBiz <https://ofbiz.apache.org>, contributor (without

privileges)

since 2008*
Apache Steve <https://steve.apache.org>, committer

smime.p7s
Description: S/MIME Cryptographic Signature