Mantis Bug Tracker - Forums

Which means that this must be happening to everyone, right? Not right, as I wrote: My test update was OK ALTER TABLE mantis_bug_table CHANGE COLUMN date_submitted_int date_submitted INTEGER UNSIGNED NOT NULL DEFAULT 1; Where did you find this statement? I find the following code, which seems to be ...

I made a test upgrade of one of my installations from 1.1.6 to 1.2.2 and don't see this problem.
Do you use PostgreSQL?
There is a known bug for this http://www.mantisbt.org/bugs/view.php?id=9088

Seems that you use IIS?
I am no specialist for this, but comparing CGI and ISAPI to run PHP is worth a try

mzainal wrote: What i worried is the structure of database. Is it same as version 1.0.7?

No it isn't the same.
But if you follow the upgrade instructions (for example read doc/INSTALL) the database structure will be migrated

You should use the latest stable version of MantisBt which is 1.2.2 at the moment.
It makes not much sense to look for problems in your 1.2.0

joujoukinder wrote: So I have to correct the code on my own and what fir the issue to be corrected on the next version right ?

Yes

nbarrocas wrote:Or do I have to wait for 1.2.3 with the fixed install.php?

The mentioned fix does not fix anything related to date fields

Related to
http://www.mantisbt.org/bugs/view.php?id=10873

This feature is still on the todo list
http://www.mantisbt.org/bugs/view.php?id=10504

There is a database abstraction layer which is used by MantisBT (adodb) which does support Oracle.
So Oracle should work. But none of the core developers uses Oracle.
Seeing for example this http://www.mantisbt.org/bugs/view.php?id=12150 I think Oracle is not the best choice for MantisBT.

This is a known feature request, but not implemented in current version.
Someone provided a patch for this, but this was for an older version of MantisBT
http://www.mantisbt.org/bugs/view.php?id=5278

Seems that someone (you, your provider?) has disabled this function in php.ini with directive disable_functions

add the following line to config_inc.php (or maybe UPDATER instead of REPORTER)