midsuit
/
core-jgi
1
0
Fork 0
Code Issues Pull Requests Packages Projects Releases Wiki Activity

IDEMPIERE-4087 Virtual search columns / enable the usage of @SQLFIND= columns in reports / update field Description

This commit is contained in:
Carlos Ruiz 2019-12-04 20:54:13 +01:00
parent 570875e74b
commit 8c3af7914e
4 changed files with 32 additions and 3 deletions
Show Stats Download Patch File Download Diff File Expand all files Collapse all files

15
migration/i7.1/oracle/201912042002_IDEMPIERE-4087.sql Normal file
View File

@ -0,0 +1,15 @@
SET SQLBLANKLINES ON
SET DEFINE OFF
-- IDEMPIERE-4087 Copy the link to this issue virtual search columns
-- Dec 4, 2019, 8:01:25 PM CET
UPDATE AD_Field SET Help='You can define virtual columns (not stored in the database). If defined, the Column name is the synonym of the SQL expression defined here. The SQL expression must be valid.<br>
Example: "Updated-Created" would list the age of the entry in days.<br>
It is not recommended to add complex queries in virtual columns as the impact on the database performance can be too expensive.<br>
However, you can use the prefix @SQLFIND= for virtual columns that can be used for queries and reports, they have less impact on the database, but as a field they don''t show values.<br>
Additionally, the prefix @SQL= allows to define a virtual UI column, this is calculated on the fly and can use context variables in the query, virtual UI columns are shown in grid just on the current row, they are not searchable, and not shown in reports.', AD_Reference_Value_ID=NULL, AD_Val_Rule_ID=NULL, IsToolbarButton=NULL,Updated=TO_DATE('2019-12-04 20:46:15','YYYY-MM-DD HH24:MI:SS'),UpdatedBy=100 WHERE AD_Field_ID=11264
;
SELECT register_migration_script('201912042002_IDEMPIERE-4087.sql') FROM dual
;

12
migration/i7.1/postgresql/201912042002_IDEMPIERE-4087.sql Normal file
View File

@ -0,0 +1,12 @@
-- IDEMPIERE-4087 Copy the link to this issue virtual search columns
-- Dec 4, 2019, 8:01:25 PM CET
UPDATE AD_Field SET Help='You can define virtual columns (not stored in the database). If defined, the Column name is the synonym of the SQL expression defined here. The SQL expression must be valid.<br>
Example: "Updated-Created" would list the age of the entry in days.<br>
It is not recommended to add complex queries in virtual columns as the impact on the database performance can be too expensive.<br>
However, you can use the prefix @SQLFIND= for virtual columns that can be used for queries and reports, they have less impact on the database, but as a field they don''t show values.<br>
Additionally, the prefix @SQL= allows to define a virtual UI column, this is calculated on the fly and can use context variables in the query, virtual UI columns are shown in grid just on the current row, they are not searchable, and not shown in reports.', AD_Reference_Value_ID=NULL, AD_Val_Rule_ID=NULL, IsToolbarButton=NULL,Updated=TO_TIMESTAMP('2019-12-04 20:46:15','YYYY-MM-DD HH24:MI:SS'),UpdatedBy=100 WHERE AD_Field_ID=11264
;
SELECT register_migration_script('201912042002_IDEMPIERE-4087.sql') FROM dual
;

4
org.adempiere.base/src/org/compiere/print/DataEngine.java
View File

@ -310,7 +310,9 @@ public class DataEngine
int AD_Column_ID = rs.getInt(1); int AD_Column_ID = rs.getInt(1);
String ColumnName = rs.getString(2); String ColumnName = rs.getString(2);
String ColumnSQL = rs.getString(24); String ColumnSQL = rs.getString(24);
if (ColumnSQL != null && ColumnSQL.length() > 0 && (ColumnSQL.startsWith("@SQL=") || ColumnSQL.startsWith("@SQLFIND="))) if (ColumnSQL != null && ColumnSQL.length() > 0 && ColumnSQL.startsWith("@SQLFIND="))
ColumnSQL = ColumnSQL.substring(9);
if (ColumnSQL != null && ColumnSQL.length() > 0 && ColumnSQL.startsWith("@SQL="))
ColumnSQL = "NULL"; ColumnSQL = "NULL";
if (ColumnSQL != null && ColumnSQL.contains("@")) if (ColumnSQL != null && ColumnSQL.contains("@"))
ColumnSQL = Env.parseContext(Env.getCtx(), -1, ColumnSQL, false, true); ColumnSQL = Env.parseContext(Env.getCtx(), -1, ColumnSQL, false, true);

4
org.adempiere.base/src/org/compiere/print/MPrintFormat.java
View File

@ -615,7 +615,7 @@ public class MPrintFormat extends X_AD_PrintFormat
int seqNo = 1; int seqNo = 1;
for (GridField gridField : gridFields) for (GridField gridField : gridFields)
{ {
if (gridField.isVirtualUIColumn() || gridField.isVirtualSearchColumn()) if (gridField.isVirtualUIColumn())
continue; continue;
MPrintFormatItem pfi = MPrintFormatItem.createFromGridField(pf, gridField, seqNo++); MPrintFormatItem pfi = MPrintFormatItem.createFromGridField(pf, gridField, seqNo++);
if (pfi != null) if (pfi != null)
@ -878,7 +878,7 @@ public class MPrintFormat extends X_AD_PrintFormat
{ {
int columnID = rs.getInt(1); int columnID = rs.getInt(1);
MColumn column = MColumn.get(ctx, columnID); MColumn column = MColumn.get(ctx, columnID);
if (column.isVirtualUIColumn() || column.isVirtualSearchColumn()) if (column.isVirtualUIColumn())
continue; continue;
MPrintFormatItem pfi = MPrintFormatItem.createFromColumn (format, columnID, seqNo++); MPrintFormatItem pfi = MPrintFormatItem.createFromColumn (format, columnID, seqNo++);
if (pfi != null) if (pfi != null)