Placing the derby.properties in the tests directory made the MailJdbc test run.
Great!
taking too much time(potentially due to many sleep calls).
Yes, I think that is a flaw with that test program; it is designed to
run very slowly so it can be left running in the background for weeks
or mon
[
https://issues.apache.org/jira/browse/DERBY-4091?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Sandeep Samdaria updated DERBY-4091:
Attachment: Activity.out
> Investigate "size_problem" column in MailJdbc terst
> ---
Hi Bryan,
Placing the derby.properties in the tests directory made the MailJdbc test
run. As per the JIRA, I have removed the column "size_problem" from the
insertStr (Statements.java) query and rebuilt the jars. Now, when I am
trying to run the MailJdbc test it is taking too much time(potentially
Aleksei Kovura created DERBY-6876:
-
Summary: Can't create triggers on a table - error 42X94
Key: DERBY-6876
URL: https://issues.apache.org/jira/browse/DERBY-6876
Project: Derby
Issue Type: Bu
[
https://issues.apache.org/jira/browse/DERBY-6876?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Aleksei Kovura updated DERBY-6876:
--
Attachment: trigger_bug.zip
> Can't create triggers on a table - error 42X94
> -
