#3 Database Backend

[James A. Pattie]

Use a Database backend as a possible configuration
mechanism (the config file contents would be stored in
the database).

Look into being able to store the gathered info in a
database (instead of mailing it to the user). Do we
develop a format or do we allow the user to specify the
database, table and table schema that the data is to be
stored in?

We could say that all checkboxes are booleans, text
fields, select boxes, radio buttons, file uploads are
text fields. A file upload would have to be able to
handle 2+MB of data (potentially). We could require
that there is a field with the name of the form item in
the table and that is where that data goes.

What database systems do we support? PostgreSQL,
MySQL, ODBC, Oracle?

Do we still email notify the mailform admin that
someone submitted something? If so do we just provide
the counter number of that entry or do we have a link
(user specifiable) that points to a cgi script that
would display the gathered data for the user. The link
would have to have a %i or something in it that would
be substitued with the index of the entry. The cgi
script would be unique for each form being worked with
(It will not be included by default with the mailform).