create table SAKAI_MESSAGE_BUNDLE statement missing in 2.8.0 conversion scripts
GENERAL
TESTING
GENERAL
TESTING
Description
The new SAKAI_MESSAGE_BUNDLE table added by KNL-563 is missing in the 2.8.0 Oracle conversion scripts. I've added it to the MySQL conversion scripts during my test/fix work as:
– KNL-563 table structure for sakai_message_bundle create table SAKAI_MESSAGE_BUNDLE ( ID bigint(20) not null auto_increment, MODULE_NAME varchar(255) not null, BASENAME varchar(255) not null, PROP_NAME varchar(255) not null, PROP_VALUE text, LOCALE varchar(255) not null, DEFAULT_VALUE text not null, primary key (ID) );
We need a statement written in the Oracle dialect.
Ok got word back from dba says my index is good and recommends going with varchar2 over clob for host of performance related issues, so we should go with whats in my last comment, and then your sequence as well.
Seth Theriault February 17, 2011 at 12:51 PM
Once your Oracle DBA reviews this, we'll put it in.
The new SAKAI_MESSAGE_BUNDLE table added by KNL-563 is missing in the 2.8.0 Oracle conversion scripts. I've added it to the MySQL conversion scripts during my test/fix work as:
– KNL-563 table structure for sakai_message_bundle
create table SAKAI_MESSAGE_BUNDLE (
ID bigint(20) not null auto_increment,
MODULE_NAME varchar(255) not null,
BASENAME varchar(255) not null,
PROP_NAME varchar(255) not null,
PROP_VALUE text,
LOCALE varchar(255) not null,
DEFAULT_VALUE text not null,
primary key (ID)
);
We need a statement written in the Oracle dialect.