Pcounter value not kept correctly between project description changes

When updating a project description, the value for pcounter (the next issue key) is reset.

Steps to reproduce:

1. Determine the current pcounter settings using a query like the following:

   Project created-
   jira401=> select description,pcounter from project;
    description | pcounter 
   -------------+----------
    first desc  |        0
   (1 row)

2. Add two issues to the project and check the settings again using a query like:

   jira401=> select description,pcounter from project;
    description | pcounter 
   -------------+----------
    first desc  |        2
   (1 row)
   

3. Change the project description field and check the pcounter value again:

   jira401=> select description,pcounter from project;
    description | pcounter 
   -------------+----------
    second desc |        0
   (1 row)
   

4. Add an issue after the project description is changed and check the value again:

   jira401=> select description,pcounter from project;
    description | pcounter 
   -------------+----------
    second desc |        3
   (1 row)
   

When adding the issue, warnings like the following will appear in the logs:

2009-12-23 07:57:59,697 http-8080-Processor22 ERROR jcurry 28679x78x1 12g2otk http://localhost:8080/secure/CreateIssueDetails.jspa [atlassian.jira.project.DefaultProjectManager] Existing issue found for key TEST-1. Incrementing key.
2009-12-23 07:57:59,700 http-8080-Processor22 ERROR jcurry 28679x78x1 12g2otk http://localhost:8080/secure/CreateIssueDetails.jspa [atlassian.jira.project.DefaultProjectManager] Existing issue found for key TEST-2. Incrementing key.