I just did this same kind of thing using SQL*Load. I had to put in my XML
delimiters for each row, etc. but it worked slick as frog snot!
cust_transaction_dtl.ctl
LOAD DATA
INTO TABLE "TRANS_HIST"."CUST_DTL" APPEND
(dummy filler enclosed by '',
SITE_CODE ENCLOSED BY '' AND '',
INVOICE_NUMBER ENCLOSED BY '' AND '',
CLOSE_DTS DATE 'MM/DD/YYYY HH24:MI:SS' ENCLOSED BY '' AND
'',
CUSTOMER_NUMBER ENCLOSED BY '' AND '',
STATUS_TYPE ENCLOSED BY '' AND '',
NEW_CUSTOMER_FLAG ENCLOSED BY '' AND '',
CUSTOMER_NAME ENCLOSED BY '' AND '',
CUSTOMER_ADDRESS ENCLOSED BY '' AND '',
CUSTOMER_CITY ENCLOSED BY '' AND '',
CUSTOMER_ST_PROV_CODE ENCLOSED BY '' AND
'',
CUSTOMER_ZIP_CODE ENCLOSED BY '' AND '',
CUSTOMER_AREA_CODE ENCLOSED BY '' AND
'',
CUSTOMER_PHONE ENCLOSED BY '' AND '',
AFFILIATED_CO ENCLOSED BY '' AND '',
dummy2 filler enclosed by '')
Hope the helps.
David
UtahToad@gmail.com
Simoneau, Roger wrote:
“ to author the parser was trivial ”
I should note for the humor impaired that I recognize writing a parser for a
very specific file is trivial in comparison to doing up the code to be able
to handle the full XML format!
As I mentioned earlier, I was looking for a quick-n-dirty method so the code
is just that. It’s not anywhere near as flexible as it would have to
be in order to handle an unknown file with only knowledge of XML to guide
the developer.
So… my apologies if any developers who author XML parsers were
offended!
RAS
PLEASE NOTE:
This communication, including any attached documentation,
is intended only for the person or entity to which it is addressed,
and may contain confidential, personal and/or privileged information.
Any unauthorized disclosure, copying, or taking action on the contents
is strictly prohibited. If you have received this message in error,
please contact us immediately so we may correct our records.
Please then delete or destroy the original transmission and any subsequent reply.
Thank you.