You are viewing a plain text version of this content. The canonical link for it is here.
Posted to derby-dev@db.apache.org by "Jeff Levitt (JIRA)" <de...@db.apache.org> on 2005/06/10 22:46:50 UTC
[jira] Commented: (DERBY-275) Add documentation support for BY DEFAULT option, once code changes are made.
[ http://issues.apache.org/jira/browse/DERBY-275?page=comments#action_12313327 ]
Jeff Levitt commented on DERBY-275:
-----------------------------------
I was going to try to make a pass at a patch for the docs for this issue. It seems to me the only place that needs a change is in the Reference Manual, to change the syntax for generated column spec for Create Table to allow the option of either ALWAYS or BY DEFAULT. Is that the only place that needs changing? It didn't look to me like there needed to be any changes to anything about dblook, because that change was under the covers...?
If someone can enlighten me, I could submit a patch very soon...Thanks!
> Add documentation support for BY DEFAULT option, once code changes are made.
> ----------------------------------------------------------------------------
>
> Key: DERBY-275
> URL: http://issues.apache.org/jira/browse/DERBY-275
> Project: Derby
> Type: Sub-task
> Components: Documentation
> Versions: 10.0.2.1
> Reporter: Satheesh Bandaram
> Fix For: 10.1.0.0
>
> Once a patch is accepted, new syntax needs to be documented.
--
This message is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of the administrators:
http://issues.apache.org/jira/secure/Administrators.jspa
-
For more information on JIRA, see:
http://www.atlassian.com/software/jira
Re: [jira] Commented: (DERBY-275) Add documentation support for BY DEFAULT option, once code changes are made.
Posted by Jeff Levitt <de...@mylevita.com>.
--- Army <qo...@sbcglobal.net> wrote:
> This probably goes without saying, but of course
> you'd have to include an
> explanation of what BY DEFAULT means, in addition to
> changing the syntax diagram :)
>
Yes, thats the plan...could someone provide me with a
good synopsis of why you'd use ALWAYS or BY DEFAULT
over each other? Whats the advantage and disadvantage
of both?
>
> Note, though, that a slight dblook modification
> should be made for DERBY-337;
> I'll post a comment to that issue and that can serve
> as the start of a new thread...
Yes, I'd be happy to do that as well, I'll make the
changes in that jira issue...
Re: [jira] Commented: (DERBY-275) Add documentation support for BY
DEFAULT option, once code changes are made.
Posted by Army <qo...@sbcglobal.net>.
Jeff Levitt (JIRA) wrote:
> [ http://issues.apache.org/jira/browse/DERBY-275?page=comments#action_12313327 ]
>
> Jeff Levitt commented on DERBY-275:
> -----------------------------------
>
> I was going to try to make a pass at a patch for the docs for
> this issue. It seems to me the only place that needs a change
> is in the Reference Manual, to change the syntax for generated
> column spec for Create Table to allow the option of either
> ALWAYS or BY DEFAULT. Is that the only place that needs
> changing?
This probably goes without saying, but of course you'd have to include an
explanation of what BY DEFAULT means, in addition to changing the syntax diagram :)
> It didn't look to me like there needed to be any changes to
> anything about dblook, because that change was under the covers...?
Yes, that's correct--i.e. no changes to the dblook documentation should be required.
Note, though, that a slight dblook modification should be made for DERBY-337;
I'll post a comment to that issue and that can serve as the start of a new thread...
Army