[
https://issues.apache.org/jira/browse/DERBY-3007?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel#action_12520650
]
Laura Stewart commented on DERBY-3007:
--------------------------------------
I want to understand the doc requirement for Derby 2925. Listed in that issue
are only 3 system procedures, but there are 4 EXPORT system procedures. It
would seem to me that this issue applies to all 4 system procedures, but I want
to be certain before I commit the changes...
Also, here is the text that I would like to add to each of the EXPORT
procedures:
"For security concerns, and to avoid accidental file damage, this EXPORT
procedure
does not export data into an existing file. You must specify a file in the
EXPORT procedure that does not exist. When you run the procedure the file is
created and the data is exported
into the new file. "
> Documentation - SYSCS EXPORT TABLE system procedures cannot export data to an
> existing file
> -------------------------------------------------------------------------------------------
>
> Key: DERBY-3007
> URL: https://issues.apache.org/jira/browse/DERBY-3007
> Project: Derby
> Issue Type: Bug
> Components: Documentation
> Affects Versions: 10.3.1.4
> Reporter: Laura Stewart
> Assignee: Laura Stewart
> Priority: Minor
> Fix For: 10.3.1.5
>
>
> Derby-2925 describes the code issue. In the documentation, add a note to
> each of the STSCS EXPORT dita files that a new file gets created when you
> export data. If you attempt to export to an existing file, an error is
> returned.
> The files that need to be updated are:
> SYSCS_UTIL.SYSCS_EXPORT_TABLE system procedure
> SYSCS_UTIL.SYSCS_EXPORT_TABLE_LOBS_TO_EXTFILE system procedure
> SYSCS_UTIL.SYSCS_EXPORT_QUERY system procedure
> SYSCS_UTIL.SYSCS_EXPORT_QUERY_LOBS_TO_EXTFILE system procedure
--
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.
