[
https://issues.apache.org/jira/browse/DERBY-3444?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12571447#action_12571447
]
Daniel John Debrunner commented on DERBY-3444:
----------------------------------------------
> Are we, in fact, deprecating the java/demo directory?
No, though based upon this I'd like to see its growth limited to *simple* demos
that focus on some aspect of Derby's technology. E.g. getting a connection,
using a table function, using Derby in tomcat, using Java routines, etc.
I don't think having applications in there is a good approach, if say the chat
server being discussed on the user list ended up in java/demo then the Apache
DB Derby sub-project has basically gone beyond databases into chat servers. I'd
like Derby to stay focused, I don't want to see posts about fixing a chat
server, a tear-off scheme or any other application on derby-dev (or derbyuser).
If the community is not responsive to fixing bugs in these complex
demos/applications then the reputation of Derby might suffer.
> separately developed code chunks could be accepted when that code is external
> and does not affect Derby itself.
No, the Derby project corresponds to the code in svn. Thus any code committed
is part of Derby, all needs to be treated equally and follow the Apache Way.
> Tearoff database demo
> ---------------------
>
> Key: DERBY-3444
> URL: https://issues.apache.org/jira/browse/DERBY-3444
> Project: Derby
> Issue Type: Task
> Components: Demos/Scripts
> Affects Versions: 10.4.0.0
> Reporter: Rick Hillegas
> Attachments: derby-3444-01-initial.diff
>
>
> Create a demonstration of tearoff databases. This shows how to use arbitrary,
> parameterized queries to tearoff datasets from an arbitrary server-hosted
> database and load those datasets into a Derby database running on a handset.
--
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.
