[
https://issues.apache.org/jira/browse/DERBY-6725?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14274186#comment-14274186
]
Mike Matrigali commented on DERBY-6725:
---------------------------------------
I too ran into problems when I first encountered the new process. I suggest
the following:
1) try with an empty up to date client and make sure you do not get any issues
with the lastcontent files, this
will separate your particular machine build issues vs your updated client
build issues.
2) I had to build with both sane and insane to get the right changes reflected
in my patch as there is a file
change for sane and for insane.
Once you work this out, consider if there are any improvements that can be made
to the message that prints out
when the build "fails" with new files that would have helped you understand
what is going on. I worked with myrna
to improve the message the last time - we should continue to improve it as
possible.
> Add a system function which returns the name of the database.
> -------------------------------------------------------------
>
> Key: DERBY-6725
> URL: https://issues.apache.org/jira/browse/DERBY-6725
> Project: Derby
> Issue Type: Improvement
> Components: SQL
> Affects Versions: 10.12.0.0
> Reporter: Rick Hillegas
> Assignee: Mamta A. Satoor
> Attachments: DERBY6725_getdbname_patch1_diff.txt,
> DERBY6725_getdbname_patch1_stat.txt
>
>
> Got this request in private conversation with a user. Other databases provide
> this functionality. Seems straightforward to add.
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
