Re: [jira] Commented: (DERBY-275) Add documentation support for BY DEFAULT option, once code changes are made.

[Satheesh Bandaram]

I would want to highlight the fact that BY DEFAULT is the preferred option, if users expect to load/unload data into tables with identity columns. If users expect BY DEFAULT identity columns to be unique, they would need to enforce that by creating an unique index on that column. ALWAYS option is more safer to be unique. Satheesh Jeff Levitt wrote: --- Army <[EMAIL PROTECTED]> 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...