[task #15810] Database access configured in configuration files

[Mohammad Akhlaghi]

Update of task #15810 (project gnuastro):

        Percent Complete:                      0% => 10%                    

    _______________________________________________________

Follow-up Comment #1:

Based on this task, the database-specific settings are currently maintained in
separate source files, for example astron.c
<http://git.savannah.gnu.org/cgit/gnuastro.git/tree/bin/query/astron.c> (for
ASTRON), gaia.c
<http://git.savannah.gnu.org/cgit/gnuastro.git/tree/bin/query/gaia.c> (for
ESA's Gaia database), ned.c
<http://git.savannah.gnu.org/cgit/gnuastro.git/tree/bin/query/ned.c> (for NED)
and vizier.c
<http://git.savannah.gnu.org/cgit/gnuastro.git/tree/bin/query/vizier.c> (for
VizieR). A common structure is being found based on these early examples which
can be filled in a plain-text configuration file instead of hard-coded strings
in the code. 

As more databases are added, we can indeed define a configuration file format,
that query can parse upon execution. For example, if the user asks for the
'vizier' database, the Query program goes searching for the file
'astquery-vizier.conf' in the standard configuration file directories
<https://www.gnu.org/software/gnuastro/manual/html_node/Configuration-file-precedence.html>.
This configuration file will contain all the strings in the '.c' files above
and Query will use them to set the internal variables.

In this way, users can easily define their own databases that aren't even in
the standard Gnuastro build or customize the databases as they like (for
example setting short names for datasets that they use a lot).

    _______________________________________________________

Reply to this item at:

  <https://savannah.gnu.org/task/?15810>

_______________________________________________
  Message sent via Savannah
  https://savannah.gnu.org/