[
https://issues.apache.org/jira/browse/DERBY-3079?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Kristian Waagan updated DERBY-3079:
---
Derby Info: (was: [Existing Application Impact])
Unset "Existing Application Impact ".
> D
Myrna van Lunteren wrote:
On 9/19/07, Kristian Waagan (JIRA) <[EMAIL PROTECTED]> wrote:
The only problem I can think about is people parsing the log for some reason,
but it should be easy enough for them to fix their parsers/scripts.
Then maybe this issue should get flagged as existing appli
[
https://issues.apache.org/jira/browse/DERBY-3079?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Kristian Waagan updated DERBY-3079:
---
Derby Info: [Patch Available, Existing Application Impact] (was: [Patch
Available])
I'm mar
On 9/19/07, Kristian Waagan (JIRA) <[EMAIL PROTECTED]> wrote:
> The only problem I can think about is people parsing the log for some reason,
> but it should be easy enough for them to fix their parsers/scripts.
Then maybe this issue should get flagged as existing application impact?
Myrna
[
https://issues.apache.org/jira/browse/DERBY-3079?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Kristian Waagan updated DERBY-3079:
---
Attachment: derby-3079-1a.diff
'derby-3079-1a.diff' removes one of the printouts of the datab
[
https://issues.apache.org/jira/browse/DERBY-3079?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Kristian Waagan updated DERBY-3079:
---
Derby Info: [Patch Available]
> Database name is printed twice in derby.log on rollbacks when
