Groups | Search | Server Info | Keyboard shortcuts | Login | Register [http] [https] [nntp] [nntps]


Groups > comp.lang.java.programmer > #32375

Re: JPA and extra fields

Path csiph.com!news.swapon.de!aioe.org!.POSTED!not-for-mail
From Arne Vajhøj <arne@vajhoej.dk>
Newsgroups comp.lang.java.programmer
Subject Re: JPA and extra fields
Date Wed, 19 Aug 2015 19:13:28 -0400
Organization Aioe.org NNTP Server
Lines 51
Message-ID <mr32iq$9aq$1@speranza.aioe.org> (permalink)
References <87zj1v3vnq.fsf@Equus.decebal.nl> <55cd52c4$0$298$14726298@news.sunsite.dk> <87mvxnr4e8.fsf@Equus.decebal.nl>
NNTP-Posting-Host 6sQnVX30ysopbfpJ+C2lEQ.user.speranza.aioe.org
Mime-Version 1.0
Content-Type text/plain; charset=utf-8; format=flowed
Content-Transfer-Encoding 8bit
X-Complaints-To abuse@aioe.org
User-Agent Mozilla/5.0 (Windows NT 6.1; WOW64; rv:38.0) Gecko/20100101 Thunderbird/38.2.0
X-Notice Filtered by postfilter v. 0.8.2
Xref csiph.com comp.lang.java.programmer:32375

Show key headers only | View raw


On 8/19/2015 5:53 AM, Cecil Westerhof wrote:
> On Friday 14 Aug 2015 04:30 CEST, Arne Vajhøj wrote:
>> On 8/13/2015 2:12 PM, Cecil Westerhof wrote:
>>> I am new to JPA. I have to migrate a JDBC application to JPA. For a
>>> certain class there are some extra fields in the table that are not
>>> in the class itself. (For example creation time, modification time
>>> and user that created the entity.) Is it possible to keep those
>>> fields in the table and updated, without putting the values in the
>>> class?
>
> […]
>
>> 2)
>>
>> Add the fields to the class but do not expose them in its
>> public API. And let them be updated internally.
>>
>> Possible by mapping fields and either no getter/setter
>> or protected.
>
> I do not need the getter fields, but I use setter fields like:
>      public void setDatecreated(final Date datecreated) {
>          this.datecreated = datecreated;
>      }
>
>      public void setUserIDCreated(final String userIDCreated) {
>          this.userIDCreatie = userIDCreatie;
>      }
>
>      public void setTimeMutated(final Timestamp timeMutated) {
>      this.tiimeMutated = timeMutated;
>      }
>
>      public void setUserIDMutated(final String userIDMutated) {
>          this.userIDMutated = userIDMutated;
>      }
>
> The first two could be done in the initialisation of the entity, but
> that would give a difference in functionality, so I do not opt for
> that.

If you call a constructor instead of loading from database, then
I would consider that creation time.

> Another possibility would be to write the functions beforeCreate and
> beforeMutate. That would be probably better as my current solution?

Or maybe have all other setters update the mutated property?

Arne

Back to comp.lang.java.programmer | Previous | Next — Previous in thread | Next in thread | Find similar | Unroll thread


Thread

JPA and extra fields Cecil Westerhof <Cecil@decebal.nl> - 2015-08-13 20:12 +0200
  Re: JPA and extra fields Eternal Hope <laughingspam99@gmail.com> - 2015-08-13 20:29 +0100
    Re: JPA and extra fields Cecil Westerhof <Cecil@decebal.nl> - 2015-08-17 07:40 +0200
  Re: JPA and extra fields Arne Vajhøj <arne@vajhoej.dk> - 2015-08-13 22:30 -0400
    Re: JPA and extra fields Cecil Westerhof <Cecil@decebal.nl> - 2015-08-17 08:22 +0200
      Re: JPA and extra fields Martin Gregorie <martin@address-in-sig.invalid> - 2015-08-17 11:40 +0000
        Re: JPA and extra fields Cecil Westerhof <Cecil@decebal.nl> - 2015-08-17 14:36 +0200
          Re: JPA and extra fields Martin Gregorie <martin@address-in-sig.invalid> - 2015-08-17 18:08 +0000
            Re: JPA and extra fields Cecil Westerhof <Cecil@decebal.nl> - 2015-08-17 21:24 +0200
              Re: JPA and extra fields Martin Gregorie <martin@address-in-sig.invalid> - 2015-08-17 22:47 +0000
                Re: JPA and extra fields Cecil Westerhof <Cecil@decebal.nl> - 2015-08-19 11:32 +0200
          Re: JPA and extra fields Arne Vajhøj <arne@vajhoej.dk> - 2015-08-17 19:48 -0400
        Re: JPA and extra fields Eternal Hope <laughingspam99@gmail.com> - 2015-08-18 06:25 +0100
          Re: JPA and extra fields Martin Gregorie <martin@address-in-sig.invalid> - 2015-08-18 10:49 +0000
            Re: JPA and extra fields Eternal Hope <laughingspam99@gmail.com> - 2015-08-19 09:00 +0100
              Re: JPA and extra fields Cecil Westerhof <Cecil@decebal.nl> - 2015-08-19 11:36 +0200
                Re: JPA and extra fields Martin Gregorie <martin@address-in-sig.invalid> - 2015-08-19 10:48 +0000
      Re: JPA and extra fields Arne Vajhøj <arne@vajhoej.dk> - 2015-08-17 19:46 -0400
        Re: JPA and extra fields Cecil Westerhof <Cecil@decebal.nl> - 2015-08-19 11:28 +0200
    Re: JPA and extra fields Cecil Westerhof <Cecil@decebal.nl> - 2015-08-19 11:53 +0200
      Re: JPA and extra fields Martin Gregorie <martin@address-in-sig.invalid> - 2015-08-19 10:51 +0000
        Re: JPA and extra fields Cecil Westerhof <Cecil@decebal.nl> - 2015-08-19 13:14 +0200
          Re: JPA and extra fields Cecil Westerhof <Cecil@decebal.nl> - 2015-08-19 14:19 +0200
      Re: JPA and extra fields Arne Vajhøj <arne@vajhoej.dk> - 2015-08-19 19:13 -0400
  Re: JPA and extra fields Silvio <silvio@internet.com> - 2015-08-20 03:49 +0200

csiph-web