Todo List

Global dui_libpg_init

translatable string not marked up

Global dui_libdbi_init

translatable string not marked up

Global dui_odbc_init

translatable string not marked up

Page Known problems

* The order in which signals are delivered can be ambiguous, resulting in out-of-order traversals, leading to unexpected results. Do something to clarify the order in which signals are submitted. (This has the greatest effect when e.g. the database connection signal is caught before the database paramters have been set, resulting in a failure to connect).

Page Known problems

* The <filter> element needs more work. The idea is to allow filters to be cascaced & custom filters to be created. In general, filters allow special data type input & handling, such as printing custom date values, or parsing and displaying custom currency strings.

Page Known problems

* add filter to check if a date field contains a valid date!

Page Known problems

* provide multiple simultaneous database support. This is needed for the GUI tool.

Page Known problems

* Provide a cascading chain for reporting errors (in particular, errors associated with a failed database conect. The cascade should allow a new user-login form to pop up, or have some other action be taken, if the connect to the DB fails.) Maybe the best way to do this is to have the DB object issue different signals for each of the failure modes?

Page Known problems

* Provide native postgres drivers so that ODBC is not needed.

Page Known problems

* Move the sql-builder code (builder.c) into the db-provider directory. The idea is to abstract the database interface a bit, allowing non-SQL data sources to be used.