[jira] [Commented] (ISIS-1859) Use of "timestamp" in JDOQL queries.
[
https://issues.apache.org/jira/browse/ISIS-1859?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16364000#comment-16364000
]
ASF subversion and git services commented on ISIS-1859:
---
Commit a47243ff9fb6aac28d9a4b80b807fb0693216532 in isis's branch
refs/heads/ISIS-1852_parallel_stream_patch from [~danhaywood]
[ https://gitbox.apache.org/repos/asf?p=isis.git;h=a47243f ]
ISIS-1859: adds a hint-n-tip doc
> Use of "timestamp" in JDOQL queries.
>
>
> Key: ISIS-1859
> URL: https://issues.apache.org/jira/browse/ISIS-1859
> Project: Isis
> Issue Type: Documentation
>Affects Versions: 1.16.0
>Reporter: Dan Haywood
>Assignee: Dan Haywood
>Priority: Trivial
> Fix For: 1.16.1
>
>
> As posted by me on the DN gitter channel...
> {code:java}
> I have an entity CommandJdo that has a property called "timestamp", of type
> java.sql.Timestamp
> My JDOQL for this is:
> SELECT
> FROM org.isisaddons.module.command.dom.CommandJdo
> WHERE executeIn == 'FOREGROUND'
> && timestamp > :timestamp
> && startedAt != null
> && completedAt != null
> ORDER BY timestamp ASC
> Running against SQL Server 2016 this gave me a different result first time it
> was run compared to subsequent times.
> Running SQL Profiler I found the underlying SQL as:
> exec sp_prepexec @p1 output,N'@P0 datetime2',N'SELECT
> ''org.isisaddons.module.command.dom.CommandJdo'' AS
> NUCLEUS_TYPE,A0.arguments,A0.completedAt,A0."exception",A0.executeIn,A0.memberIdentifier,A0.memento,A0.replayState,A0.replayStateFailureReason,A0."result",A0.startedAt,A0.targetAction,A0.targetClass,A0.target,A0."timestamp",A0.transactionId,A0."user",''2018-01-24
> 17:29:18.3'' AS NUCORDER0 FROM isiscommand.Command A0 WHERE A0.executeIn =
> ''FOREGROUND'' AND A0."timestamp" > @P0 AND A0.startedAt IS NOT NULL AND
> A0.completedAt IS NOT NULL ORDER BY NUCORDER0 OFFSET 0 ROWS FETCH NEXT 2 ROWS
> ONLY ','2018-01-24 17:29:18.300'
> To unpick this, the key bit is: '
> '2018-01-24 17:29:18.3'' AS NUCORDER0
> ... ORDER BY NUCORDER0
> So in the JDOQL the "ORDER BY timestamp ASC", the "timestamp" is being
> evaluated as the current time, I suppose as a sort-of built-in function.
> Which was surprising.
> My fix was to change the JDOQL to be:
> ORDER BY this.timestamp ASC{code}
>
>
--
This message was sent by Atlassian JIRA
(v7.6.3#76005)
[jira] [Commented] (ISIS-1859) Use of "timestamp" in JDOQL queries.
[
https://issues.apache.org/jira/browse/ISIS-1859?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16363970#comment-16363970
]
ASF subversion and git services commented on ISIS-1859:
---
Commit a47243ff9fb6aac28d9a4b80b807fb0693216532 in isis's branch
refs/heads/master from [~danhaywood]
[ https://gitbox.apache.org/repos/asf?p=isis.git;h=a47243f ]
ISIS-1859: adds a hint-n-tip doc
> Use of "timestamp" in JDOQL queries.
>
>
> Key: ISIS-1859
> URL: https://issues.apache.org/jira/browse/ISIS-1859
> Project: Isis
> Issue Type: Documentation
>Affects Versions: 1.16.0
>Reporter: Dan Haywood
>Assignee: Dan Haywood
>Priority: Trivial
> Fix For: 1.16.1
>
>
> As posted by me on the DN gitter channel...
> {code:java}
> I have an entity CommandJdo that has a property called "timestamp", of type
> java.sql.Timestamp
> My JDOQL for this is:
> SELECT
> FROM org.isisaddons.module.command.dom.CommandJdo
> WHERE executeIn == 'FOREGROUND'
> && timestamp > :timestamp
> && startedAt != null
> && completedAt != null
> ORDER BY timestamp ASC
> Running against SQL Server 2016 this gave me a different result first time it
> was run compared to subsequent times.
> Running SQL Profiler I found the underlying SQL as:
> exec sp_prepexec @p1 output,N'@P0 datetime2',N'SELECT
> ''org.isisaddons.module.command.dom.CommandJdo'' AS
> NUCLEUS_TYPE,A0.arguments,A0.completedAt,A0."exception",A0.executeIn,A0.memberIdentifier,A0.memento,A0.replayState,A0.replayStateFailureReason,A0."result",A0.startedAt,A0.targetAction,A0.targetClass,A0.target,A0."timestamp",A0.transactionId,A0."user",''2018-01-24
> 17:29:18.3'' AS NUCORDER0 FROM isiscommand.Command A0 WHERE A0.executeIn =
> ''FOREGROUND'' AND A0."timestamp" > @P0 AND A0.startedAt IS NOT NULL AND
> A0.completedAt IS NOT NULL ORDER BY NUCORDER0 OFFSET 0 ROWS FETCH NEXT 2 ROWS
> ONLY ','2018-01-24 17:29:18.300'
> To unpick this, the key bit is: '
> '2018-01-24 17:29:18.3'' AS NUCORDER0
> ... ORDER BY NUCORDER0
> So in the JDOQL the "ORDER BY timestamp ASC", the "timestamp" is being
> evaluated as the current time, I suppose as a sort-of built-in function.
> Which was surprising.
> My fix was to change the JDOQL to be:
> ORDER BY this.timestamp ASC{code}
>
>
--
This message was sent by Atlassian JIRA
(v7.6.3#76005)
[jira] [Commented] (ISIS-1859) Use of "timestamp" in JDOQL queries.
[
https://issues.apache.org/jira/browse/ISIS-1859?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16363262#comment-16363262
]
ASF subversion and git services commented on ISIS-1859:
---
Commit a47243ff9fb6aac28d9a4b80b807fb0693216532 in isis's branch
refs/heads/maint-1.16.1 from [~danhaywood]
[ https://gitbox.apache.org/repos/asf?p=isis.git;h=a47243f ]
ISIS-1859: adds a hint-n-tip doc
> Use of "timestamp" in JDOQL queries.
>
>
> Key: ISIS-1859
> URL: https://issues.apache.org/jira/browse/ISIS-1859
> Project: Isis
> Issue Type: Documentation
>Affects Versions: 1.16.0
>Reporter: Dan Haywood
>Assignee: Dan Haywood
>Priority: Trivial
> Fix For: 1.16.1
>
>
> As posted by me on the DN gitter channel...
> {code:java}
> I have an entity CommandJdo that has a property called "timestamp", of type
> java.sql.Timestamp
> My JDOQL for this is:
> SELECT
> FROM org.isisaddons.module.command.dom.CommandJdo
> WHERE executeIn == 'FOREGROUND'
> && timestamp > :timestamp
> && startedAt != null
> && completedAt != null
> ORDER BY timestamp ASC
> Running against SQL Server 2016 this gave me a different result first time it
> was run compared to subsequent times.
> Running SQL Profiler I found the underlying SQL as:
> exec sp_prepexec @p1 output,N'@P0 datetime2',N'SELECT
> ''org.isisaddons.module.command.dom.CommandJdo'' AS
> NUCLEUS_TYPE,A0.arguments,A0.completedAt,A0."exception",A0.executeIn,A0.memberIdentifier,A0.memento,A0.replayState,A0.replayStateFailureReason,A0."result",A0.startedAt,A0.targetAction,A0.targetClass,A0.target,A0."timestamp",A0.transactionId,A0."user",''2018-01-24
> 17:29:18.3'' AS NUCORDER0 FROM isiscommand.Command A0 WHERE A0.executeIn =
> ''FOREGROUND'' AND A0."timestamp" > @P0 AND A0.startedAt IS NOT NULL AND
> A0.completedAt IS NOT NULL ORDER BY NUCORDER0 OFFSET 0 ROWS FETCH NEXT 2 ROWS
> ONLY ','2018-01-24 17:29:18.300'
> To unpick this, the key bit is: '
> '2018-01-24 17:29:18.3'' AS NUCORDER0
> ... ORDER BY NUCORDER0
> So in the JDOQL the "ORDER BY timestamp ASC", the "timestamp" is being
> evaluated as the current time, I suppose as a sort-of built-in function.
> Which was surprising.
> My fix was to change the JDOQL to be:
> ORDER BY this.timestamp ASC{code}
>
>
--
This message was sent by Atlassian JIRA
(v7.6.3#76005)
