Active
Project:
OAI-PMH Module
Version:
6.x-1.3
Component:
Code
Priority:
Normal
Category:
Bug report
Assigned:
Unassigned
Reporter:
Created:
4 May 2011 at 13:18 UTC
Updated:
4 May 2011 at 13:32 UTC
I recently installed 6.x-1.3 and immediately I'm getting schema mismatch warnings. It seems that in the .install file in the oai2_install() function, you install the defined schema the normal way and then manually modify the oai2_tokens table with an SQL query. Is there a reason for this? (versus, say, fixing the schema and adding another oai2_update_n() function?)
function oai2_install(){
$result = array();
drupal_install_schema('oai2');
$result[] = update_sql("ALTER TABLE {oai2_tokens} MODIFY COLUMN timestamp TIMESTAMP ");
...
}
Comments
Comment #1
rjerome commentedThat's a very good question, unfortunately, I can't give a very good answer. I can only speculate that that dates back to the 4.x or 5.x versions (where for whatever reason) that column could not be made a timestamp initially.
All that being said, there is no reason that should still be there and I'll fix it.
Ron.