dbt1 PostGres kit

Engineers at BULL.NET has ported dbt1 to PostGreSQL.
Satoshi Nagayasu and his team is reviewing/improving it. Before we merge it to the orginal dbt1 kit, it is available as a tarball release.

> I list below different remarks on our work and modifications on DBT1
> sources :
>
> 1. As we did not find any history in the source files, we have written
> in some header comment our Names. The goal is to confirm the Bull
> image as a contributor on Open Source Software.
> 2. The main difficulties to port DBT1 on PostgreSQL is linked to the
> fact that PL/pgSQL doesn't support OUT parameters in stored
> functions. So, we have chosen to slide some Transaction code from
> the Stored Proc to C / ODBC code in "interfaces/odbc". But there
> are at least 2 others solutions :
> o Use PL/pgSQL functions which return cursors. We try that, it
> could work on the PL/pgSQL but we have been blocked on ODBC.
> We haven't found how to return cursor through ODBC API.
> o Generate temporaries tables for the results of SELECT
> instructions. We haven't chosen this solution as it change the
> Transaction to the Spec clauses.
> 3. As our goal is to evaluate PostgreSQL, so, we don't use the DBT1
> Server Cache functions.
> 4. In PostgreSQL there aren't the built-in function addtime() and
> adddate() which exist in SAPDB. We have created one : addTime(J
> HH:MI:SS), i put it in the storedproc but until now, we use
> PostgreSQL built-in function tomorrow() and current_date(). See the
> files : InsertCust.sql, updateCustInfo.sql, and buyconfirm.sql.
> 5. Please note that appServer and dbdriver_p2 have to be launch with
> "PostgreSQL" privileges (DBA). Other users cause errors. We haven't
> yet identified why.
> 6. In include/common.h the macro SHOPPING_CART_MAX has changed from 20
> to 10. The reason is that the maximum number of parameters in a
> PL/pgSQL is 32.
> 7. ODBC driver. We use UNIXODBC 2.2.4 driver and programs are linked
> to libodbcpsql.so
> 8. Datagen : we have limited the a_string_char to the alpha numeric
> chars as other chars ('~?./+-[]{} ...) have special meaning in
> PostgreSQL. So, common.h and common.c have been modified. I would
> suggest you also, to give to ability to generate the *.data file in
> an other file system. Big database could lead to block the
> generating process due to the FS size.
>
> Please, fell free to ask me questions if something does not work.