#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 wimh):
I think you miss my point.
I have read bep:0010 and I confirm it is implemented when I install
bloodhound using sqlite.
However when I use PostgreSQL, it is not and using the previous ticket
numbering system. For me it is hard to believe that it bloodhound
installations using sqlite and postgres are incompatible. It means it will
never be possible to upgrade from sqlite to postgres. Nowhere in bep:0010
I read that it is a sqlite-only feature. It is even discussed how to
implement this in postgres. Finally in wiki:BloodhoundInstall it is
recommented to use postgresql. Then why not implement bep:0010 for
postgresql too? Otherwise you should recommend to use sqlite as it has
more features.
Should I change the title of this ticket to "BEP-0010 is not implemented
for PostgreSQL installations"?
--
Ticket URL: <https://issues.apache.org/bloodhound/ticket/806#comment:5>
Apache Bloodhound <https://issues.apache.org/bloodhound/>
The Apache Bloodhound issue tracker
