db-derby-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From Satheesh Bandaram <sathe...@Sourcery.Org>
Subject Re: [jira] Commented: (DERBY-275) Add documentation support for BY DEFAULT option, once code changes are made.
Date Tue, 14 Jun 2005 18:12:31 GMT
<!DOCTYPE html PUBLIC "-//W3C//DTD HTML 4.01 Transitional//EN">
  <meta content="text/html;charset=ISO-8859-1" http-equiv="Content-Type">
<body bgcolor="#ffffff" text="#000000">
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.<br>
Jeff Levitt wrote:<br>
<blockquote cite="mid20050613232203.97202.qmail@web81607.mail.yahoo.com"
  <pre wrap="">
--- Army <a class="moz-txt-link-rfc2396E" href="mailto:qozinx@sbcglobal.net">&lt;qozinx@sbcglobal.net&gt;</a>

  <blockquote type="cite">
    <pre wrap="">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 :)

  <pre wrap=""><!---->
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?

  <blockquote type="cite">
    <pre wrap="">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...
  <pre wrap=""><!---->
Yes, I'd be happy to do that as well, I'll make the
changes in that jira issue...


View raw message