Path: dp-news.maxwell.syr.edu!spool.maxwell.syr.edu!news-spur1.maxwell.syr.edu!news.maxwell.syr.edu!postnews.google.com!news3.google.com!border1.nntp.dca.giganews.com!nntp.giganews.com!local01.nntp.dca.giganews.com!nntp.comcast.com!news.comcast.com.POSTED!not-for-mail
NNTP-Posting-Date: Fri, 03 Mar 2006 07:38:28 -0600
Reply-To: "Mark C. Stock" <mcstockX@Xenquery .com>
From: "Mark C. Stock" <mcstockX@Xenquery .com>
Newsgroups: comp.databases.oracle.server
References: <MPG.1e724ce1b06d6fe698a102@news.individual.net> <p9ydnXnZo57joJXZnZ2dnUVZ_tudnZ2d@comcast.com> <MPG.1e725007d54f327098a104@news.individual.net>
Subject: Re: Reducing coding of insert into.. select statement
Date: Fri, 3 Mar 2006 08:38:25 -0500
Organization: Enquery, Incorporated
X-Priority: 3
X-MSMail-Priority: Normal
X-Newsreader: Microsoft Outlook Express 6.00.2900.2180
x-mimeole: Produced By Microsoft MimeOLE V6.00.2900.2180
Message-ID: <q7CdnQpB5YdJ25XZRVn-og@comcast.com>
Lines: 34
NNTP-Posting-Host: 68.57.99.188
X-Trace: sv3-MOognx56EzC+ZlY6Dgna2NIGoo8I1wfkWEEYm+L3akt8FX8GyhDuCsfXnuN+ekcKTrFSDLlcJnuojUZ!JolTtHzrQis6OIi5dDcwib5LGczBlBgvQx/eRe+dD9fd4yHZsenXT+qk/UCM/JoSz1fG7tmt7ZFH!lg==
X-Complaints-To: abuse@comcast.net
X-DMCA-Complaints-To: dmca@comcast.net
X-Abuse-and-DMCA-Info: Please be sure to forward a copy of ALL headers
X-Abuse-and-DMCA-Info: Otherwise we will be unable to process your complaint properly
X-Postfilter: 1.3.32
Xref: dp-news.maxwell.syr.edu comp.databases.oracle.server:262687


"Jeremy" <jeremy0505@gmail.com> wrote in message 
news:MPG.1e725007d54f327098a104@news.individual.net...
: In article <p9ydnXnZo57joJXZnZ2dnUVZ_tudnZ2d@comcast.com>, Mark C. Stock
: says...
: >
:
: >
: > you could use the data dictionary to generate the script
: >
:
: Hi mark - I guess so - then edit the resultant script to alter the bits
: that need altering. Any examples of a "previously-used" script?
:
:
: -- 
:
: jeremy
: '01 Triumph Sprint ST in green
: _______________________________________
: jeremy0505 at gmail.com
:

no, but it should really be trivial and not require any editing --  
especially if you've got a trigger on the target table assigning the pks

at any rate, your only variables are table name, db link name, and (perhaps) 
sequence name -- everything else is in USER_TAB_COLUMNS and 
USER_CONSTRAINTS/USER_CONS_COLUMNS (to identify the single-column PK or 
exception process multi-column PKs)

++ mcs 


