hi chris,
thanks for the tip. I got the initial certificates working by creating the table "sequence_csr".
In order to get the Batch Process Quick import working I had to also create:
sequence_global_id sequence_audittrail sequence_crr sequence_data
This was a bug in the reference handling. It is fixed on my computer not on CVS. Actually it is a little bit frustrating. If it works with MySQL then PostgreSQL has a problem and vice versa.
I am a bit confused why the Initialisation process did not create these tables.
Anyway, the bpCreatePin function works and I have lots of data now in the "data" table corresponding to my new users and PINS, e.g.
| 229504 | 25216 | BATCH_HASHED_PIN | NULL | NULL | NULL | 9f97e4bb37359dce6fb232239b748d4878f84107 |
Is it right that I have NULL values corresponding to "array_counter ", "content_type" and "int_content" ? These are the default values, but I would expect them to be poulated describing the otehr data in the table. I seem to remember in the old days, NULL values indicated an error.
NULL is no error. I only ignored it because it was clear for me which content type the field BATCH_HASHED_PIN has. I only introduced the other columns to have a clean design. You can add integer and character data. Arrays are also supported. Today we don't need it but I want a design which has not to be changed in the future.
From what I can see you have moved the old batch processor directory structure (e.g. "bp/private/purePIN") to the data base in the new set of tables "sequence_*". You also have a table "statemachine" which is doing the job of the old text file to maintain the status of each of the users/process.
sequence_* is only for sequence generation because MySQL has no sequence generators. The table data contains all the old file data.
Looking at the create_pin code, all references to the file system have been removed, and the work is done on the data base.
This looks good to me and is as we discussed it at the Workshop. Have you got any design notes that I can see ? As I don't really understand the "dummy" values in the sequence_* tables. It would be nice to understand what you are planning to do with these colunms.
I don't have any desing notes until now. If postgres and mysql work both then I write the documentation.
I also presume that the other new table "private" is for management of the private keys better when generated server side.
Correct.
Michael -- _______________________________________________________________
Michael Bell Humboldt-Universitaet zu Berlin
Tel.: +49 (0)30-2093 2482 ZE Computer- und Medienservice Fax: +49 (0)30-2093 2704 Unter den Linden 6 [EMAIL PROTECTED] D-10099 Berlin _______________________________________________________________
------------------------------------------------------- This SF.Net email is sponsored by: Sybase ASE Linux Express Edition - download now for FREE LinuxWorld Reader's Choice Award Winner for best database on Linux. http://ads.osdn.com/?ad_id=5588&alloc_id=12065&op=click _______________________________________________ OpenCA-Devel mailing list [EMAIL PROTECTED] https://lists.sourceforge.net/lists/listinfo/openca-devel
