Currently we have views in the Grouper registry which are not used by Grouper itself, so if the views weren't there, its wouldn't affect the operation of the registry itself. However, we now have a need to use views in Grouper. Shilen added support for HSQL in the grouper ddl (views already were supported in Oracle, MySQL, and postgres). So going forward we will assume the registry runs in a database that supports views, and we will use views in Grouper when convenient. This will allow us to re-use sql logic, have simpler queries, and will make the registry more transparent to administrators. If administrators are going to use the views for their applications, it is probably a good idea to build a view on top of the grouper views (that do not start with grouper_ ) so that if things change you will know since your view wont compile, it will be easy to fix.