#806: default installation results in different ticket numbering depending on
database
---------------------------+----------------------
Reporter: wimh | Owner: nobody
Type: defect | Status: closed
Priority: major | Milestone:
Component: multiproduct | Version: 0.8.0dev
Resolution: wontfix | Keywords: ticket
---------------------------+----------------------
Comment (by olemis):
I see your point . Nevertheless afaict there is no problem upgrading
sqlite DB to PostgreSQL . Database schema supports consecutive ticket ID
sequences in PostgreSQL as well . AFAICR the fact is that SQLite and MySQL
generate product-specific IDs in code (as explained in bep:0010, since
they the backend does not support multiple autoinc columns) whereas in
PostgreSQL this value is generated directly by the database .
Saying that ''bloodhound installations using sqlite and postgres are
incompatible.'' is not completely accurate , even if that seems to be the
case . If you migrate an environment from SQLite -> PostgreSQL -> MySQL
then what you'll notice is that consecutive product IDs will be used up-to
a given point , that will change after first migration , and revert back
to consecutive IDs after second migration . No harm will be done , no need
to fill the gaps .
--
Ticket URL: <https://issues.apache.org/bloodhound/ticket/806#comment:6>
Apache Bloodhound <https://issues.apache.org/bloodhound/>
The Apache Bloodhound issue tracker
