Forum OpenACS Development: LORS ORACLE port Issues

Collapse
1: LORS ORACLE port Issues
Posted by Mario Aguado on 06/29/06 01:20 PM
we, at UNED, are starting to port LORS package to Oracle.

First, we want to port lors, lorsm, lorsm-portlet and dotlrn-lorsm package. After it, we will port lors-central package.

The lorsm package need the views package and this need Oracle port also.

We have a problem with all packages and this is the datamodel compatibility. specially with the length of table name and the reserved words in ORACLE.
e.g.: The package views has a table with name views that can be create but the PL/SQL cannot compile if this table is in the code.

What do you recommend?.

We can rename the tables for ORACLE implementation, but maybe renaming and upgrading PostgreSQL implementation with ORACLE compatibility would be interesting.

Thanks in advance.

Collapse
2: Re: LORS ORACLE port Issues (response to 1)
Posted by Dave Bauer on 06/29/06 05:45 PM
We definitely have to coordinate the postgresql and oracle implementations.

Please post a list of table names that are a problem in Oracle and we can collaborate on upgrade scripts to keep Oracle and Postgresql implementations in line. I am working on adding new feaures to LORS to allow more management at the learning object level, and we want to keep this in sync. All the work I am doing is in CVS HEAD.

Collapse
3: Re: LORS ORACLE port Issues (response to 1)
Posted by Dave Bauer on 06/29/06 05:49 PM
I will write up all the new work on LORS in the wiki in the next few days. I am on vacation so it might be a little while.

Mainly we are colsolidating the user interface code between lorsm and lors-central so the same learning object management user interface between lorsm and lors-central.

Collapse
4: Re: Re: LORS ORACLE port Issues (response to 3)
Posted by Mario Aguado on 06/30/06 12:54 PM

Thanks Dave,

ORACLE have a limit of 30 characters for identifiers. I started three days ago to migrate LORS to ORACLE. These objects has more 30 characters or another issues:

  • Package view:
    • views table have a problem when I compile PL/SQL and insert data.
    • colunm views in views table. I cannot reference to it in PL/SQL code.
  • Package LORS
    • File: lors-imsmd-create.sql
      • Sequence: ims_md_life_cycle_contrib_entity_seq
      • Table: ims_md_life_cycle_contrib_entity
      • Sequence: ims_md_metadata_contrib_entity_seq
      • Sequence: ims_md_technical_requirement_seq
      • Sequence: ims_md_classification_taxpath_seq
      • Sequence: ims_md_classification_taxpath_taxon_seq
      • Table: ims_md_classification_taxpath_taxon
      • Sequence: ims_md_classification_keyword_seq
  • Package LORSM
    • File: lorsm-create.sql
      • Table: lorsm_course_presentation_formats

I'm on vacances last week, but the second week on July return. My deadline to finish to port is september and we want to put it in production in october.

I'm working on release dotlrn2.2b2 file, but I see last changes in the CVS HEAD and update my files.

Collapse
5: Re: LORS ORACLE port Issues (response to 1)
Posted by Dave Bauer on 07/12/06 05:55 PM
I created a branch in CVS called "lors-oracle-port". Please commit all changes to support oracle to this branch.