[Mulgara-dev] dateTime information being corrupted

[Paul Gearon]

Ah, OK.


On 11/2/06, David Moll <DMoll at viewpointusa.com> wrote:
>
>  Actually we're just doing an insertion of raw triples.  The insert query
> looks like:
>
<snip/>

> This is also the query that we run to correct the incorrect dateTime
> elements, and checking the triples immediately after they are inserted shows
> the correct information.  So we are reasonably certain the the problem is
> not in the initial insert query that puts the triples into the data store,
> but is occurring at some later point.
>

Doesn't sound like an easy one to track down.

Do you have any way to reproduce this?  I suppose it is completely random?

Logging is not currently running on our production system.  I have not
> looked at the log4j-conf.xml file much as of yet.  Our production system
> is running TKS, so while I can't look at any of that code, I can investigate
> the logging options that should be turned on the next time we restart the
> system.
>

TKS?!?  Erk.  I never knew when TKS releases were built, so I don't know
which will be your corresponding Kowari.  You may well be looking at a bug
that was since fixed, but I don't know how to find out.

I'm not about to suggest that you change your production system, but is it
possible to duplicate it using Mulgara (or a recent Kowari) instead of TKS?
If this is still a problem then we will need to get to it quickly.  I have a
feeling that it may be resolved though...

Paul
-------------- next part --------------
An HTML attachment was scrubbed...
URL: http://mulgara.org/pipermail/mulgara-dev/attachments/20061102/07a2a949/attachment.html