> This is normal and not an error!!! > > The first line (DBD::Pg::st execute failed ...) is a test to determine > the existence of the table because the initialization doesn't run in > FORCE-mode. Please look into the script generateCADB. The second line > (NOTICE: ...) is only a warning that the database creates an own primary > key where it is not established by the "create table"-statement. So no > real error occurs.
Aha, I see. > > > I also had to comment out hte block of code in OpenCA::DBI that referred to > > DB2 and used DBD::DB2::Constants, as I don't have a DB2 system (using > > postgres here). > > This should be fixed on the cvs since several weeks. I think > Massimiliano uses an old version to build the snap. The debugging output > which shows some variables which are relevant for DB2 are no problem for > other databases. Okay. > If you still have problems you can try two different version from the > CVS: > * openca/openca-dbi > * openca/openca-0.9/src/modules/openca-dbi but here you must fix several > things > + check one of the conf-files in > openca/openca-0.9/src/cgi-bin/cgi-*/conf/DBI.conf.in (new structure) > + copy the initDBI (openca/openca-0.9/src/cgi-bin/cgi-*/lib/initDBI > > OpenCA::DBI uses a debuggingswitch in DBI.conf. So if there are problems > please use the switch and send the output to me. This will help a lot. Great -- I'll try configuring with these parts tonight. Do you recommend going with the CVS version, or fixing up the SNAP one by hand? thanks, --bob _______________________________________________ OpenCA-Devel mailing list [EMAIL PROTECTED] https://lists.sourceforge.net/lists/listinfo/openca-devel
