Hi Evan,
Do you mean that
(a) Users do want (must take care) to truncate the date value
appropriately on their own before they store it in the date attribute
of some entity ?
or
(b) OpenJPA should take the value stored in a date field of some
entity (e.g. 12:34:56.123456789) and truncate/round
In several cases you do want to truncate, just at a certain resolution
lower than seconds, e.g. 100th of a second.
> -Original Message-
> From: Dinkar Rao [mailto:[EMAIL PROTECTED]
> Sent: Saturday, 28 June 2008 4:54 a.m.
> To: dev@openjpa.apache.org
> Subject: Re: [jira] Closed: (OPENJPA-
Patrick and others,
On Fri, Jun 27, 2008 at 1:29 PM, Patrick Linskey <[EMAIL PROTECTED]> wrote:
> Hi,
>
> I guess I see things a bit differently than does Craig.
> Pragmatically-speaking, it is quite difficult to "just" use an internal svn
> repository. Would that we all used git, my tune might b
Hi,
I guess I see things a bit differently than does Craig. Pragmatically-
speaking, it is quite difficult to "just" use an internal svn
repository. Would that we all used git, my tune might be different.
Setting up a separate svn repository for distribution-specific
maintenance is a diffi
Thanks for the clarification, Dinkar.
On Fri, Jun 27, 2008 at 11:53 AM, Dinkar Rao <[EMAIL PROTECTED]>
wrote:
> The warnings about Sybase, SQLServer, and Infomix are just a reminder
> for folks trying to use precise dates in their code. Due to
> limitations in these databases with precision for d
[
https://issues.apache.org/jira/browse/OPENJPA-646?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Kevin Sutter updated OPENJPA-646:
-
Attachment: openjpa-646.patch
This hack of a patch just modifies our TempClassLoader implementat
The warnings about Sybase, SQLServer, and Infomix are just a reminder
for folks trying to use precise dates in their code. Due to
limitations in these databases with precision for date types, what
you get back from the database might not be what you expect.
On the OpenJPA side, we ensure with thi
[
https://issues.apache.org/jira/browse/OPENJPA-646?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Kevin Sutter updated OPENJPA-646:
-
Attachment: pmr.zip
File pmr.zip is a simplified version of the problem that I put together for
JDK problems with defineClass and enum class types
--
Key: OPENJPA-646
URL: https://issues.apache.org/jira/browse/OPENJPA-646
Project: OpenJPA
Issue Type: Bug
Components: kernel
A
[
https://issues.apache.org/jira/browse/OPENJPA-643?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Jeremy Bauer updated OPENJPA-643:
-
Attachment: CacheImplTest.jar
Attaching cache implementation test program from parent task, OPEN
Should this topic be opened as a separate Issue (or sub-task)? Or, should
this Issue just be re-opened? I'm not an expert with this timestamp stuff,
but it seems like we still have an open issue with this resolution.
Kevin
On Thu, Jun 26, 2008 at 4:13 PM, Dinkar Rao <[EMAIL PROTECTED]>
wrote:
11 matches
Mail list logo
