I'm also new to OrientDB, but I think you should try changing the global
datetime format
<http://orientdb.com/docs/2.1/Managing-Dates.html#date-and-datetime-formats>("yyyy-MM-dd
HH:mm:ss a") first and then use asDateTime()
<http://orientdb.com/docs/last/SQL-Methods.html#asdatetime> in the ETL
configuration file like this:
> { "field": { "fieldName": "your_new_field_name", "expression":
> "your_old_field_name.asDateTime()" } }
On Friday, September 25, 2015 at 5:32:57 AM UTC+9, Joe S. wrote:
>
> I'm trying to ETL import from a MySQL database. currently the information
> is in a string with mm/dd/yyyy hh:mm:ss tt format. ex. 8/22/2013 9:43:05 AM
>
> I can't change the format in the database because I have another program
> writing the information to it, but I want to be able to move it into
> orientdb.
>
> Tested this as a transform.
>
> { "field": { "fieldName": "time_modified", "expression": "date(
> $time_modified, 'mm-dd-yyyy hh:mm:ss tt' )" } }
>
>
> How can I use the ETL import to convert it to the proper datetime format?
>
> Alternatively I can leave it as a string, but then I don't think I can
> make calculations against it.
>
--
---
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.
