[Mulgara-dev] dateTime information being corrupted

[David Moll]

Actually we're just doing an insertion of raw triples.  The insert query
looks like:
 
insert
 
<http://www.viewpointusa.com/vss/fm#027D1235-B3C6-47B8-A315E9AAFB2C206B>

 <http://www.viewpointusa.com/vss/elements/1.0/createdDate> 
 '2006-10-26T23:21:46'^^<http://www.w3.org/2001/XMLSchema#dateTime> 
 
 
<http://www.viewpointusa.com/vss/fm#027D1235-B3C6-47B8-A315E9AAFB2C206B>

 <http://www.viewpointusa.com/vss/elements/1.0/modifiedDate> 
 '2006-10-26T23:55:52'^^<http://www.w3.org/2001/XMLSchema#dateTime> 
 
 
<http://www.viewpointusa.com/vss/fm#027D1235-B3C6-47B8-A315E9AAFB2C206B>

 <http://www.viewpointusa.com/vss/elements/1.0/accessedDate> 
 '2006-10-26T23:21:46'^^<http://www.w3.org/2001/XMLSchema#dateTime> 
 
 
<http://www.viewpointusa.com/vss/fm#027D1235-B3C6-47B8-A315E9AAFB2C206B>

 <http://www.viewpointusa.com/vss/elements/1.0/uploadedDate> 
 '2006-10-26T23:53:32'^^http://www.w3.org/2001/XMLSchema#dateTime 
 
into <rmi://localhost/server1#model1>;
 
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.
 
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.
 
Thanks,
 
~Dave
 

________________________________

From: gearon at gmail.com [mailto:gearon at gmail.com] On Behalf Of Paul
Gearon
Sent: Thursday, November 02, 2006 11:51 AM
To: David Moll
Cc: mulgara-dev at mulgara.org
Subject: Re: [Mulgara-dev] dateTime information being corrupted


Am I correct in assuming that you are doing an "insert-select" here?
I'm guessing this, since the object you describe is a variable.

Based on this assumption, you've already started to use logging, so can
you turn on debug logging in: 
src/jar/resolver-store/java/org/mulgara/resolver/store/StatementStoreRes
olver.java

Line 359 does this following log:
logger.debug("Inserting statement: [" + statements.getSubject() + " "
                                                +
statements.getPredicate() + " "
                                                + statements.getObject()
+ "] in " + model);

This should tell you if the problem is the statement you retrieved (the
log will contain the wrong value).  Or the statement you insert (the log
will contain the correct value). 

Paul

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