[
https://issues.apache.org/jira/browse/DERBY-1447?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12836611#action_12836611
]
Sylvain Leroux commented on DERBY-1447:
---------------------------------------
Hi Kristian,
and thanks for the comments!
Here, I was targeting environment without JLine-like software available. For
those cases, ij should provide some rudimentary editing capabilities available
everywhere.
But, for "advanced" editing features, JLine will still be the best option -
however, it requires manual setup (due to incompatibilities between BSD and
Apache licenses). And it is not 100% Java (it uses platform specific native
code).
----
At functional level, I agree with you: the history should handle properly
multi-line commands an multi-command lines:
ij> insert into T(a,b)
values(1,2),
(3,4);
ij> insert into T(a,b) values(1,2); insert into T(a,b) values(3,4);
Concerning parameters substitution as suggested in DERBY-4557 ($1, $2, ...), I
think the history should hold the value before substitution.
> add command line history to ij
> ------------------------------
>
> Key: DERBY-1447
> URL: https://issues.apache.org/jira/browse/DERBY-1447
> Project: Derby
> Issue Type: Improvement
> Components: Tools
> Reporter: Gary Orser
> Priority: Minor
> Attachments: jline-0_9_5.jar, jline.diff
>
>
> Using the command line tool
> org.apache.derby.tools.ij
> is user unfriendly.
--
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.
