#806: default installation results in different ticket numbering depending on
database
---------------------------+----------------------
Reporter: wimh | Owner: nobody
Type: defect | Status: new
Priority: major | Milestone:
Component: multiproduct | Version: 0.8.0dev
Resolution: | Keywords:
---------------------------+----------------------
Old description:
> after installing bloodhound (I use vagrant and a puppet based deployment
> script:
> https://github.com/wimh/bloodhound/blob/vagrant/installer/vagrant.puppet/puppet/manifests/site.pp),
> new tickets are numbered different depending on the database I have
> chosen.
> When I use PostgreSQL, every new ticket gets a new number, independent on
> the product. When I use mySQL, ticket numbers start at 1 for each
> product. So After I have created ticket {{{#1}}} for product ONE, and I
> create a new ticket for product TWO, it will be numbered {{{#2}}} when I
> use PostgreSQL, but {{{#1}}} if I use mySQL. I am not aware of any
> difference, so I expect both to behave the same.
New description:
after installing bloodhound (I use vagrant and a puppet based deployment
script:
https://github.com/wimh/bloodhound/blob/vagrant/installer/vagrant.puppet/puppet/manifests/site.pp),
new tickets are numbered different depending on the database I have
chosen.
When I use PostgreSQL, every new ticket gets a new number, independent on
the product. When I use sqlite, ticket numbers start at 1 for each
product. So After I have created ticket {{{#1}}} for product ONE, and I
create a new ticket for product TWO, it will be numbered {{{#2}}} when I
use PostgreSQL, but {{{#1}}} if I use sqlite. I am not aware of any
difference, so I expect both to behave the same.
--
Comment (by wimh):
correction, I meant sqlite vs PostgreSQL
--
Ticket URL: <https://issues.apache.org/bloodhound/ticket/806#comment:3>
Apache Bloodhound <https://issues.apache.org/bloodhound/>
The Apache Bloodhound issue tracker
