-
When (visually) defining a query with multiple joins, the AND conditions are messed. For instance, defining a query such as:
SELECT *
FROM tabA
INNER JOIN tabB ON condition1 AND condition2
INNER JOIN tabC ON condition3
this may result in:
SELECT *
FROM tabA
INNER JOIN tabB ON condition1
INNER JOIN tabC ON condition3 AND condition2
Description
When (visually) defining a...
2009-12-22 16:34:33 UTC in SQLeonardo
-
http://jira.pentaho.com/browse/PRD-2374
The order of joins in the generated SQL code is not the same as in the definition in the visual editor. This can bring to a serious loss of performance (even preventing the execution of the query).
2009-12-16 01:07:14 UTC in SQLeonardo
-
Editing a previously defined (and working) query with Query Designer messes with columns aliases. So, for instance, when editing a query such as:
select field1, field2 as alias2, field3, field4, field5 as alias5 from table
it becomes:
select field1, field2 as alias2, field3 as alias2, field4 as alias2, field5 as alias5 from table
The alias for field2 is replicated for the following...
2009-12-11 11:44:29 UTC in SQLeonardo
-
taqua made 2 file-release changes.
2009-12-02 20:01:01 UTC in Pentaho Reporting
-
taqua made 1 file-release changes.
2009-12-02 20:00:01 UTC in Pentaho Reporting
-
taqua made 2 file-release changes.
2009-12-02 19:54:01 UTC in Pentaho Reporting
-
taqua made 2 file-release changes.
2009-12-02 19:51:01 UTC in Pentaho Reporting
-
In Reference to PRD-862:
nickyb.sqleonardo.querybuilder.DiagramLoader#getPrimaryKeys does not check whether the primary key returned is null. As the JavaDoc of java.sql.DatabaseMetaData#getPrimaryKeys states, column 6 can be null.
java.lang.NullPointerException
at java.util.Hashtable.put(Hashtable.java:632)
at. nickyb.sqleonardo.querybuilder.DiagramLoader.getPrimaryKeys...
2009-10-12 17:03:06 UTC in SQLeonardo
Thomas Morgner
