Limitations of row queries

Row queries have the following limitations:

Result values are not part of object domain graphs

You cannot use object path notation with values in results from row queries. The values in results from row queries are not part of object domain graphs.

Access only to columns and foreign keys

You can access only values of columns and foreign keys with row queries. To access values of virtual properties, or properties of entities through arrays or one-to-ones, you must use entity queries, additional queries, or bundles.

Result values are not in the application cache

Values in the result are in local memory only. The application cache does not contain the results.

Results cannot be updated

You cannot update the database with changes that you make to data returned by a row query.

Incompatible with list views or detail panels

The columns in a row in a row query result do not have properties that the PolicyCenter user interface can access. You must transform the row query results to another type before using them as data sources for list views or detail panels in page configuration files.

See also

• Transforming results of row queries to other types
• Comparison of entity and row queries
• Performance differences between entity and row queries

Limitations of MonetaryAmount objects in aggregate queries

The MonetaryAmount object encapsulates two main properties: Amount, a BigDecimal that contains a numeric value, and Currency, a Currency object. You can use MonetaryAmount objects in ordering, column comparisons, and constant comparisons.

If you want to use aggregate functions such as Avg, Count, Min, Max, and Sum, be aware of the following:

• MonetaryAmount objects cannot be used in aggregate functions.
• The individual properties MonetaryAmount.Amount and MonetaryAmount.Currency are normal properties for the query builder APIs. For example, you can use Sum on the MonetaryAmount.Amount property, or use Count on the MonetaryAmount.Currency property.