Creates an example schema with three tables and a view:
contributor[contributor_id,name,country] (TABLE)
project[project_id,name,lines_of_code,parent_project_id] (TABLE)
role[contributor_id,project_id,role_name] (TABLE)
project_contributor[contributor,project,role] (VIEW)
The example schema is good for testing purposes and possess various
features of the schema model:
Relations between tables: one-Contributor-to-many-Role's and
many-Role's-to-one-Project
Recursive relations: A project can have a parent project
Views: The ProjectContributor view
Examines a query and extracts an array of FromItem's that refer
(directly) to tables (hence Joined FromItems and SubQuery FromItems are
traversed but not included).
A filter that is executed client-side because filter criteria are either more
dynamic than the Query-functionality offer or because it cannot be expressed
using datastore-neutral queries.
This class contains various helper functionality to common tasks involving
MetaModel, eg.:
Easy-access for traversing common schema items
Manipulate data in memory.
The QuerySplitter class makes it possible to split up queries that are
expected to yield a huge result set which may cause performance problems like
OutOfMemoryError's or very long processing periods.