Personally i have found inbound processing of xml very easy and powerful in unidata . The documentation is quite clearly split - use a map file for creating xml documents use an ext file for receiving them - i use it daily for large (multi gigabyte) xml files, EXT files are very easy to set up, you do need to be careful with character encoding and make sure your LANG settings are correct but it certainly works fine.
I agree the basic xml export from a list command is ugly but it is in any system where you leave it to auto generate by itself - if you want nice xml use a map file, or if your xml is published by way of a webs ervice i return my data arrays to a asp.net app using uniobjects and let it formulate the xml web service - again very easy and simple to do. Also i have never spent time with the xml db tool - xml handling is easy and it is quicker to write the ten lines of code you require than to play around with an eclipse tool. Just my experience with XML ... Symeon. -----Original Message----- From: [email protected] [mailto:[email protected]] On Behalf Of Debster Sent: 28 February 2009 07:52 To: [email protected] Subject: RE: [U2] OLEDB error Well... After all the back and forth in attempting to transfer data back & forth between a third party SQL Server based tool... IMHO -- Unidata XML is rudimentary at best. It is not exactly pretty, outbound is easy even if esthetically UGLY, is easily transmitted, read, and data populated once outside Unidata. -- Parsing inbound XML data is yet another story on Unidata 6.x it simply does not work. Not ready for prime time. The only work around is to create a program to read the tags and populate. One document states to create a map (was done), yet another document states to create an extract file, (duh - isn't a map stating what field, size, position providing the same information? - use the search on the complete doc set and see all the conflicting hits you can find!) A Big Thumbs down. This method was bagged -- The XML/DB tool has bugs - but is workable, but for what end result I do not know due to the above mentioned results -- ODBC/OLEDB setup, documentation, & support is nearly non-existent and woefully skewed and is devoid of "Big Picture", "Best Practices" and "Commonly used" information. It took FOREVER to get the slimmest of answers to basic questions. -- End result, I am able to write directly from within the app....Oh joy! Direct DML used... SQL Server 2005 to Unidata 6.x down to the Multi subvalue. The data can cleanly be pushed or pulled in either direction. This was done with much trial and error invested -- no additional third party drivers required - and if I told you how I did it -- I would have to kill you -- and NOW they decide the time is to upgrade to Unidata 7.x -- aaarrrrgggghhhhhhhhhhhhhh -----Original Message----- From: [email protected] [mailto:[email protected]]on Behalf Of Garry Smith Sent: Wednesday, February 18, 2009 4:53 PM To: [email protected] Subject: RE: [U2] OLEDB error Insert to a view has several limitations: You cannot Insert multiple tables to a view with multiple tables. Only one table at a time. If a view is not showing all the fields and some of those "un-seen" fields do not allow nulls then when you do an Insert to the view it fails. Garry L. Smith Dir Info Systems Charles McMurray Company V# 559-292-5782 F# 559-346-6169 -----Original Message----- From: [email protected] [mailto:[email protected]] On Behalf Of Symeon Breen Sent: Tuesday, February 17, 2009 1:44 PM To: [email protected] Subject: RE: [U2] OLEDB error What is the actual sql command you are performing ? It is a bit confusing as the error talks about an insert but it is a select it is showing. -----Original Message----- From: [email protected] [mailto:[email protected]] On Behalf Of Debra Fedchin Sent: 17 February 2009 15:59 To: [email protected] Subject: RE: [U2] OLEDB error Yep All permission's are set to PUBLIC It is frustrating since most of the DOCS give examples of utilizing SQL statements as if you attempting to manipulate Unidata data within the Unidata server itself (duh -- now why would I be attempting to make like more complicated for no good reason?) OR examples of how to EXTRACT data from a SQL server into Unidata. There are no clear examples of a standard SQL statement that would be used on a Client to update exposed SQL Tables that have a parent/child relationship (MV) -- and a statement that goes beyond a mere snipit that would give you more than the smallest granular overview. It's bad enough that the XML extract does not work as documented (non standard and just plain butt ugly in regards to hierarchy!) without adding further insult to injury. All I am trying to do is to update FROM a client to Unidata without having to drop-kick to flat text files! It ain't rocket science! Horacio Pellegrino <[email protected]> Sent by: [email protected] 02/12/2009 08:11 PM Please respond to [email protected] To [email protected] cc Subject RE: [U2] OLEDB error Username has permissions to create and insert granted? HP -----Original Message----- From: [email protected] [mailto:[email protected]] On Behalf Of Debra Fedchin Sent: Wednesday, February 11, 2009 11:08 AM To: [email protected] Cc: [email protected]; '[email protected]' Subject: [U2] OLEDB error ok Can someone tell me why I got this error? Debug: OLEDB driver: Insert SQL='SELECT BIG_01_Invoice_Date, BIG_02_Invoice_Num, BIG_03_PO_Date, BIG_04_PO_Num, BIG_05_Rel_Num, BIG_07_Trans_Type, Benco_Host, CTT_01_CTT_Amt, DTM_01_Date_Qualifer, DTM_02_Date_Shipped, Date_Processed, EDI810_ID, Mailbox, N1_BT_01_Code, N1_BT_02_Name, N1_BT_03_Qualifier, N1_BT_04_ID, N3_BT_01_Address1, N3_BT_02_Address2, N4_BT_01_City, N4_BT_02_State, N4_BT_03_Zip, N4_BT_04_Country_Code, TDS_01_Amount, Trading_Partner, Vendor_Num FROM daf.EDI_INVOICE_HDR_NF_SUB WHERE (0=1)' Error: Couldn't insert row into table 'EDI_INVOICE_HDR_NF_SUB'. Error: Error 0x80004005: "[Ardent][UniData ODBC Driver][IBM][SQL Client][UNIDATA]Can not insert into view EDI_INVOICE_HDR_NF_SUB" Now -- this table was created, had SQL.CONVERT run against it, followed by going through VSG to create both Views and Subtables, all Privileges have been set to PUBLIC The error states that the table is a view when in fact it is a Subtable ================================================= This communication (including any attachments) is intended only for use by the addressee(s) named herein and may contain legally privileged or confidential information. If you are not the intended recipient or an authorized representative of the intended recipient on this communication, you are hereby notified that any dissemination or distribution of this communication (or attachments) is strictly prohibited. If you have received this communication in error, please notify us immediately by e-mail and permanently delete the communication and any attachments from your system. ------- u2-users mailing list [email protected] To unsubscribe please visit http://listserver.u2ug.org/ ------- u2-users mailing list [email protected] To unsubscribe please visit http://listserver.u2ug.org/ ================================================= This communication (including any attachments) is intended only for use by the addressee(s) named herein and may contain legally privileged or confidential information. If you are not the intended recipient or an authorized representative of the intended recipient on this communication, you are hereby notified that any dissemination or distribution of this communication (or attachments) is strictly prohibited. If you have received this communication in error, please notify us immediately by e-mail and permanently delete the communication and any attachments from your system. ------- u2-users mailing list [email protected] To unsubscribe please visit http://listserver.u2ug.org/ ------- u2-users mailing list [email protected] To unsubscribe please visit http://listserver.u2ug.org/ ------- u2-users mailing list [email protected] To unsubscribe please visit http://listserver.u2ug.org/ ------- u2-users mailing list [email protected] To unsubscribe please visit http://listserver.u2ug.org/ ------- u2-users mailing list [email protected] To unsubscribe please visit http://listserver.u2ug.org/
