[JBoss JIRA] Created: (JBAS-4576) Include ORDER BY cols in SELECT clause in EJBQLToSQL92Compiler
by Michal Borowiecki (JIRA)
Include ORDER BY cols in SELECT clause in EJBQLToSQL92Compiler
--------------------------------------------------------------
Key: JBAS-4576
URL: http://jira.jboss.com/jira/browse/JBAS-4576
Project: JBoss Application Server
Issue Type: Bug
Security Level: Public (Everyone can see)
Affects Versions: JBossAS-4.0.5.GA
Environment: postgresql 8.2.4
Reporter: Michal Borowiecki
Bug JBAS-206 is still present in the EJBQLToSQL92Compiler.
For example this dynamic JBoss QL works fine with the default compiler:
select distinct object(o) from TransactionRO o where o.account.accountId = ?1 and o.date >= ?2 order by o.user.login desc offset 0 limit 25
After switching to the EJBQLToSQL92Compiler, an exception is raised on posgresql:
org.postgresql.util.PSQLException: ERROR: for SELECT DISTINCT, ORDER BY expressions must appear in select list
--
This message is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of the administrators: http://jira.jboss.com/jira/secure/Administrators.jspa
-
For more information on JIRA, see: http://www.atlassian.com/software/jira
19 years
[JBoss JIRA] Commented: (JBAS-206) Include ORDER BY cols in SELECT clause
by Michal Borowiecki (JIRA)
[ http://jira.jboss.com/jira/browse/JBAS-206?page=comments#action_12369744 ]
Michal Borowiecki commented on JBAS-206:
----------------------------------------
This bug is still present in the EJBQLToSQL92Compiler.
This dynamic JBoss QL works fine with the default compiler:
select distinct object(o) from TransactionRO o where o.account.accountId = ?1 and o.date >= ?2 order by o.user.login desc offset 0 limit 25
After switching to the EJBQLToSQL92Compiler, an exception is raised on posgresql:
org.postgresql.util.PSQLException: ERROR: for SELECT DISTINCT, ORDER BY expressions must appear in select list
> Include ORDER BY cols in SELECT clause
> --------------------------------------
>
> Key: JBAS-206
> URL: http://jira.jboss.com/jira/browse/JBAS-206
> Project: JBoss Application Server
> Issue Type: Bug
> Security Level: Public(Everyone can see)
> Components: CMP service
> Affects Versions: JBossAS-3.2.6 Final
> Reporter: SourceForge User
> Assigned To: Scott M Stark
> Fix For: Closed issues from sourceforge
>
>
> SourceForge Submitter: scoy .
> Some databases, Oracle in particular, require that columns named
> in an ORDER BY clause be included in the SELECT clause when
> SELECT DISTINCT is used.
> Here is some text from current Oracle documentation:
> Restrictions on the order_by_clause:
> * If you have specified the DISTINCT operator in this statement,
> then this clause cannot refer to columns unless they appear in the
> select list.
> * An order_by_clause can contain no more than 255 expressions.
> This can be worked around using on-find loading with load groups,
> but it sure would be useful if JBoss managed it for us.
--
This message is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of the administrators: http://jira.jboss.com/jira/secure/Administrators.jspa
-
For more information on JIRA, see: http://www.atlassian.com/software/jira
19 years
[JBoss JIRA] Created: (JBCACHE-1134) Consolidate delegating cache loader classes
by Galder Zamarreno (JIRA)
Consolidate delegating cache loader classes
-------------------------------------------
Key: JBCACHE-1134
URL: http://jira.jboss.com/jira/browse/JBCACHE-1134
Project: JBoss Cache
Issue Type: Task
Security Level: Public (Everyone can see)
Components: Cache loaders
Affects Versions: 1.4.1.SP3, 2.0.0.CR3
Reporter: Galder Zamarreno
Assigned To: Manik Surtani
Priority: Minor
Fix For: 2.0.0.CR4, 2.0.0.GA
In the org.jboss.cache.loader package, we have:
o.j.c.l.DelegatingCacheLoader and
o.j.c.l.AbstractDelegatingCacheLoader
The second one was created by me when I first created
SingletonStoreCL (doh!). I refactored common code
from AsyncCL to AbstractDelegatingCL and made
AsyncCL and SingletonStoreCL.
I have just spotted DelegatingCacheLoader which is
extended by LocalDelegatingCacheLoader and
TcpDelegatingCacheLoader.
We should try to consolidate, if possible, all delegating
cache loaders into one DelegatingCacheLoader interface
and an abstract implementation.
It'd be nice if this could be done by 2.0.GA, so setting that
fix version for the moment :). Otherwise, we'll have to leave it
for 3.0
--
This message is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of the administrators: http://jira.jboss.com/jira/secure/Administrators.jspa
-
For more information on JIRA, see: http://www.atlassian.com/software/jira
19 years
[JBoss JIRA] Created: (JBAS-4449) Remove deprecated attribute "PartitionName" from HAServiceMBean
by Brian Stansberry (JIRA)
Remove deprecated attribute "PartitionName" from HAServiceMBean
---------------------------------------------------------------
Key: JBAS-4449
URL: http://jira.jboss.com/jira/browse/JBAS-4449
Project: JBoss Application Server
Issue Type: Task
Security Level: Public (Everyone can see)
Components: Clustering
Reporter: Brian Stansberry
Assigned To: Brian Stansberry
Fix For: JBossAS-5.0.0.CR1
1) Remove deprecated attribute "PartitionName" from HAServiceMBean
This attribute is legacy code from the days before the legacy microkernel could do dependency injection. It's used to do a JMX lookup of the HAPartition. No reason to not just inject the HAPartition.
2) Add mbean attribute "HAPartition" of type HAPartition.
This is the type that HAServiceMBean impls really want. The "ClusterPartition" attribute just provides a way to provide the HAPartition via JMX injection.
--
This message is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of the administrators: http://jira.jboss.com/jira/secure/Administrators.jspa
-
For more information on JIRA, see: http://www.atlassian.com/software/jira
19 years
[JBoss JIRA] Created: (GPD-118) Infinite loop in ActionDomAdapter.createSemanticElementFor(XmlAdapter)
by John Ruud (JIRA)
Infinite loop in ActionDomAdapter.createSemanticElementFor(XmlAdapter)
----------------------------------------------------------------------
Key: GPD-118
URL: http://jira.jboss.com/jira/browse/GPD-118
Project: JBoss jBPM GPD
Issue Type: Bug
Affects Versions: jBPM JPDL Designer 3.1.0.beta2
Reporter: John Ruud
Assigned To: Koen Aers
In the 'else' statement below, (this.)createSemanticElementFor() is invoked instead of super.createSemanticElement(), and this is causing an infinite loop to occur. Several other subclasses of XmlAdapter got the same problem.
protected SemanticElement createSemanticElementFor(XmlAdapter child) {
if ("configInfoElement".equals(child.getElementType())) {
return getSemanticElementFactory().createById("org.jbpm.gd.jpdl.configInfoElement");
} else {
return createSemanticElementFor(child);
}
}
}
--
This message is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of the administrators: http://jira.jboss.com/jira/secure/Administrators.jspa
-
For more information on JIRA, see: http://www.atlassian.com/software/jira
19 years