db-derby-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Eranda Sooriyabandara (JIRA)" <j...@apache.org>
Subject [jira] Commented: (DERBY-4317) convert columnDefaults.sql to JUNIT
Date Fri, 31 Jul 2009 17:46:14 GMT

    [ https://issues.apache.org/jira/browse/DERBY-4317?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12737613#action_12737613

Eranda Sooriyabandara commented on DERBY-4317:

Hi Bryan, Mamta,
I try to use a decorator to overload decorateSQL method in which you can put
all the create table/view/function. But the problem is if I use that method
some of the create table must leave as it is now,

1.assertStatementError("42894", st," create table neg(c1 int default
These are asserting errors so we can keep them as they are now.

2. some times the same table names used by dropping the table.
   st.executeUpdate(" drop table neg");
   st.executeUpdate("create table neg(c1 int default 10)");
This can recover by using other name for the table.

But the biggest problem is the when we move the create table statements in
a separate method the readability is reduced(I think), because it is
checking the default values of the columns.
We can use alter table add column for this as a solution.

So the problem  what can I do?

> convert columnDefaults.sql to JUNIT
> -----------------------------------
>                 Key: DERBY-4317
>                 URL: https://issues.apache.org/jira/browse/DERBY-4317
>             Project: Derby
>          Issue Type: Improvement
>          Components: Test
>            Reporter: Eranda Sooriyabandara
>            Assignee: Eranda Sooriyabandara
>            Priority: Minor
>         Attachments: ColumnDefaultsTest.diff, ColumnDefaultsTest.diff
> Conversion of the columnDefaults.sql to JUNIT

This message is automatically generated by JIRA.
You can reply to this email to add a comment to the issue online.

View raw message