Closed benmishkanian closed 8 years ago
Currently, Bicho doesn't support PostgreSQL and I'm afraid it won't be supported any time soon.
I see. Thank you for the response. I think it might be useful for other users if this missing functionality was documented in the project readme, or in the help description of --db-password-out.
I think it might be useful for other users if this missing functionality was documented in the project readme, or in the help description of --db-password-out.
I agree. Right now in README we have:
- mysqldb or psycopg2 or pysqlite2 (unstable with PostgreSQL; MySQL is recommended - default engine should be set to MYISAM)
I suggest that we change this, removing the references to psycopg2 (and maybe pysqlite2) and to PostgreSQL, and include a new text stating that the data is stored only in MySQL.
@sduenas what do you think? If you agree, I can do the change.
@benmishkanian sorry for the misunderstood, I didn't know that this was in the documentation.
@jgbarah go ahead, please
Done in a07cf9c31f6dba2b56b4c9b11518920675d3684b.
@benmishkanian please close if you think it is clear enough now.
Closing...
It seems that when using a JIRA backend, the output database must be MySQL, or else bicho crashes. For example, if I try to use postgresql:
I get this:
bugsdb is initialized by get_database(backend), which only returns something if opts.db_driver_out == "mysql". So when a different DB type is chosen, bugsdb is None and causes this crash.