There is one additional aspect to this - note the line in the log:

INFO: Column PROP_VALUE_EXT in table MY_TABLE differs from current specification


I didn't make any changes, but DDLUtils thinks the column has been changed.


Tim





Thomas Dudziak wrote:

On 1/31/06, Tim Dudgeon <[EMAIL PROTECTED]> wrote:

<snip>

   public void run() throws Exception {

       OracleDataSource ods = new OracleDataSource();

       ods.setURL("jdbc:oracle:thin:@localhost:1521:orcl");
       ods.setUser("my_user");
       ods.setPassword("my_password");

       String sql = "CREATE TABLE MY_TABLE( " +
               "prop_name VARCHAR2(200) NOT NULL PRIMARY KEY, " +
               "prop_value VARCHAR2(200), prop_value_ext LONG RAW NULL)";

       Connection conn = ods.getConnection();
       Statement stmt = conn.createStatement();
       stmt.execute(sql);
       stmt.close();
       conn.close();

       String schema = "MY_SCHEMA";

       Platform platform = PlatformFactory.createNewPlatformInstance(ods);
       Database db = platform.readModelFromDatabase("test", null,
schema, null);

       dumpDb(db);

       platform.alterTables(db, false, false, false);

This is the problem here: DdlUtils does not yet provide a mechanism
for specifying the catalog/schema to work in (. Could you create an
improvement in JIRA for this ?

Tom

Reply via email to