It was partially fixed in the last commit, but the database needed to be updated to support the value as well. The archive maintainers will need to alter their tables to allow the value D be inserted in the capcode column. Depending on the size of the board, it may take a couple of minutes to a few hours. I would suggest changing the data type for the capcode column to varchar(1) in case moot feels the need to add another capcode in the future.
It was partially fixed in the last commit, but the database needed to be updated to support the value as well. The archive maintainers will need to alter their tables to allow the value
Dbe inserted in the capcode column. Depending on the size of the board, it may take a couple of minutes to a few hours. I would suggest changing the data type for the capcode column tovarchar(1)in case moot feels the need to add another capcode in the future.(Issue #61)