My favorites | Sign in
Project Home Downloads Wiki Issues Source
New issue   Search
  Advanced search   Search tips   Subscriptions
Issue 76: DatabaseTableSource optimization
1 person starred this issue and may be notified of changes. Back to list
Project Member Reported by, Jan 14, 2009
DatabaseTableSource currently has very little optimization as far as
handling queries, thus forcing most of the queries to be handled by Rhino
by iterating through the table. Performance could be greatly improved if
more JSONQuery queries could be translated to SQL by this data source such
as translating nested property references to inner joins.
Apr 29, 2009
Project Member #1
(No comment was entered for this change.)
Labels: Component-Data-Source Effort-Large
Sign in to add a comment

Powered by Google Project Hosting