Announcement

Collapse

Mirth Connect 3.12.0 Released!

Mirth Connect 3.12.0 is now available as an appliance update and on our GitHub page. This release includes database performance improvements, improves visual HL7 representation, message pruning, keystore handling, PDF generation, community contributions, and fixes several security vulnerabilities. This release also contains many improvements to commercial extensions. See the release notes for the list of fixes and updates.

Download | See What's New | Upgrade Guide | Release Notes

For discussion on this release, see this thread.
See more
See less

oracle-database.sql

Collapse
X
 
  • Filter
  • Time
  • Show
Clear All
new posts

  • oracle-database.sql

    This installation script should be run with care. It starts up with the following loop:
    BEGIN
    FOR R1 IN (SELECT TABLE_NAME FROM USER_TABLES) LOOP
    BEGIN
    EXECUTE IMMEDIATE 'DROP TABLE ' || R1.TABLE_NAME;
    EXCEPTION WHEN OTHERS THEN NULL;
    END;
    END LOOP;
    END;

    This could be very dangerous and IMHO it is useless since the following creation of each table is preceded by its corresponding drop. May these lines be removed ?
    regards

  • #2
    Reracle-database.sql

    I believe these lines are there to get rid of some things the other drops do not. This schema should only have Mirth tables, so it shouldn't be a problem unless you are using the schema for something else as well. If this is the case, you would have a big problem. Remember, this script is to recreate the entire schema for Mirth.
    Jacob Brauer
    Director, Software Development
    NextGen Healthcare

    sigpic

    Comment

    Working...
    X