[GRASS-dev] Unused files

Moritz Lennert mlennert at club.worldonline.be
Tue Apr 17 10:14:24 EDT 2007


On 16/04/07 22:14, Glynn Clements wrote:
> Daniel Calvelo wrote:
> 
>>>  lib/db/dbmi_client/c_add_col.c    | db_add_column
>>>  lib/db/dbmi_client/c_bindupdate.c | db_bind_update
>>>  lib/db/dbmi_client/c_createdb.c   | db_create_database
>>>  lib/db/dbmi_client/c_delete.c     | db_delete
>>>  lib/db/dbmi_client/c_deletedb.c   | db_delete_database
>>>  lib/db/dbmi_client/c_drop_col.c   | db_drop_column
>>>  lib/db/dbmi_client/c_drop_index.c | db_drop_index
>>>  lib/db/dbmi_client/c_drop_tab.c   | db_drop_table
>>>  lib/db/dbmi_client/c_finddb.c     | db_find_database
>>>  lib/db/dbmi_client/c_insert.c     | db_insert
>>>  lib/db/dbmi_client/c_list_idx.c   | db_list_indexes
>>>  lib/db/dbmi_client/c_listdb.c     | db_list_databases
>>>  lib/db/dbmi_client/c_openinsert.c | db_open_insert_cursor
>>>  lib/db/dbmi_client/c_openupdate.c | db_open_update_cursor
>>>  lib/db/dbmi_client/c_update.c     | db_update
>>>  lib/db/dbmi_client/c_version.c    | db_gversion
>>>  lib/db/dbmi_client/printtab.c     | db_print_column_definition
>>>  lib/db/dbmi_client/printtab.c     | db_print_table_definition
>>>  lib/db/dbmi_driver/d_mkdir.c      | db_driver_mkdir
>> Aren't these template functions and files to develop new drivers?
> 
> No; they are the actual client-side DBMI interface.
> 
> I was surprised to find so many of them unused.

On 16/04/07 23:19, Markus Neteler wrote:
 > [ ... dbmi ...]
 > I feel that DBMI was left in the middle of its development,
 > in particular Radim was digging through and making it
 > functional (the needed parts). I have no idea which parts
 > can be savely abandoned.

If they have useful code in them and could be potentially
used, why not keep them and hope than someone picks things up ? Unless 
we decide either

- that implementing these functionalities as scripts as we are doing now 
is better or at least just as good (e.g. the v.db.* scripts), or

- that database management should be done via relevant db client 
programs (independent of GRASS) or db.execute.

Moritz




More information about the grass-dev mailing list