[
https://issues.jboss.org/browse/TEIID-5026?page=com.atlassian.jira.plugin...
]
Steven Hawkins commented on TEIID-5026:
---------------------------------------
So this enhancement can be considered exactly that.
My confusion is that this seemed to stem from JDG integration, which seems like it would
use millis/longs instead.
Looking at this more, I think our implementation of from_unixtime is not correct. The
other vendors use it as a conversion to string, not to timestamp - although in many
contexts that distinction won't matter. I'll see if there is a way to rationalize
all of this.
Add function to transform timestamp into Unix time
--------------------------------------------------
Key: TEIID-5026
URL:
https://issues.jboss.org/browse/TEIID-5026
Project: Teiid
Issue Type: Feature Request
Components: Query Engine
Reporter: Jan Stastny
Assignee: Steven Hawkins
Fix For: 10.0
Teiid supports function FROM_UNIXTIME as a result of TEIID-248.
There isn't its reverse counterpart though.
This is an issue, when there is a data source which doesn't support
timestamp/date/time data types:
* users choose to use long(unix time) in the source
* by using FROM_UNIXTIME function they transform the long value (unix time) into
respective data type value in their virtual model
* they can read such source.
* they can't insert/update it as this would require 'INSTEAD OF TRIGGER' with
ability to transform timestamp/time/date back to long value - Unix time. This part is
missing.
As an example could serve [MySQL's
UNIX_TIMESTAMP|https://dev.mysql.com/doc/refman/5.5/en/date-and-time-func...]
--
This message was sent by Atlassian JIRA
(v7.2.3#72005)