Sorry to jump onto an old thread like this, but I'm running into an issue where I have data that comes in with Date fields and TimeOfDay fields. The Date fields are basically ISO8601 in UTC zulu time (yyyy-MM-ddTHH:mm:ssZ" and I can handle that just fine... but the TimeOfDay fields are just a HH:mm:ss string showing the 24-hour time of day.
Currently I'm just keeping those as strings, but it would be nice if there was a time-only field type as a proper type... Is there any possibility in the future that OrientDB might support a time-specific data type? -William On Tuesday, May 26, 2015 at 2:28:43 AM UTC-6, scott molinari wrote: > > From a NoSQL database perspective, I'd say it is par for the course. > Neither MongoDB nor Neo4J, for instance, support a time field type. > > http://docs.mongodb.org/manual/reference/bson-types/ > http://neo4j.com/docs/stable/rest-api-property-values.html > > Though, since they all offer an integer for a datetime field and it can > depict time down to milliseconds, calculations on it are relatively easy > and quite accurate. > > That said, the answer from you Luca is a bit disheartening for me, as > someone who is looking for a better alternative to MongoDB. The features > other RDBMSes offer should be quite clear to you and it shouldn't be up to > a customer to "point them out". Wayne already pointed out what he wants. > The answer should have been either reasoning to the decision not to support > a time field or the path to the addition of the field type, like an issue > in your project tracking system. > > You should really never make customer run (around), if you can. > > Scott > -- --- 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/d/optout.
