You can use also: alter database DATETIMEFORMAT yyyy-MM-dd HH:mm:ss:SSS
And the same with DATEFORMAT. Lvc@ On 9 May 2012 11:33, Luca Garulli <[email protected]> wrote: > Hi Salvatore, > unfortunately this is not yet supported but you can save this setting once > for all at the beginning: > > db.getStorage().getConfiguration().dateTimeFormat = "yyyy-MM-dd > HH:mm:ss:SSS"; > db.getStorage().getConfiguration().update(); > > Then close and reopen the database (or stop and restart the server) and > the settings should be updated for all the clients. > > Lvc@ > > > On 9 May 2012 10:35, Salvatore Piccione <[email protected]> wrote: > >> Hello Luca, >> >> your reply implies that, on the server side, the java.util.Date instances >> preserve the milliseconds, right? >> I've some further questions: is there a way to set that configuration >> parameter without using the Java API? If not, this implies that it is not >> possible to perform queries with milliseconds precision through the web >> GUI... Could it be possible to enable the milliseconds precision also for >> non-Java clients? >> >> TIA, >> >> Salvatore >> >> >> 2012/5/8 Luca Garulli <[email protected]> >> >>> Ciao Salvatore, >>> it's a matter of configuration: >>> >>> Set this right after you've open the database: >>> >>> db.getStorage().getConfiguration().dateTimeFormat = "yyyy-MM-dd >>> HH:mm:ss:SSS"; >>> >>> Lvc@ >>> >>> >>> On 8 May 2012 18:16, Salvatore Piccione <[email protected]> wrote: >>> >>>> Hello, >>>> >>>> I've defined a simple class that has got a DATETIME property and I've >>>> inserted some data (below you can find the console script I run): >>>> >>>> CREATE DATABASE remote:localhost:2426/datetime-precision-test root pippo >>>> local graph;CREATE CLASS TestClass EXTENDS OGraphVertex;CREATE PROPERTY >>>> TestClass.Issuer STRING;CREATE PROPERTY TestClass.IssueInstant >>>> DATETIME;CREATE PROPERTY TestClass.ID STRING;CREATE PROPERTY >>>> TestClass.resourceID STRING;INSERT INTO TestClass (Issuer, IssueInstant, >>>> ID, resourceID) VALUES ('[email protected]', '2012-05-14 13:41:23:214', >>>> 'adafq3wr367364rfbeq', 'http://www.iot-at-work.eu/resourceA');INSERT INTO >>>> TestClass (Issuer, IssueInstant, ID, resourceID) VALUES >>>> ('[email protected]', '2012-05-14 13:41:23:147', 'f243erd3wr367364rfb', >>>> 'http://www.iot-at-work.eu/resourceB'); >>>> >>>> >>>> In order to test whether millisecond precision works in SQL WHERE clause, >>>> I've executed the queries below that select nothing: >>>> >>>> select from TestClass where IssueInstant = date( '2012-05-14 >>>> 13:41:23:214', 'yyyy-MM-dd HH:mm:ss:SSS' ) >>>> >>>> select from TestClass where IssueInstant = '2012-05-14 13:41:23:214' >>>> >>>> Indeed, both queries below select the records I defined. It seems that >>>> datetime milliseconds are ignored! >>>> >>>> select from TestClass where IssueInstant = date( '2012-05-14 >>>> 13:41:23:000', 'yyyy-MM-dd HH:mm:ss:SSS' ) >>>> >>>> select from TestClass where IssueInstant = '2012-05-14 13:41:23:000' >>>> >>>> Affected versions: *1.0rc9* and the latest *1.0-SNAPSHOT* (downloaded >>>> from >>>> https://oss.sonatype.org/content/groups/public/com/orientechnologies/orientdb/1.0-SNAPSHOT/orientdb-1.0-20120505.121554-24-distribution.zip >>>> ). >>>> The results are the same even if the SQL INSERT statements are run >>>> through the Java APIs. >>>> >>>> Any idea? >>>> >>>> TIA, >>>> >>>> Salvatore >>>> >>>> >>> >> > -- --- You received this message because you are subscribed to the Google Groups "OrientDB" group. To unsubscribe from this group and stop receiving emails from it, send an email to [email protected]. For more options, visit https://groups.google.com/groups/opt_out.
