You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
It makes sense that we don't allow a standard Bean to be returned as that would infer that use of Store() or Trash() are valid.
The RowToBean method is therefore useful here, but I'd like to profile the performance like for like.
If internal Bean creation is faster than we should create a QueryBean subclass or similar which Limebean knows not to try and store, and Kind == "" and can't be changed.
The text was updated successfully, but these errors were encountered:
Nick-Lucas
changed the title
Allow a Bean to be return by general queries (ie. RowsIterator(...))
Allow a Bean to be returned by general queries (ie. RowsIterator(...))
Jul 4, 2016
It makes sense that we don't allow a standard Bean to be returned as that would infer that use of Store() or Trash() are valid.
The RowToBean method is therefore useful here, but I'd like to profile the performance like for like.
If internal Bean creation is faster than we should create a
QueryBean
subclass or similar which Limebean knows not to try and store, andKind == ""
and can't be changed.The text was updated successfully, but these errors were encountered: