|
|||||||||
| PREV CLASS NEXT CLASS | FRAMES NO FRAMES | ||||||||
| SUMMARY: NESTED | FIELD | CONSTR | METHOD | DETAIL: FIELD | CONSTR | METHOD | ||||||||
java.lang.Objecttoolkit.db.api.FormulaInfo
public class FormulaInfo
Class FormulaInfo wraps some information of related formulas.
| Method Summary | |
|---|---|
java.lang.String |
getExpression()
Gets the expression of this FormulaInfo. |
java.lang.String |
getMappingName()
Gets the name of this FormulaInfo. |
java.lang.String |
getValue()
Gets the value of this FormulaInfo. |
boolean |
isNonSQLCriterion()
Deprecated since v6.1. |
java.lang.String |
toString()
Returns a string representing this FormulaInfo's values. |
| Methods inherited from class java.lang.Object |
|---|
equals, getClass, hashCode, notify, notifyAll, wait, wait, wait |
| Method Detail |
|---|
public java.lang.String getValue()
public java.lang.String getMappingName()
public java.lang.String getExpression()
public boolean isNonSQLCriterion()
return @"Customers_Customer ID";
It is easy to translate it into Customers.`Customer ID` and it is also valid to form a valid SQL criterion like:
Customers.`Customer ID` = 15;
So if this formula is inserted in SQL criterion, we call it an SQL criterion formula. But for other complex formulas, for example, for formulas containing "if else" statements, they can not be contained in the final SQL string. If inserting such a complex formula in SQL criterion, we call it a non-SQL criterion formula. Non-SQL criterion formulas are handled in JReport, so users do not need to handle criteria containing non-SQL criterion formulas when creating SQL string.
public java.lang.String toString()
className@hashCode[ mappingName | expression | isNonSQLCriterion ]
toString in class java.lang.Object
|
|||||||||
| PREV CLASS NEXT CLASS | FRAMES NO FRAMES | ||||||||
| SUMMARY: NESTED | FIELD | CONSTR | METHOD | DETAIL: FIELD | CONSTR | METHOD | ||||||||