#7 Add capability of mapping to different types

[Archimedes Trajano]

In Oracle we have NUMBER, in other database its
DECIMAL. Would it be possible to add support so we
can map certain types in a different way on another
database?

Or even add support so if the table creation fails, it will
change the types to what it closely represents, e.g.
VARCHAR2 (oracle) ==> java.lang.String ==> VARCHAR
(db2)

[Oliver Gries]

Logged In: YES
user_id=571857

This is already possible if the target table exists.

You can specify on the mapping page the desired column of
your target table (standard mapping is done by the equality
of column names).

At the moment there is still the problem with inpropper SQL
DDL statements for different table types. I work on a solution
for this.

However there is a simple way of getting around for this. Just
copy the generated DDL statement out of the error message
pane, adjust the wrong values with your desired ones and
execute the statement via the dbcopy SQL editor manually.

Once successful with your table creation, you can use the
mapping dialog according to your needs.

But be aware that you can not mix column types (NUMERIC /
CHAR / etc.) that will fail. An upcomming converter for a
mapping step would be the solution.

Thanks
Oliver

[Archimedes Trajano]

Logged In: YES
user_id=55322

Is there a way of extracting all the DDL from the database
with your tool rather than doing it one table at a time I can
just use the DDL and use search and replace then add the
new tables to the database.

[Nobody/Anonymous]

Logged In: NO

... sorry, extracting just the DDL for all tables in the db is not
directly possible yet.

************************************

You might do it in the following way:

- select all tables in the database to be copied
- switch off [Copy Data]
- switch on [Create Tables]
- start the copy process

You should see in the log entries starting with: "Exexcute:
create table ..." either with an error sign or just the normal
info icon.

Now you still have to double click on each of this entry to get
the SQL command shown (and maybe copied out from there).

Alternativly start DBCopy from the command line as descriped
in the HELP forum, and either look for a file called "dbcopy.log"
or redirect the console output to a file which you then can
use to copy all the statement out.

Sorry that there is no easier way, but I will keep this feature
in mind for the next releases.

Thanks
Oliver