View Issue Details
ID | Project | Category | View Status | Date Submitted | Last Update |
---|---|---|---|---|---|
0011572 | mantisbt | db postgresql | public | 2010-02-28 09:42 | 2015-03-25 17:50 |
Reporter | simtel | Assigned To | dregad | ||
Priority | normal | Severity | crash | Reproducibility | always |
Status | closed | Resolution | unable to reproduce | ||
Summary | 0011572: Error 401 when adding a note after upgrade from 1.1.x to 1.2.0 | ||||
Description | After upgrading from 1.1.x to 1.2.0, using PostgreSQL, everytime a note gets added to a project, the following error appears and the notification mail doesn't get sent: APPLICATION ERROR 0000401 Interrogazione database fallita. L'errore ricevuto dal database รจ #-1: ERROR: relation "mantis_email_table_email_id_seq" does not exist The DB contains the sequence mantis_email_table_id_seq which has not been renamed by the upgrade process | ||||
Tags | No tags attached. | ||||
Adding notes works fine for me with a fresh installation of MantisBT 1.3.x and PostgreSQL 8.4.2 Have you remembered to grant permission for your MantisBT user account to use the sequences? The best approach to setting up MantisBT database permissions is to first create a "MantisBT database admin" user that can create, destroy and alter tables. When installing MantisBT, you use this account. After installation you of course need to make a new user which only has the minimum set of permissions needed to use MantisBT. SELECT, INSERT, UPDATE, etc permissions on the tables and the appropriate permissions on the sequences too (don't forget this!). If you're still stuck, try recreating the primary key on mantis_email_table (the ID column). |
|
as I said, it's an upgrade problem. The upgrade process should have renamed the sequence. Probably it wasn't accessed directly in the 1.1.x series, or something else changed. Anyway, renaming the sequence solved my problem (but it won't solve it for other users that upgrade ;-) |
|
MantisBT currently supports Mysql and has support for other database engines. The support for other databases is known to be problematic. Having implemented the current database layer into Mantis 10 years ago, I'm currently working on replacing the current layer. If you are interested in using Mantis with non-mysql databases - for example, Oracle, PGSQL or MSSQL, and would be willing to help out testing the new database layer, please drop me an email at paul@mantisforge.org In the meantime, I'd advise running Mantis with Mysql Only to avoid issues. Thanks |
|
Reminder sent to: dregad, grangeway Not sure, maybe this issue should be moved back to project mantis. |
|
I was not able to reproduce this. Considering that there's an easy workaround anyway (manually renaming the sequence), I'm sure you'll agree that it's not really worth the effort to try and fix this. |
|