title: New Oracle Constraint Type
body: <p>I have to admit that this just caught me by surprise in a production system.  I recently added supplemental logging to a few tables for use with Oracle Change Data Capture.  A routine check during an unrelated code build revealed that this apparently created disabled constraints in the database of type "S".  I can't seem to find any reference to this in the Oracle docs and the single "S" makes it hard to Google for something relevant.</p>
  
  <p>My questions:</p>
  
  <ol>
  <li>Can anyone thing of a reason that
  supplemental logging results in an
  implicit constraint?</li>
  <li>Why is it created with a DISABLED
  state?</li>
  <li>Does anyone have experience with the
  effects of enabling these?  We have
  a standard clean-up process that
  runs after deployments to fully
  enable constraints that may have
  been disabled or enabled novalidate
  for data migration reasons.</li>
  </ol>