Mailing-List: contact users-help@openjpa.apache.org; run by ezmlm
Precedence: bulk
Reply-To: users@openjpa.apache.org
Received-SPF: pass (nike.apache.org: domain of kwsutter@gmail.com designates
 209.85.217.174 as permitted sender)
MIME-Version: 1.0
In-Reply-To: 
 <CAKiEph+=NczPZtk51Fy6ZUj5m3Oq4AKcHVQ61CbPOF6bgx_agg@mail.gmail.com>
References: 
 <CAKiEphKzgqKu_D_uLirDL1K0H4vaZYA1uGvn7Eus71FrOD0K0w@mail.gmail.com>
 <CABH8erksGm3c0WuPLkaXh+NLaSyThrkA6m2AZFscW4eQjSK4LQ@mail.gmail.com>
 <CAKiEphJeqvPTTV2kiM4urMeVanVeO0VS5bfp5cArATe8uM=vuQ@mail.gmail.com>
 <CABH8ermoVO7WXrjXzHS3oDXEQS5dhW0KW0yTiisscx1WLA-Xbw@mail.gmail.com>
 <CAKiEph+mW5BnmLgf+PtPoPoOF8w-+8nWKcxMsiH+cEYhgq1JKQ@mail.gmail.com>
 <CABH8erkt3Mw6u8GE=1tx-FW76ZbwWpt-WUbcUD1FGVbZ2XOOQA@mail.gmail.com>
 <CAKiEph+=NczPZtk51Fy6ZUj5m3Oq4AKcHVQ61CbPOF6bgx_agg@mail.gmail.com>
From: Kevin Sutter <kwsutter@gmail.com>
Date: Thu, 21 Jun 2012 08:23:00 -0500
Message-ID: 
 <CABH8erm8gqT1XOGua0rsEhv3-PdAGotYDGDYPc4oyT99ovGP2g@mail.gmail.com>
Subject: Re: Timestamp precision question.
To: users@openjpa.apache.org
Content-Type: multipart/alternative; boundary=bcaec55407c077300b04c2fb6b2c

--bcaec55407c077300b04c2fb6b2c
Content-Type: text/plain; charset=ISO-8859-1

Correct.

On Wed, Jun 20, 2012 at 8:56 PM, yu wang <wangyumi@gmail.com> wrote:

> Kevin,
> So if I need nanosecond, the Date precision should be 1,right?
>
> Regards,
> Yu Wang
>
> On Wed, Jun 20, 2012 at 9:28 PM, Kevin Sutter <kwsutter@gmail.com> wrote:
> > Good to hear, Yu!
> >
> > It's kind of strange, but the base units used for timestamps are
> > Nanoseconds.  So, the DatePrecision specifies what multiplier to use to
> get
> > the desired precision.  Multiply Nanos by 1000 and you get Micros.  The
> > default value for DatePrecision is 1000000, which then translates to
> Millis.
> >
> > Kevin
> >
> > On Wed, Jun 20, 2012 at 4:54 AM, yu wang <wangyumi@gmail.com> wrote:
> >
> >> Kevin,
> >> It does work. Thanks! By the way, what does "DatePrecision=1000" mean?
> Why
> >> 1000?
> >>
> >> Regards,
> >> Yu Wang
> >>
> >>
> >> On Tue, Jun 19, 2012 at 10:04 PM, Kevin Sutter <kwsutter@gmail.com>
> wrote:
> >> > Thanks, Yu, for the clarification.
> >> >
> >> > By default, OpenJPA uses Millisecond precision on the date fields
> (least
> >> > common denominator).  Some of the data dictionaries have been updated
> to
> >> > Microsecond (DB2, Postgres, etc) or even Nanosecond (Ingres).  It
> looks
> >> > like the Oracle dictionary is still using the default Millisecond
> >> > precision.  You can easily update this by modifying the Oracle
> dictionary
> >> > as follows:
> >> >
> >> > <property name="openjpa.jdbc.DBDictionary"
> >> value="oracle(DatePrecision=1000)"/>
> >> >
> >> > If this does the trick for you and you feel that the default precision
> >> for
> >> > the Oracle dictionary should be Microseconds, please file a JIRA [1].
> >> >
> >> > Thanks, Kevin
> >> >
> >> > [1]  http://openjpa.apache.org/found-a-bug.html
> >> >
> >> > On Mon, Jun 18, 2012 at 11:24 PM, yu wang <wangyumi@gmail.com> wrote:
> >> >
> >> >> Kevin
> >> >> Before the field is persisted, I use toString() method of Timestamp
> >> >> object to print the value of the field, its precision is microsecond.
> >> >> But when I read the Timestamp field from DB, its precision is
> >> millisecond.
> >> >>
> >> >> I need the precision of this Timestamp filed is microsecond. I am
> >> >> using ORacle DB and I can insert microsecond Timestamp filed into DB
> >> >> by SQL directly.
> >> >>
> >> >> Thanks,
> >> >> Yu Wang
> >> >>
> >> >> On Mon, Jun 18, 2012 at 9:43 PM, Kevin Sutter <kwsutter@gmail.com>
> >> wrote:
> >> >> > Hi Yu,
> >> >> > Can you clarify your request?    You said that your Timestamp
> fields
> >> are
> >> >> > persisted to the DB at a millisecond level.  But, I'm not following
> >> your
> >> >> > "print" comments and microsecond precision level.  After retrieved
> >> from
> >> >> the
> >> >> > DB, are the Timestamps still at a millisecond precision?  Or, are
> you
> >> >> > looking to store the Timestamp to the DB at a microsecond
> precision?
> >> >> > Various databases have different practices as it comes to Timestamp
> >> >> > precision.  If you could clarify what your expectations are, maybe
> >> >> > something can be figured out.  Thanks.
> >> >> >
> >> >> > Kevin
> >> >> >
> >> >> > On Mon, Jun 18, 2012 at 4:31 AM, yu wang <wangyumi@gmail.com>
> wrote:
> >> >> >
> >> >> >> Hello,
> >> >> >> I am using OpenJPA 1.2.2 connecting oracle DB.
> >> >> >> For Timestamp field, the precision is always millisecond level
> after
> >> >> >> the filed is persisted into DB, regardless of I print the
> timestampe
> >> >> >> filed in java, its precision is microsecond level.
> >> >> >> Any specific configuration I am not aware of?
> >> >> >>
> >> >> >> Below is a sample:
> >> >> >>        @Basic()
> >> >> >>        @Column(name="LOGTIME")
> >> >> >>        public java.sql.Timestamp getLogtime() {
> >> >> >>                return this.logtime;
> >> >> >>        }
> >> >> >>        @Override
> >> >> >>        public void setLogtime(java.sql.Timestamp logtime) {
> >> >> >>                this.logtime = logtime;
> >> >> >>        }
> >> >> >>
> >> >> >> Regards,
> >> >> >> Yu Wang
> >> >> >>
> >> >>
> >>
>

--bcaec55407c077300b04c2fb6b2c--