>>Or, maybe you could code up your stored procedure as a FUNCTION and have it >>return an error message. That's what I just did using Mercator with Oracle; works good.
Michael, that's really all I'm looking for is the ability to pass the detailed (custom, not system defined) error message back to Delta. If Delta truly only allows a simple return code, I can't pass something helpful such as "GLN code not found for 1234567890123", for example. I could log out to a custom table or something like that, but that's a somewhat fugly solution in my opinion. I could probably also append directly into ECS's tables to "supplement" the error logging shown to the user, but Liaison would probably frown on that plan, and it would require some reverse engineering to figure out how to safely accomplish that... Another reason I think this may also help is that I'm not extremely versed at Delta mapping yet, and I'm not sure if I'm going to get "all the errors" from Delta during a translation. Just getting the first of many errors, doled out one at a time is really obnoxious, and if they are nondescript, it's just that much worse. :) Travis- ----- Original Message ----- From: "Michael Mattias/LS" <[email protected]> To: [email protected] Sent: Thursday, June 20, 2013 9:07:07 AM Subject: Re: [EDI-L] Liaison / Softshare Delta + SQL Stored Procedures >Delta's db support is much more robust, given that it was actually not an >afterthought.... Amazing how that is true of so much software. Oh, you were looking for some real ideas... > I would really like some mechanism to get a detailed error message returned > from the SQL SP back into Delta to display & log to > users so they don't have to >perform SQL queries to find what errors have > occurred. I assume you are looking for 'DBMS' error messages (e.g "invalid tablename in SELECT " or "constraint violation on INSERT") as contrasted to "A DBMS action succeeded at the DBMS level but Delta had a problem?" I don't know Delta (although I may have to learn quickly and soon), but if there is no 'native' facility for this you could look at creating your own "exit" type code which will. return what you want. Or, maybe you could code up your stored procedure as a FUNCTION and have it return an error message. That's what I just did using Mercator with Oracle; works good. Michael C. Mattias Tal Systems Inc. Racine WI [email protected] ------------------------------------ ... Please use the following Message Identifiers as your subject prefix: <SALES>, <JOBS>, <LIST>, <TECH>, <MISC>, <EVENT>, <OFF-TOPIC> Job postings are welcome, but for job postings or requests for work: <JOBS> IS REQUIRED in the subject line as a prefix.Yahoo! Groups Links [Non-text portions of this message have been removed] ------------------------------------ ... Please use the following Message Identifiers as your subject prefix: <SALES>, <JOBS>, <LIST>, <TECH>, <MISC>, <EVENT>, <OFF-TOPIC> Job postings are welcome, but for job postings or requests for work: <JOBS> IS REQUIRED in the subject line as a prefix.Yahoo! Groups Links <*> To visit your group on the web, go to: http://groups.yahoo.com/group/EDI-L/ <*> Your email settings: Individual Email | Traditional <*> To change settings online go to: http://groups.yahoo.com/group/EDI-L/join (Yahoo! ID required) <*> To change settings via email: [email protected] [email protected] <*> To unsubscribe from this group, send an email to: [email protected] <*> Your use of Yahoo! Groups is subject to: http://docs.yahoo.com/info/terms/
