 |
I am suspecting this bug maybe related to the upgrade of ADODB. You might want to try getting the ADODB version that is shipped with 1.0.6, put it in 1.1.0a1 and then try installing. |
 |
Replaced directory adodb in core with the one from 1.0.6. Installation works now, but Database needs to be created manually with mantis user assigned full rights to DB. Now I get an error when creating a new user stating that Sequence 'mantis_email_table_id_seq' does not exist. In pgAdmin I found a Sequence 'mantis_email_table_email_id_seq' instead. After manually creating the first Sequence I get the following Message: "Database query failed. Error received from database was #-1: ERROR: currval of sequence "mantis_email_table_id_seq" is not yet defined in this session for the query: SELECT currval('mantis_email_table_id_seq')" Looks like some inconsistent naming to me. |
 |
Hi, The problem is that PostgreSQLsequences are created like tablename_primarykeyname_seq for serial fields which for the mantis_email_table table gives us mantis_email_table_email_id_seq. It's not consistent with the code in db_insert_id which adds a id_seq to the name of the table so it requires the following name for the sequence: mantis_email_table_id_seq. The current code and schema have the following behaviour:
IMHO the only way to fix this problem without changing too much the existing API is to rename the email_id field of mantis_email_table to id. So that the sequence created by PostgreSQL will be named mantis_email_table_id_seq. Any comment? |
|
|
Agreed that the easiest fix would be to rename the email_id field to id. |
|
|
I think we should use the fix on the following forum thread: |
 |
Fix certainly helps... $150 for you if you solve PosgreSQL related problems... |
 |
This fix worked for me as well, mantis 1.1.1, pgsql 8.2. Would love to see it get rolled into the main package. |
 |
Hello all, I think most of the postgres issues have been resolved in the latest SVN trunk from http://mantisbt.svn.sourceforge.net/viewvc/mantisbt/trunk/mantisbt/ [^] If one of you could test the latest SVN code to see if it improves the support for postgres, it would be appreciated. Paul |
 |
testing 1.1.2 on gentoo... doesn't work... part of it seems to be in the create tables when the column is type BOOL the DEFAULT should be '0' not 0 as it is representative of the character not the integer. the value FALSE would also work. |
 |
The same error exists in 1.2.0a1. |
 |
Hello I'm new to Mantis. We testing it against PostgreSQL 8.2 for future production deployment. I'm still studying how Mantis is designed and how it works, but I've created and attached patch which fixes most problems with 'Manage Users'. But especially that bool problem is more related to adodb than mantis database_api.php I think (but I've fixed it in database_api.php). Excuse my English and dirty places in patch. It's against latest trunk from svn. |
 |
Is there a nicer fix than the one from forums? If not I could probably look at it and post a patch... |
 |
@blami: (about the attached patch) db_prepare_bool() can't return true/false because boolean fields that were created sometimes prior to 1.2 are in the database as type smallint (see 0009806:0019866). I propose returning strings "'0'" and "'1'" which works for both boolean's and smallint's. But then all the code needs to be scrubbed to eliminate usage like this, from filter_api.php, filter_db_get_available_queries(): (db_prepare_bool() should ONLY be used to construct a query; and only be called with one argument, not two like in filter_db_set_for_current_user() in the same file, but I digress...) [the code I'm commenting on is svn r5751] Alternatively, the change to real true/false can be made in the next major release, with the installer changing types from smallint to boolean. And conversely, anyone having a problem with booleans now, can change the type to smallint, which seems to work for me: ALTER TABLE t ALTER COLUMN b TYPE smallint USING CASE WHEN b THEN 1 WHEN NOT b THEN 0 ELSE null END; |
|
|
I think current 1.2.0 git trunk fixes most pgsql issues. I'm currently running my dev instance of mantis on a pgsql db. Paul |
|
|
Hello all, The latest nightly builds at http://www.mantisbt.org/builds/ should fix most of the postgres issues Let me know how you get on. THanks |
|
|
Paul, what about 0009720? |
 |
Hi, The nightly builds do not fix my problems. I can get the thing to create tables by changing a lot of lines in admin/schema.php: L NOTNULL DEFAULT '1' -> L NOTNULL DEFAULT true But this breaks the file for mysql |
|
|
The attached file ncmichiel_7616.diff fixes the issue of table creation in mantis 1.1.6 Works for postgresql and mysql |
|
|
ncmichiel, Which nightly build file are you trying to use? Paul |
|
|
I tried nightly build mantisbt-1.1.6-2009-04-15-master Just tested against git trunk, all works fine there. |
 |
'mantisbt-svn5752.register-user-on-postgresql.patch' - reworked 'fix_user_management.diff' patch to current SVN revision. New user registering work fine, but password request still broken. 'mantisbt-svn5752.lost_pwd.patch' - fixed password requests. |
|
|
Ok. I've tested it only-that on 'mantisbt-1.2.0a3'. In this version all work fine without any patches. Thank you. |
|
|
Note: development moved to git ( http://git.mantisbt.org/ ) so svn 5752 is about 6 months out of date. Paul |
|
|
Marking this as resolved - pgsql support should be fine in 1.2 rc Paul |
|
|
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 |
- Anonymous
