Return-Path: Delivered-To: apmail-db-ddlutils-user-archive@www.apache.org Received: (qmail 44737 invoked from network); 28 Oct 2010 17:09:24 -0000 Received: from unknown (HELO mail.apache.org) (140.211.11.3) by 140.211.11.9 with SMTP; 28 Oct 2010 17:09:24 -0000 Received: (qmail 24351 invoked by uid 500); 28 Oct 2010 17:09:24 -0000 Delivered-To: apmail-db-ddlutils-user-archive@db.apache.org Received: (qmail 24313 invoked by uid 500); 28 Oct 2010 17:09:23 -0000 Mailing-List: contact ddlutils-user-help@db.apache.org; run by ezmlm Precedence: bulk List-Help: List-Unsubscribe: List-Post: List-Id: Reply-To: ddlutils-user@db.apache.org Delivered-To: mailing list ddlutils-user@db.apache.org Received: (qmail 24305 invoked by uid 99); 28 Oct 2010 17:09:23 -0000 Received: from nike.apache.org (HELO nike.apache.org) (192.87.106.230) by apache.org (qpsmtpd/0.29) with ESMTP; Thu, 28 Oct 2010 17:09:23 +0000 X-ASF-Spam-Status: No, hits=4.4 required=10.0 tests=FREEMAIL_ENVFROM_END_DIGIT,FREEMAIL_FROM,HTML_MESSAGE,RCVD_IN_DNSWL_NONE,SPF_PASS,T_TO_NO_BRKTS_FREEMAIL X-Spam-Check-By: apache.org Received-SPF: pass (nike.apache.org: domain of kscarr73@gmail.com designates 209.85.213.172 as permitted sender) Received: from [209.85.213.172] (HELO mail-yx0-f172.google.com) (209.85.213.172) by apache.org (qpsmtpd/0.29) with ESMTP; Thu, 28 Oct 2010 17:09:15 +0000 Received: by yxp4 with SMTP id 4so1514391yxp.31 for ; Thu, 28 Oct 2010 10:08:54 -0700 (PDT) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=gamma; h=domainkey-signature:mime-version:received:received:date:message-id :subject:from:to:content-type; bh=a2ADv/f5vB7oDSHOydXSjV0JCOPUWMqaQa8U2RcSWY8=; b=Eve88VQVvWWn7eaYeHLHkJXVp7qcOMicftWhDmsKAYofT30TvqN1o21ZrAuJ6SMH2D TmNrsFE189UBuyUsuQEmwQNPONtYSW//Kbga08dxhRSBN4f/otNgxoIER9wfq/6OWaeD zC0Thm47yL5PGxGurhfkbOSYBlx5Ft1ZxiM68= DomainKey-Signature: a=rsa-sha1; c=nofws; d=gmail.com; s=gamma; h=mime-version:date:message-id:subject:from:to:content-type; b=OaQE/qhiSlLgz3tTZL0kYsgynXJqd25o4RUcMdF/E+75XKiHrdMleh0MX0j4ATkpPF jxK4UUZLCKhDCdb/iE9F2vQB3BlGZ9ctZyWdxWzheZwh3gQm5mPPWHrUa0ug9fSrFNX1 K71Ew1JjCkzem00dV8fDK7ZmXT2SCe2xCJiFY= MIME-Version: 1.0 Received: by 10.204.117.199 with SMTP id s7mr8933969bkq.15.1288285475748; Thu, 28 Oct 2010 10:04:35 -0700 (PDT) Received: by 10.204.64.83 with HTTP; Thu, 28 Oct 2010 10:04:35 -0700 (PDT) Date: Thu, 28 Oct 2010 12:04:35 -0500 Message-ID: Subject: Adding a Data Tag to the schema From: Kevin Carr To: ddlutils-user@db.apache.org Content-Type: multipart/alternative; boundary=0016e6d648162888f00493b0564f X-Virus-Checked: Checked by ClamAV on apache.org --0016e6d648162888f00493b0564f Content-Type: text/plain; charset=ISO-8859-1 I am thinking of adding a data tag to the schema. Something like: My first widget Business My Second widget Business My third widget Business Indexed would tell the code that this field is the should be searched first to see if it exists, and replaced if it does. Auto tells the code that this field is auto generated and shouldn't be messed with. Basically, the field is ignored when creating the update or insert. Does this sound like a good idea? Am I trying to fix a problem that is already fixed better elsewhere? Thanks --0016e6d648162888f00493b0564f--