[JBoss JIRA] Updated: (TEIID-251) Support SQL 2003 order by with expressions
by Steven Hawkins (JIRA)
[ https://jira.jboss.org/jira/browse/TEIID-251?page=com.atlassian.jira.plug... ]
Steven Hawkins updated TEIID-251:
---------------------------------
Original Estimate: 2 days
Remaining Estimate: 2 days
Component/s: Query Engine
Fix Version/s: 6.1.0
Affects Version/s: 6.0.0
Affects: [Documentation (Ref Guide, User Guide, etc.), Release Notes]
Complexity: Medium
Support should be taken all the way down to the connector level.
> Support SQL 2003 order by with expressions
> ------------------------------------------
>
> Key: TEIID-251
> URL: https://jira.jboss.org/jira/browse/TEIID-251
> Project: Teiid
> Issue Type: Feature Request
> Components: Query Engine
> Affects Versions: 6.0.0
> Reporter: Steven Hawkins
> Priority: Optional
> Fix For: 6.1.0
>
> Original Estimate: 2 days
> Remaining Estimate: 2 days
>
> Defect Tracker #25000: SQL 2003 allows the order by clause to contain expressions instead of just simple simple symbol names. Since we already support expressions in the group by clause (which is actually against the SQL spec), it would make since to support expressions in the order by as well.
--
This message is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of the administrators: https://jira.jboss.org/jira/secure/Administrators.jspa
-
For more information on JIRA, see: http://www.atlassian.com/software/jira
15 years, 10 months
[JBoss JIRA] Updated: (TEIID-270) Simplify SessionService
by Steven Hawkins (JIRA)
[ https://jira.jboss.org/jira/browse/TEIID-270?page=com.atlassian.jira.plug... ]
Steven Hawkins updated TEIID-270:
---------------------------------
Component/s: Server
Affects: [Documentation (Ref Guide, User Guide, etc.), Compatibility/Configuration, Release Notes] (was: [Documentation (Ref Guide, User Guide, etc.)])
> Simplify SessionService
> -----------------------
>
> Key: TEIID-270
> URL: https://jira.jboss.org/jira/browse/TEIID-270
> Project: Teiid
> Issue Type: Task
> Components: Server
> Affects Versions: 6.0.0
> Reporter: Steven Hawkins
> Assignee: Steven Hawkins
> Fix For: 6.0.0
>
> Original Estimate: 3 days
> Remaining Estimate: 3 days
>
> The SessionService currently relies upon a database to store sessions and also maintains a history of old sessions up to a configurable amount of days.
> It would simply things to:
> Remove the database in favor of a JBossCache cache and to not maintain a history. Logs would still be made on ping timeout, session expiration, and session termination.
> Make the ping functionality non-configurable, rather it would just be a built-in application level protocol for detecting invalid connections.
--
This message is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of the administrators: https://jira.jboss.org/jira/secure/Administrators.jspa
-
For more information on JIRA, see: http://www.atlassian.com/software/jira
15 years, 10 months
[JBoss JIRA] Closed: (TEIID-270) Simplify SessionService
by Steven Hawkins (JIRA)
[ https://jira.jboss.org/jira/browse/TEIID-270?page=com.atlassian.jira.plug... ]
Steven Hawkins closed TEIID-270.
--------------------------------
The doc and config changes will be handled as part of JBEDSP-830
> Simplify SessionService
> -----------------------
>
> Key: TEIID-270
> URL: https://jira.jboss.org/jira/browse/TEIID-270
> Project: Teiid
> Issue Type: Task
> Components: Server
> Affects Versions: 6.0.0
> Reporter: Steven Hawkins
> Assignee: Steven Hawkins
> Fix For: 6.0.0
>
> Original Estimate: 3 days
> Remaining Estimate: 3 days
>
> The SessionService currently relies upon a database to store sessions and also maintains a history of old sessions up to a configurable amount of days.
> It would simply things to:
> Remove the database in favor of a JBossCache cache and to not maintain a history. Logs would still be made on ping timeout, session expiration, and session termination.
> Make the ping functionality non-configurable, rather it would just be a built-in application level protocol for detecting invalid connections.
--
This message is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of the administrators: https://jira.jboss.org/jira/secure/Administrators.jspa
-
For more information on JIRA, see: http://www.atlassian.com/software/jira
15 years, 10 months