The schema change to implement 0017766 did not assign the standard table options to the CreateTableSQL statement

array(

'mysql' => 'ENGINE=MyISAM DEFAULT CHARSET=utf8',

'pgsql' => 'WITHOUT OIDS' )

)

This will most likely not be a problem for MySQL since the plan is to move away from the MyISAM engine, and the charset will be inherited from global database settings.

We need to fix this for PostgreSQL however.

Unfortunately, AFAIK the ADOdb data dictionary does not let us alter table options, so it's not possible to do this cleanly without dropping the table and recreating it. That implies

• create new table with correct structure
• migrate data from old table to new
• drop old table
• rename new table

Alternatively, as the presence of an OID field is unlikely to cause any significant issues in Mantis, we could go with a more simple approach of updating upgrade step 200 as appropriate.

Considering the market share of postgresql, I would be tempted to go with the 2nd approach.