web/wdoc/advanced_usage_schema_en.rst
author Christophe de Vienne <cdevienne@gmail.com>
Wed, 30 Apr 2014 08:07:59 +0200
changeset 9720 a7210c912507
parent 0 b97547f5f1fa
child 10218 5ebbaf713caf
permissions -rw-r--r--
[req.find] Use vreg.schema.eschema for eschema lookup If an etype is non-existant, using vreg.schema[etype] raises a confusing error complaining about a non-existing relation. This is because of the implementation of vreg.schema.__getitem__ that look first in entities and then in relations. Using directly vreg.schema.eschema restrict the lookup to etypes only, hence raises a meaningful error when the etype does not exist.

Schema of the data
------------------

First take a look at the data schema_ then try to remember that you are browsing
through a heap of data by applying stylesheets to the results of queries. This
site is not a content management system with items placed in folders. It is an
interface to a database which applies a view to retreived data.

.. _schema: schema