[
https://issues.apache.org/jira/browse/DERBY-6910?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16185163#comment-16185163
]
Rick Hillegas commented on DERBY-6910:
--------------------------------------
I am a bit worried about the proliferation of export procedures. They have
gradually accreted over time, one by one, without much thought for future
expansion. I am ok with a new procedure, but I think that it must cover the
following cases:
1) Export from query. The query can be a select from a table but it can be more
elaborate than that.
2) Allow for a separate file for LOB columns. Maybe one file per LOB column.
3) Support CSV with or without header. But also support other formats like
JSON. We wouldn't have to implement all of them up front, but we should leave
ourselves room for expansion.
This issue deserves some thought and design. What do people think?
> Add Option for column names in first line of export file when using CALL
> SYSCS_UTIL.SYSCS_EXPORT_TABLE
> ------------------------------------------------------------------------------------------------------
>
> Key: DERBY-6910
> URL: https://issues.apache.org/jira/browse/DERBY-6910
> Project: Derby
> Issue Type: Improvement
> Components: Tools
> Affects Versions: 10.12.1.1
> Reporter: Christian Eugster
> Assignee: Lashan Faliq
> Priority: Trivial
> Attachments: DERBY-6910Enhancement.diff
>
>
> It would be fine if there was the Option for adding the columnnames in the
> first line of an Export file in CALL SYSCS_UTIL.SYSCS_EXPORT_TABLE
--
This message was sent by Atlassian JIRA
(v6.4.14#64029)
