It appears from looking at the code and running test
cases against my database that SQLREST attempts to
build a complete meta data structure of the database.
This can be very expensive in terms of time (esp. if
the DB connection is remote) and resources for large
databases, which is the case for me.
Rather than constructing the meta data in an
initialization phase might I...
It might be nice if SQLREST would allow the
specification of mutiple DB sources so that it could
front end connectivity via a single HTTP end point to
these databases making it an integration interface
across multiple resources. At the same point it would
be useful to be able to specify the list of
tables/views which you would like published as
resources.
A config of the style:
Right now it appears that SQLREST derives the
resource definitions based on the TABLE structure of
the database. Often a database may contain
information about a single object in mutiple tables.
I would be nice to be able to manually control the
structure of the resources based on a configuration
file such as the following:
...
