SQL Backend can't parse URL

[Mark Johnson]

I have built trunk rev 17855 with the wrong configure options.  I 
accidentally used the old --enable-gda instead of the correct 
--enable-dbi.  The file menu has a Database Connection option and when I 
filled in its dialog's fields and clicked OK, I got a "can't parse URL 
error".

If I haven't enabled the dbi backend, should this menu option even be there?

Here is the relevant portion of gnucash.trace:
* 07:22:41 DEBUG <qof.session> [enter qofsession.c:qof_session_begin()]  
sess=0x8512e68 ignore_lock=0, 
book-id=postgres://localhost:gnucash:gnucash_user:kirk
* 07:22:41 DEBUG <qof.session>     [enter 
qofsession.c:qof_session_load_backend()]  list=6, initted=true
* 07:22:41  INFO <qof.session>         [qof_session_load_backend]  
selected GnuCash Libdbi (POSTGRESQL) Backend
* 07:22:41  INFO <gnc.backend.dbi>         [init_sql_backend] -1 DBD 
drivers found
* 07:22:41 DEBUG <gnc.backend.sql>         
[gnc_sql_register_col_type_handler] Col type ct_string registered
* 07:22:41 DEBUG <gnc.backend.sql>         
[gnc_sql_register_col_type_handler] Col type ct_boolean registered
* 07:22:41 DEBUG <gnc.backend.sql>         
[gnc_sql_register_col_type_handler] Col type ct_int registered
* 07:22:41 DEBUG <gnc.backend.sql>         
[gnc_sql_register_col_type_handler] Col type ct_int64 registered
* 07:22:41 DEBUG <gnc.backend.sql>         
[gnc_sql_register_col_type_handler] Col type ct_double registered
* 07:22:41 DEBUG <gnc.backend.sql>         
[gnc_sql_register_col_type_handler] Col type ct_guid registered
* 07:22:41 DEBUG <gnc.backend.sql>         
[gnc_sql_register_col_type_handler] Col type ct_timespec registered
* 07:22:41 DEBUG <gnc.backend.sql>         
[gnc_sql_register_col_type_handler] Col type ct_gdate registered
* 07:22:41 DEBUG <gnc.backend.sql>         
[gnc_sql_register_col_type_handler] Col type ct_numeric registered
* 07:22:41 DEBUG <gnc.backend.sql>         
[gnc_sql_register_col_type_handler] Col type ct_commodityref registered
* 07:22:41 DEBUG <gnc.backend.sql>         
[gnc_sql_register_col_type_handler] Col type ct_accountref registered
* 07:22:41 DEBUG <gnc.backend.sql>         
[gnc_sql_register_col_type_handler] Col type ct_txref registered
* 07:22:41 DEBUG <gnc.backend.sql>         
[gnc_sql_register_col_type_handler] Col type ct_lotref registered
* 07:22:41 DEBUG <qof.session>     [leave qof_session_load_backend()] 
* 07:22:41 DEBUG <gnc.backend.dbi>     [enter 
gnc-backend-dbi.c:gnc_dbi_postgres_session_begin()] 
* 07:22:41  CRIT <gnc.backend.dbi>         
[gnc_dbi_postgres_session_begin()] Unable to create pgsql dbi connection
* 07:22:41 DEBUG <gnc.backend.dbi>     [leave 
gnc_dbi_postgres_session_begin()] 
* 07:22:41  INFO <qof.session>     [qof_session_begin] Done running 
session_begin on backend
* 07:22:41 DEBUG <qof.session> [leave qof_session_begin()]  backend 
error 3 (null)
*

It seems odd to me that it is loading a postgresql backend, when I did 
not specify --enable-dbi.

Mark