<html xmlns:v="urn:schemas-microsoft-com:vml" xmlns:o="urn:schemas-microsoft-com:office:office" xmlns:w="urn:schemas-microsoft-com:office:word" xmlns:x="urn:schemas-microsoft-com:office:excel" xmlns:p="urn:schemas-microsoft-com:office:powerpoint" xmlns:a="urn:schemas-microsoft-com:office:access" xmlns:dt="uuid:C2F41010-65B3-11d1-A29F-00AA00C14882" xmlns:s="uuid:BDC6E3F0-6DA3-11d1-A2A3-00AA00C14882" xmlns:rs="urn:schemas-microsoft-com:rowset" xmlns:z="#RowsetSchema" xmlns:b="urn:schemas-microsoft-com:office:publisher" xmlns:ss="urn:schemas-microsoft-com:office:spreadsheet" xmlns:c="urn:schemas-microsoft-com:office:component:spreadsheet" xmlns:odc="urn:schemas-microsoft-com:office:odc" xmlns:oa="urn:schemas-microsoft-com:office:activation" xmlns:html="http://www.w3.org/TR/REC-html40" xmlns:q="http://schemas.xmlsoap.org/soap/envelope/" xmlns:rtc="http://microsoft.com/officenet/conferencing" xmlns:D="DAV:" xmlns:Repl="http://schemas.microsoft.com/repl/" xmlns:mt="http://schemas.microsoft.com/sharepoint/soap/meetings/" xmlns:x2="http://schemas.microsoft.com/office/excel/2003/xml" xmlns:ppda="http://www.passport.com/NameSpace.xsd" xmlns:ois="http://schemas.microsoft.com/sharepoint/soap/ois/" xmlns:dir="http://schemas.microsoft.com/sharepoint/soap/directory/" xmlns:ds="http://www.w3.org/2000/09/xmldsig#" xmlns:dsp="http://schemas.microsoft.com/sharepoint/dsp" xmlns:udc="http://schemas.microsoft.com/data/udc" xmlns:xsd="http://www.w3.org/2001/XMLSchema" xmlns:sub="http://schemas.microsoft.com/sharepoint/soap/2002/1/alerts/" xmlns:ec="http://www.w3.org/2001/04/xmlenc#" xmlns:sp="http://schemas.microsoft.com/sharepoint/" xmlns:sps="http://schemas.microsoft.com/sharepoint/soap/" xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance" xmlns:udcs="http://schemas.microsoft.com/data/udc/soap" xmlns:udcxf="http://schemas.microsoft.com/data/udc/xmlfile" xmlns:udcp2p="http://schemas.microsoft.com/data/udc/parttopart" xmlns:wf="http://schemas.microsoft.com/sharepoint/soap/workflow/" xmlns:dsss="http://schemas.microsoft.com/office/2006/digsig-setup" xmlns:dssi="http://schemas.microsoft.com/office/2006/digsig" xmlns:mdssi="http://schemas.openxmlformats.org/package/2006/digital-signature" xmlns:mver="http://schemas.openxmlformats.org/markup-compatibility/2006" xmlns:m="http://schemas.microsoft.com/office/2004/12/omml" xmlns:mrels="http://schemas.openxmlformats.org/package/2006/relationships" xmlns:spwp="http://microsoft.com/sharepoint/webpartpages" xmlns:ex12t="http://schemas.microsoft.com/exchange/services/2006/types" xmlns:ex12m="http://schemas.microsoft.com/exchange/services/2006/messages" xmlns:pptsl="http://schemas.microsoft.com/sharepoint/soap/SlideLibrary/" xmlns:spsl="http://microsoft.com/webservices/SharePointPortalServer/PublishedLinksService" xmlns:Z="urn:schemas-microsoft-com:" xmlns:st="" xmlns="http://www.w3.org/TR/REC-html40">
<head>
<meta http-equiv=Content-Type content="text/html; charset=iso-8859-1">
<meta name=Generator content="Microsoft Word 12 (filtered medium)">
<style>
<!--
/* Font Definitions */
@font-face
{font-family:Wingdings;
panose-1:5 0 0 0 0 0 0 0 0 0;}
@font-face
{font-family:"Cambria Math";
panose-1:2 4 5 3 5 4 6 3 2 4;}
@font-face
{font-family:Calibri;
panose-1:2 15 5 2 2 2 4 3 2 4;}
@font-face
{font-family:Tahoma;
panose-1:2 11 6 4 3 5 4 4 2 4;}
/* Style Definitions */
p.MsoNormal, li.MsoNormal, div.MsoNormal
{margin:0in;
margin-bottom:.0001pt;
text-align:justify;
font-size:10.5pt;
font-family:"Calibri","sans-serif";}
a:link, span.MsoHyperlink
{mso-style-priority:99;
color:blue;
text-decoration:underline;}
a:visited, span.MsoHyperlinkFollowed
{mso-style-priority:99;
color:purple;
text-decoration:underline;}
em
{mso-style-priority:20;
font-weight:bold;
font-style:normal;}
pre
{mso-style-priority:99;
mso-style-link:"HTML Preformatted Char";
margin:0in;
margin-bottom:.0001pt;
font-size:10.0pt;
font-family:"Courier New";}
p.MsoListParagraph, li.MsoListParagraph, div.MsoListParagraph
{mso-style-priority:34;
margin-top:0in;
margin-right:0in;
margin-bottom:0in;
margin-left:.5in;
margin-bottom:.0001pt;
text-align:justify;
font-size:10.5pt;
font-family:"Calibri","sans-serif";}
span.HTMLPreformattedChar
{mso-style-name:"HTML Preformatted Char";
mso-style-priority:99;
mso-style-link:"HTML Preformatted";
font-family:"Courier New";}
span.EmailStyle21
{mso-style-type:personal;
font-family:"Calibri","sans-serif";
color:windowtext;}
span.EmailStyle22
{mso-style-type:personal;
font-family:"Calibri","sans-serif";
color:#1F497D;}
span.EmailStyle23
{mso-style-type:personal;
font-family:"Calibri","sans-serif";
color:#1F497D;}
span.EmailStyle24
{mso-style-type:personal;
font-family:"Calibri","sans-serif";
color:#1F497D;}
span.EmailStyle25
{mso-style-type:personal;
font-family:"Calibri","sans-serif";
color:#1F497D;}
span.EmailStyle26
{mso-style-type:personal;
font-family:"Calibri","sans-serif";
color:#1F497D;}
span.EmailStyle27
{mso-style-type:personal;
font-family:"Calibri","sans-serif";
color:#1F497D;}
span.EmailStyle28
{mso-style-type:personal;
font-family:"Calibri","sans-serif";
color:#1F497D;}
span.EmailStyle29
{mso-style-type:personal;
font-family:"Calibri","sans-serif";
color:#1F497D;}
span.EmailStyle30
{mso-style-type:personal;
font-family:"Calibri","sans-serif";
color:#1F497D;}
span.EmailStyle31
{mso-style-type:personal;
font-family:"Calibri","sans-serif";
color:#1F497D;}
span.EmailStyle32
{mso-style-type:personal;
font-family:"Calibri","sans-serif";
color:#1F497D;}
span.EmailStyle33
{mso-style-type:personal;
font-family:"Calibri","sans-serif";
color:#1F497D;}
span.EmailStyle34
{mso-style-type:personal;
font-family:"Calibri","sans-serif";
color:#1F497D;}
span.EmailStyle35
{mso-style-type:personal;
font-family:"Calibri","sans-serif";
color:#1F497D;}
span.EmailStyle36
{mso-style-type:personal;
font-family:"Calibri","sans-serif";
color:#1F497D;}
span.EmailStyle37
{mso-style-type:personal;
font-family:"Calibri","sans-serif";
color:#1F497D;}
span.EmailStyle38
{mso-style-type:personal-reply;
font-family:"Calibri","sans-serif";
color:#1F497D;}
.MsoChpDefault
{mso-style-type:export-only;
font-size:10.0pt;}
@page Section1
{size:8.5in 11.0in;
margin:1.0in 1.25in 1.0in 1.25in;}
div.Section1
{page:Section1;}
/* List Definitions */
@list l0
{mso-list-id:1813861629;
mso-list-type:hybrid;
mso-list-template-ids:-813300246 -253878180 67698691 67698693 67698689 67698691 67698693 67698689 67698691 67698693;}
@list l0:level1
{mso-level-number-format:bullet;
mso-level-text:\F0D8;
mso-level-tab-stop:none;
mso-level-number-position:left;
text-indent:-.25in;
font-family:Wingdings;
mso-fareast-font-family:Calibri;
mso-bidi-font-family:"Times New Roman";}
@list l0:level2
{mso-level-tab-stop:1.0in;
mso-level-number-position:left;
text-indent:-.25in;}
@list l0:level3
{mso-level-tab-stop:1.5in;
mso-level-number-position:left;
text-indent:-.25in;}
@list l0:level4
{mso-level-tab-stop:2.0in;
mso-level-number-position:left;
text-indent:-.25in;}
@list l0:level5
{mso-level-tab-stop:2.5in;
mso-level-number-position:left;
text-indent:-.25in;}
@list l0:level6
{mso-level-tab-stop:3.0in;
mso-level-number-position:left;
text-indent:-.25in;}
@list l0:level7
{mso-level-tab-stop:3.5in;
mso-level-number-position:left;
text-indent:-.25in;}
@list l0:level8
{mso-level-tab-stop:4.0in;
mso-level-number-position:left;
text-indent:-.25in;}
@list l0:level9
{mso-level-tab-stop:4.5in;
mso-level-number-position:left;
text-indent:-.25in;}
ol
{margin-bottom:0in;}
ul
{margin-bottom:0in;}
-->
</style>
<!--[if gte mso 9]><xml>
<o:shapedefaults v:ext="edit" spidmax="1026" />
</xml><![endif]--><!--[if gte mso 9]><xml>
<o:shapelayout v:ext="edit">
<o:idmap v:ext="edit" data="1" />
</o:shapelayout></xml><![endif]-->
</head>
<body lang=EN-US link=blue vlink=purple style='text-justify-trim:punctuation'>
<div class=Section1>
<p class=MsoNormal><span style='font-size:11.0pt;color:#1F497D'>I’ll
second that. If you want to handle FDO errors that are provider agnostic then
handle FdoException or some of the new derived types which are being proposed
here. Otherwise, if you know the provider and want to handle the native code
you can do that as well.<o:p></o:p></span></p>
<p class=MsoNormal><span style='font-size:11.0pt;color:#1F497D'><o:p> </o:p></span></p>
<p class=MsoNormal><span style='font-size:11.0pt;color:#1F497D'>Alan<o:p></o:p></span></p>
<p class=MsoNormal><span style='font-size:11.0pt;color:#1F497D'><o:p> </o:p></span></p>
<div>
<div style='border:none;border-top:solid #B5C4DF 1.0pt;padding:3.0pt 0in 0in 0in'>
<p class=MsoNormal align=left style='text-align:left'><b><span
style='font-size:10.0pt;font-family:"Tahoma","sans-serif"'>From:</span></b><span
style='font-size:10.0pt;font-family:"Tahoma","sans-serif"'>
fdo-internals-bounces@lists.osgeo.org
[mailto:fdo-internals-bounces@lists.osgeo.org] <b>On Behalf Of </b>Greg Boone<br>
<b>Sent:</b> Thursday, June 18, 2009 8:11 AM<br>
<b>To:</b> FDO Internals Mail List<br>
<b>Subject:</b> RE: [fdo-internals] RE: FDO RFC 37 - Detailed Exception is readyfor
review.<o:p></o:p></span></p>
</div>
</div>
<p class=MsoNormal align=left style='text-align:left'><o:p> </o:p></p>
<p class=MsoNormal><span style='font-size:11.0pt;color:#1F497D'>Sorry….<o:p></o:p></span></p>
<p class=MsoNormal><span style='font-size:11.0pt;color:#1F497D'><o:p> </o:p></span></p>
<p class=MsoNormal><span style='font-size:11.0pt;color:#1F497D'>The reason I am
<b><u>not</u></b> in favor of having this native code mapped to a common FDO
code is that would a) require clients to jump through hoops to compile and
link, b) water down the original concept of returning the native code in the
first place. <o:p></o:p></span></p>
<p class=MsoNormal><span style='font-size:11.0pt;color:#1F497D'><o:p> </o:p></span></p>
<p class=MsoNormal><span style='font-size:11.0pt;color:#1F497D'><o:p> </o:p></span></p>
<div>
<div style='border:none;border-top:solid #B5C4DF 1.0pt;padding:3.0pt 0in 0in 0in'>
<p class=MsoNormal align=left style='text-align:left'><b><span
style='font-size:10.0pt;font-family:"Tahoma","sans-serif"'>From:</span></b><span
style='font-size:10.0pt;font-family:"Tahoma","sans-serif"'>
fdo-internals-bounces@lists.osgeo.org
[mailto:fdo-internals-bounces@lists.osgeo.org] <b>On Behalf Of </b>Greg Boone<br>
<b>Sent:</b> Thursday, June 18, 2009 11:05 AM<br>
<b>To:</b> FDO Internals Mail List<br>
<b>Subject:</b> RE: [fdo-internals] RE: FDO RFC 37 - Detailed Exception is
readyfor review.<o:p></o:p></span></p>
</div>
</div>
<p class=MsoNormal align=left style='text-align:left'><o:p> </o:p></p>
<p class=MsoNormal><span style='font-size:11.0pt;color:#1F497D'>As I see it,
the purpose of the additional method is to simply return the native error code
thrown by the underlying data store implementation. The purpose is not map it
to a common FDO error code. The reason I am in favor of having this native code
mapped to a common FDO code is that would a) require clients to jump through
hoops to compile and link, b) water down the original concept of returning the
native code in the first place. <o:p></o:p></span></p>
<p class=MsoNormal><span style='font-size:11.0pt;color:#1F497D'><o:p> </o:p></span></p>
<p class=MsoNormal><span style='font-size:11.0pt;color:#1F497D'>What the client
does with the error code is up to the client. <o:p></o:p></span></p>
<p class=MsoNormal><span style='font-size:11.0pt;color:#1F497D'><o:p> </o:p></span></p>
<p class=MsoNormal><span style='font-size:11.0pt;color:#1F497D'>Greg<o:p></o:p></span></p>
<p class=MsoNormal><span style='font-size:11.0pt;color:#1F497D'><o:p> </o:p></span></p>
<p class=MsoNormal><span style='font-size:11.0pt;color:#1F497D'><o:p> </o:p></span></p>
<div>
<div style='border:none;border-top:solid #B5C4DF 1.0pt;padding:3.0pt 0in 0in 0in'>
<p class=MsoNormal align=left style='text-align:left'><b><span
style='font-size:10.0pt;font-family:"Tahoma","sans-serif"'>From:</span></b><span
style='font-size:10.0pt;font-family:"Tahoma","sans-serif"'> fdo-internals-bounces@lists.osgeo.org
[mailto:fdo-internals-bounces@lists.osgeo.org] <b>On Behalf Of </b>Dan Stoica<br>
<b>Sent:</b> Thursday, June 18, 2009 10:53 AM<br>
<b>To:</b> FDO Internals Mail List<br>
<b>Subject:</b> RE: [fdo-internals] RE: FDO RFC 37 - Detailed Exception is
readyfor review.<o:p></o:p></span></p>
</div>
</div>
<p class=MsoNormal align=left style='text-align:left'><o:p> </o:p></p>
<p class=MsoNormal><span style='font-size:11.0pt;color:#1F497D'>The question
is: what is the caller going to do with this ‘native error code’?<o:p></o:p></span></p>
<p class=MsoNormal><span style='font-size:11.0pt;color:#1F497D'>If the purpose
is to get a ‘native error message’ then the answer is simple: he
doesn’t need it since this message is already available via GetCause()
and GetRootCause().<o:p></o:p></span></p>
<p class=MsoNormal><span style='font-size:11.0pt;color:#1F497D'><o:p> </o:p></span></p>
<p class=MsoNormal><span style='font-size:11.0pt;color:#1F497D'>Note: FdoException
allows chaining the exceptions. Which means the error code we need is the
deepest error code or…?<o:p></o:p></span></p>
<p class=MsoNormal><span style='font-size:11.0pt;color:#1F497D'><o:p> </o:p></span></p>
<p class=MsoNormal><span style='font-size:11.0pt;color:#1F497D'>Therefore </span><span
lang=EN style='font-size:10.0pt;font-family:"Courier New";color:black'>GetNativeErrorCode()</span><span
lang=EN style='font-size:12.0pt;color:#1F497D'>is not a proper name. It should
be GetErrorCode() instead and it should return FDO error codes as I suggested
before. I guess the application has to navigate down the chain and extract the
error code(s).<o:p></o:p></span></p>
<p class=MsoNormal><span lang=EN style='font-size:12.0pt;color:#1F497D'><o:p> </o:p></span></p>
<p class=MsoNormal><span lang=EN style='font-size:12.0pt;color:#1F497D'>Dan.</span><span
style='font-size:12.0pt;color:#1F497D'><o:p></o:p></span></p>
<p class=MsoNormal><span style='font-size:11.0pt;color:#1F497D'><o:p> </o:p></span></p>
<div>
<div style='border:none;border-top:solid #B5C4DF 1.0pt;padding:3.0pt 0in 0in 0in'>
<p class=MsoNormal align=left style='text-align:left'><b><span
style='font-size:10.0pt;font-family:"Tahoma","sans-serif"'>From:</span></b><span
style='font-size:10.0pt;font-family:"Tahoma","sans-serif"'>
fdo-internals-bounces@lists.osgeo.org
[mailto:fdo-internals-bounces@lists.osgeo.org] <b>On Behalf Of </b>Orest
Halustchak<br>
<b>Sent:</b> Thursday, June 18, 2009 9:07 AM<br>
<b>To:</b> FDO Internals Mail List<br>
<b>Subject:</b> RE: [fdo-internals] RE: FDO RFC 37 - Detailed Exception is
readyfor review.<o:p></o:p></span></p>
</div>
</div>
<p class=MsoNormal align=left style='text-align:left'><o:p> </o:p></p>
<p class=MsoNormal><span style='font-size:11.0pt;color:#1F497D'>I think this is
one of those things that are good in theory but in practice are hard to make work
and keep up to date with all the providers. Think also of the non-open source
commercial providers too and how this would fit. How does the agnostic list of
codes get kept up to date?<o:p></o:p></span></p>
<p class=MsoNormal><span style='font-size:11.0pt;color:#1F497D'><o:p> </o:p></span></p>
<p class=MsoNormal><span style='font-size:11.0pt;color:#1F497D'>Thanks,<o:p></o:p></span></p>
<p class=MsoNormal><span style='font-size:11.0pt;color:#1F497D'>Orest.<o:p></o:p></span></p>
<p class=MsoNormal><span style='font-size:11.0pt;color:#1F497D'><o:p> </o:p></span></p>
<div>
<div style='border:none;border-top:solid #B5C4DF 1.0pt;padding:3.0pt 0in 0in 0in'>
<p class=MsoNormal align=left style='text-align:left'><b><span
style='font-size:10.0pt;font-family:"Tahoma","sans-serif"'>From:</span></b><span
style='font-size:10.0pt;font-family:"Tahoma","sans-serif"'>
fdo-internals-bounces@lists.osgeo.org [mailto:fdo-internals-bounces@lists.osgeo.org]
<b>On Behalf Of </b>Trevor Wekel<br>
<b>Sent:</b> Wednesday, June 17, 2009 5:25 PM<br>
<b>To:</b> FDO Internals Mail List<br>
<b>Subject:</b> RE: [fdo-internals] RE: FDO RFC 37 - Detailed Exception is
readyfor review.<o:p></o:p></span></p>
</div>
</div>
<p class=MsoNormal align=left style='text-align:left'><o:p> </o:p></p>
<p class=MsoNormal><span style='font-size:11.0pt;color:#1F497D'>Could we add a
method “int GetAgnosticCode(int nativeCode)” to each Fdo provider
which would return a provider agnostic error code, if one exists, for the
native error code? The implementation would basically be an error code
lookup table coded specifically for each provider.<o:p></o:p></span></p>
<p class=MsoNormal><span style='font-size:11.0pt;color:#1F497D'><o:p> </o:p></span></p>
<p class=MsoNormal><span style='font-size:11.0pt;color:#1F497D'>External
applications could then call GetAgnosticCode and do something based on the
results.<o:p></o:p></span></p>
<p class=MsoNormal><span style='font-size:11.0pt;color:#1F497D'><o:p> </o:p></span></p>
<p class=MsoNormal><span style='font-size:11.0pt;color:#1F497D'>Trevor<o:p></o:p></span></p>
<p class=MsoNormal><span style='font-size:11.0pt;color:#1F497D'><o:p> </o:p></span></p>
<p class=MsoNormal><span style='font-size:11.0pt;color:#1F497D'><o:p> </o:p></span></p>
<p class=MsoNormal><span style='font-size:11.0pt;color:#1F497D'><o:p> </o:p></span></p>
<div>
<div style='border:none;border-top:solid #B5C4DF 1.0pt;padding:3.0pt 0in 0in 0in'>
<p class=MsoNormal align=left style='text-align:left'><b><span
style='font-size:10.0pt;font-family:"Tahoma","sans-serif"'>From:</span></b><span
style='font-size:10.0pt;font-family:"Tahoma","sans-serif"'>
fdo-internals-bounces@lists.osgeo.org
[mailto:fdo-internals-bounces@lists.osgeo.org] <b>On Behalf Of </b>Dan Stoica<br>
<b>Sent:</b> Wednesday, June 17, 2009 3:00 PM<br>
<b>To:</b> FDO Internals Mail List<br>
<b>Subject:</b> RE: [fdo-internals] RE: FDO RFC 37 - Detailed Exception is
readyfor review.<o:p></o:p></span></p>
</div>
</div>
<p class=MsoNormal align=left style='text-align:left'><o:p> </o:p></p>
<p class=MsoNormal><span style='font-size:11.0pt;color:#1F497D'>I can have an
error code = 714 for 3 different providers but meaning something different in
each case.<o:p></o:p></span></p>
<p class=MsoNormal><span style='font-size:11.0pt;color:#1F497D'>How is a
provider agnostic client supposed to interpret this number?<o:p></o:p></span></p>
<p class=MsoNormal><span style='font-size:11.0pt;color:#1F497D'><o:p> </o:p></span></p>
<p class=MsoNormal><span style='font-size:11.0pt;color:#1F497D'>Dan.<o:p></o:p></span></p>
<p class=MsoNormal><span style='font-size:11.0pt;color:#1F497D'><o:p> </o:p></span></p>
<div>
<div style='border:none;border-top:solid #B5C4DF 1.0pt;padding:3.0pt 0in 0in 0in'>
<p class=MsoNormal align=left style='text-align:left'><b><span
style='font-size:10.0pt;font-family:"Tahoma","sans-serif"'>From:</span></b><span
style='font-size:10.0pt;font-family:"Tahoma","sans-serif"'>
fdo-internals-bounces@lists.osgeo.org
[mailto:fdo-internals-bounces@lists.osgeo.org] <b>On Behalf Of </b>Haris
Kurtagic<br>
<b>Sent:</b> Wednesday, June 17, 2009 5:06 PM<br>
<b>To:</b> FDO Internals Mail List<br>
<b>Subject:</b> RE: [fdo-internals] RE: FDO RFC 37 - Detailed Exception is
readyfor review.<o:p></o:p></span></p>
</div>
</div>
<p class=MsoNormal align=left style='text-align:left'><o:p> </o:p></p>
<p class=MsoNormal><span style='font-size:11.0pt;color:#1F497D'>I agree with
that.<o:p></o:p></span></p>
<p class=MsoNormal><span style='font-size:11.0pt;color:#1F497D'>Haris<o:p></o:p></span></p>
<p class=MsoNormal><span style='font-size:11.0pt;color:#1F497D'><o:p> </o:p></span></p>
<div>
<div style='border:none;border-top:solid #B5C4DF 1.0pt;padding:3.0pt 0in 0in 0in'>
<p class=MsoNormal align=left style='text-align:left'><b><span
style='font-size:10.0pt;font-family:"Tahoma","sans-serif"'>From:</span></b><span
style='font-size:10.0pt;font-family:"Tahoma","sans-serif"'>
fdo-internals-bounces@lists.osgeo.org
[mailto:fdo-internals-bounces@lists.osgeo.org] <b>On Behalf Of </b>Orest
Halustchak<br>
<b>Sent:</b> Wednesday, June 17, 2009 10:45 PM<br>
<b>To:</b> FDO Internals Mail List<br>
<b>Subject:</b> RE: [fdo-internals] RE: FDO RFC 37 - Detailed Exception is
readyfor review.<o:p></o:p></span></p>
</div>
</div>
<p class=MsoNormal align=left style='text-align:left'><o:p> </o:p></p>
<p class=MsoNormal><span style='font-size:11.0pt;color:#1F497D'>I think if we
advertise “native” error code, then it should just be the code
returned by the underlying server. Yes, that will be different for different
providers. I’m also concerned about client applications writing a lot of
provider specific code, but I do understand that there will be cases where
applications will want this information and we should just pass it through. As
someone mentioned in a related thread, this is consistent with other data
access API’s out there.<o:p></o:p></span></p>
<p class=MsoNormal><span style='font-size:11.0pt;color:#1F497D'><o:p> </o:p></span></p>
<p class=MsoNormal><span style='font-size:11.0pt;color:#1F497D'>Thanks,<o:p></o:p></span></p>
<p class=MsoNormal><span style='font-size:11.0pt;color:#1F497D'>Orest.<o:p></o:p></span></p>
<p class=MsoNormal><span style='font-size:11.0pt;color:#1F497D'><o:p> </o:p></span></p>
<div>
<div style='border:none;border-top:solid #B5C4DF 1.0pt;padding:3.0pt 0in 0in 0in'>
<p class=MsoNormal align=left style='text-align:left'><b><span
style='font-size:10.0pt;font-family:"Tahoma","sans-serif"'>From:</span></b><span
style='font-size:10.0pt;font-family:"Tahoma","sans-serif"'>
fdo-internals-bounces@lists.osgeo.org
[mailto:fdo-internals-bounces@lists.osgeo.org] <b>On Behalf Of </b>Traian
Stanev<br>
<b>Sent:</b> Wednesday, June 17, 2009 4:38 PM<br>
<b>To:</b> FDO Internals Mail List<br>
<b>Subject:</b> RE: [fdo-internals] RE: FDO RFC 37 - Detailed Exception is
ready for review.<o:p></o:p></span></p>
</div>
</div>
<p class=MsoNormal align=left style='text-align:left'><o:p> </o:p></p>
<p class=MsoNormal><span style='font-size:11.0pt;color:#1F497D'><o:p> </o:p></span></p>
<p class=MsoNormal><span style='font-size:11.0pt;color:#1F497D'>Yes, like SHP.
Are the error codes also going to apply to the SHP provider for example? Is it
going to throw some kind of meaningful integer error code?<o:p></o:p></span></p>
<p class=MsoNormal><span style='font-size:11.0pt;color:#1F497D'><o:p> </o:p></span></p>
<p class=MsoNormal><span style='font-size:11.0pt;color:#1F497D'><o:p> </o:p></span></p>
<p class=MsoNormal><span style='font-size:11.0pt;color:#1F497D'><o:p> </o:p></span></p>
<div>
<div style='border:none;border-top:solid #B5C4DF 1.0pt;padding:3.0pt 0in 0in 0in'>
<p class=MsoNormal align=left style='text-align:left'><b><span
style='font-size:10.0pt;font-family:"Tahoma","sans-serif"'>From:</span></b><span
style='font-size:10.0pt;font-family:"Tahoma","sans-serif"'>
fdo-internals-bounces@lists.osgeo.org
[mailto:fdo-internals-bounces@lists.osgeo.org] <b>On Behalf Of </b>Dan Stoica<br>
<b>Sent:</b> Wednesday, June 17, 2009 4:35 PM<br>
<b>To:</b> FDO Internals Mail List<br>
<b>Subject:</b> RE: [fdo-internals] RE: FDO RFC 37 - Detailed Exception is
ready for review.<o:p></o:p></span></p>
</div>
</div>
<p class=MsoNormal align=left style='text-align:left'><o:p> </o:p></p>
<p class=MsoNormal><span style='font-size:11.0pt;color:#1F497D'>Like SHP?<o:p></o:p></span></p>
<p class=MsoNormal><span style='font-size:11.0pt;color:#1F497D'><o:p> </o:p></span></p>
<p class=MsoNormal><span style='font-size:11.0pt;color:#1F497D'>Dan.<o:p></o:p></span></p>
<p class=MsoNormal><span style='font-size:11.0pt;color:#1F497D'><o:p> </o:p></span></p>
<div>
<div style='border:none;border-top:solid #B5C4DF 1.0pt;padding:3.0pt 0in 0in 0in'>
<p class=MsoNormal align=left style='text-align:left'><b><span
style='font-size:10.0pt;font-family:"Tahoma","sans-serif"'>From:</span></b><span
style='font-size:10.0pt;font-family:"Tahoma","sans-serif"'>
fdo-internals-bounces@lists.osgeo.org
[mailto:fdo-internals-bounces@lists.osgeo.org] <b>On Behalf Of </b>Traian
Stanev<br>
<b>Sent:</b> Wednesday, June 17, 2009 4:29 PM<br>
<b>To:</b> FDO Internals Mail List<br>
<b>Subject:</b> RE: [fdo-internals] RE: FDO RFC 37 - Detailed Exception is
ready for review.<o:p></o:p></span></p>
</div>
</div>
<p class=MsoNormal align=left style='text-align:left'><o:p> </o:p></p>
<p class=MsoNormal><span style='font-size:11.0pt;color:#1F497D'><o:p> </o:p></span></p>
<p class=MsoNormal><span style='font-size:11.0pt;color:#1F497D'>OK so it can be
common for providers based on the FdoRdbms code, but there are a dozen other
providers. What about them?<o:p></o:p></span></p>
<p class=MsoNormal><span style='font-size:11.0pt;color:#1F497D'><o:p> </o:p></span></p>
<p class=MsoNormal><span style='font-size:11.0pt;color:#1F497D'>Traian<o:p></o:p></span></p>
<p class=MsoNormal><span style='font-size:11.0pt;color:#1F497D'><o:p> </o:p></span></p>
<p class=MsoNormal><span style='font-size:11.0pt;color:#1F497D'><o:p> </o:p></span></p>
<div>
<div style='border:none;border-top:solid #B5C4DF 1.0pt;padding:3.0pt 0in 0in 0in'>
<p class=MsoNormal align=left style='text-align:left'><b><span
style='font-size:10.0pt;font-family:"Tahoma","sans-serif"'>From:</span></b><span
style='font-size:10.0pt;font-family:"Tahoma","sans-serif"'>
fdo-internals-bounces@lists.osgeo.org [mailto:fdo-internals-bounces@lists.osgeo.org]
<b>On Behalf Of </b>Dan Stoica<br>
<b>Sent:</b> Wednesday, June 17, 2009 4:27 PM<br>
<b>To:</b> FDO Internals Mail List<br>
<b>Subject:</b> RE: [fdo-internals] RE: FDO RFC 37 - Detailed Exception is
ready for review.<o:p></o:p></span></p>
</div>
</div>
<p class=MsoNormal align=left style='text-align:left'><o:p> </o:p></p>
<p class=MsoListParagraph style='text-indent:-.25in;mso-list:l0 level1 lfo2'><![if !supportLists]><span
style='font-size:11.0pt;font-family:Wingdings;color:#1F497D'><span
style='mso-list:Ignore'>Ø<span style='font:7.0pt "Times New Roman"'> </span></span></span><![endif]><span
style='font-size:11.0pt;color:#1F497D'>Do SQLServer and Oracle have the same
error codes?<o:p></o:p></span></p>
<p class=MsoNormal><span style='font-size:12.0pt;color:#1F497D'><o:p> </o:p></span></p>
<p class=MsoNormal><span style='font-size:12.0pt;color:#1F497D'>No, they
don’t. This is my point, e.g. OCIDR_RDBI_END_OF_FETCH can be mapped to
RDBI_END_OF_FETCH and such type of error is common to SQLServer, MySql etc. I
suppose it’s not a crime to also have RDBI_ORA_xxx for specific cases
(oddities).<o:p></o:p></span></p>
<p class=MsoNormal><span style='font-size:12.0pt;color:#1F497D'><o:p> </o:p></span></p>
<p class=MsoNormal><span style='font-size:12.0pt;color:#1F497D'>Currently we get
a localized “End of fetch” message but not the error code. And the
native error message is lost along the way, although FdoException allows for a
‘cause’ detail…<o:p></o:p></span></p>
<p class=MsoNormal><span style='font-size:12.0pt;color:#1F497D'><o:p> </o:p></span></p>
<p class=MsoNormal><span style='font-size:12.0pt;color:#1F497D'>Dan.<o:p></o:p></span></p>
<p class=MsoNormal><span style='font-size:11.0pt;color:#1F497D'><o:p> </o:p></span></p>
<div>
<div style='border:none;border-top:solid #B5C4DF 1.0pt;padding:3.0pt 0in 0in 0in'>
<p class=MsoNormal align=left style='text-align:left'><b><span
style='font-size:10.0pt;font-family:"Tahoma","sans-serif"'>From:</span></b><span
style='font-size:10.0pt;font-family:"Tahoma","sans-serif"'>
fdo-internals-bounces@lists.osgeo.org [mailto:fdo-internals-bounces@lists.osgeo.org]
<b>On Behalf Of </b>Traian Stanev<br>
<b>Sent:</b> Wednesday, June 17, 2009 4:06 PM<br>
<b>To:</b> FDO Internals Mail List<br>
<b>Subject:</b> RE: [fdo-internals] RE: FDO RFC 37 - Detailed Exception is
ready for review.<o:p></o:p></span></p>
</div>
</div>
<p class=MsoNormal align=left style='text-align:left'><o:p> </o:p></p>
<p class=MsoNormal><span style='font-size:11.0pt;color:#1F497D'><o:p> </o:p></span></p>
<p class=MsoNormal><span style='font-size:11.0pt;color:#1F497D'>My assumption
was that the integer error codes would be potentially different for each
provider, since the RFC mentions native error codes for SQLServer and Oracle.
Do SQLServer and Oracle have the same error codes?<o:p></o:p></span></p>
<p class=MsoNormal><span style='font-size:11.0pt;color:#1F497D'><o:p> </o:p></span></p>
<p class=MsoNormal><span style='font-size:11.0pt;color:#1F497D'>Traian<o:p></o:p></span></p>
<p class=MsoNormal><span style='font-size:11.0pt;color:#1F497D'><o:p> </o:p></span></p>
<p class=MsoNormal><span style='font-size:11.0pt;color:#1F497D'><o:p> </o:p></span></p>
<div>
<div style='border:none;border-top:solid #B5C4DF 1.0pt;padding:3.0pt 0in 0in 0in'>
<p class=MsoNormal align=left style='text-align:left'><b><span
style='font-size:10.0pt;font-family:"Tahoma","sans-serif"'>From:</span></b><span
style='font-size:10.0pt;font-family:"Tahoma","sans-serif"'>
fdo-internals-bounces@lists.osgeo.org
[mailto:fdo-internals-bounces@lists.osgeo.org] <b>On Behalf Of </b>Dan Stoica<br>
<b>Sent:</b> Wednesday, June 17, 2009 3:59 PM<br>
<b>To:</b> FDO Internals Mail List<br>
<b>Subject:</b> RE: [fdo-internals] RE: FDO RFC 37 - Detailed Exception is
ready for review.<o:p></o:p></span></p>
</div>
</div>
<p class=MsoNormal align=left style='text-align:left'><o:p> </o:p></p>
<p class=MsoNormal><span style='font-size:11.0pt;color:#1F497D'>Talking about
the native error codes apparently the RFC doesn’t say how they look like…<o:p></o:p></span></p>
<p class=MsoNormal><span style='font-size:11.0pt;color:#1F497D'><o:p> </o:p></span></p>
<p class=MsoNormal><span style='font-size:11.0pt;color:#1F497D'>In my mind the
native error codes are not necessary a direct mapping to </span><em><span
style='font-family:"Arial","sans-serif";color:#1F497D'>ORA</span></em><span
style='font-family:"Arial","sans-serif";color:#1F497D'>-02429, for example. A
rdbms driver has limited ability to extract the exact cause anyways. (Even the
native error messages are sometimes very cryptic or ambiguous or both) Therefore
the numerical ‘native’ error code is in fact ‘low
level’ error code and provider agnostic like </span><span
style='font-size:10.0pt;font-family:"Courier New"'>RDBI_DATA_TRUNCATED</span><span
style='font-family:"Arial","sans-serif";color:#1F497D'>.<o:p></o:p></span></p>
<p class=MsoNormal><span style='font-family:"Arial","sans-serif";color:#1F497D'><o:p> </o:p></span></p>
<p class=MsoNormal><span style='font-family:"Arial","sans-serif";color:#1F497D'>Dan.</span><span
style='font-size:11.0pt;color:#1F497D'><o:p></o:p></span></p>
<p class=MsoNormal><span style='font-size:11.0pt;color:#1F497D'><o:p> </o:p></span></p>
<div>
<div style='border:none;border-top:solid #B5C4DF 1.0pt;padding:3.0pt 0in 0in 0in'>
<p class=MsoNormal align=left style='text-align:left'><b><span
style='font-size:10.0pt;font-family:"Tahoma","sans-serif"'>From:</span></b><span
style='font-size:10.0pt;font-family:"Tahoma","sans-serif"'>
fdo-internals-bounces@lists.osgeo.org
[mailto:fdo-internals-bounces@lists.osgeo.org] <b>On Behalf Of </b>Traian
Stanev<br>
<b>Sent:</b> Wednesday, June 17, 2009 12:04 PM<br>
<b>To:</b> FDO Internals Mail List<br>
<b>Subject:</b> RE: [fdo-internals] RE: FDO RFC 37 - Detailed Exception is
ready for review.<o:p></o:p></span></p>
</div>
</div>
<p class=MsoNormal align=left style='text-align:left'><o:p> </o:p></p>
<p class=MsoNormal><span style='font-size:11.0pt;color:#1F497D'><o:p> </o:p></span></p>
<p class=MsoNormal><span style='font-size:11.0pt;color:#1F497D'>My main concern
is that having native error codes encourages the client code to be non-generic,
in that it would have to know which provider it is working with, in order to
handle the native error code correctly. Of course, that is a concern about the
client code, not FDO itself, so the client code is free to handle this any way
it wants… including in bad ways.<o:p></o:p></span></p>
<p class=MsoNormal><span style='font-size:11.0pt;color:#1F497D'><o:p> </o:p></span></p>
<p class=MsoNormal><span style='font-size:11.0pt;color:#1F497D'>Traian<o:p></o:p></span></p>
<p class=MsoNormal><span style='font-size:11.0pt;color:#1F497D'><o:p> </o:p></span></p>
<p class=MsoNormal><span style='font-size:11.0pt;color:#1F497D'><o:p> </o:p></span></p>
<div>
<div style='border:none;border-top:solid #B5C4DF 1.0pt;padding:3.0pt 0in 0in 0in'>
<p class=MsoNormal align=left style='text-align:left'><b><span
style='font-size:10.0pt;font-family:"Tahoma","sans-serif"'>From:</span></b><span
style='font-size:10.0pt;font-family:"Tahoma","sans-serif"'>
fdo-internals-bounces@lists.osgeo.org
[mailto:fdo-internals-bounces@lists.osgeo.org] <b>On Behalf Of </b>Dan Stoica<br>
<b>Sent:</b> Tuesday, June 16, 2009 10:10 AM<br>
<b>To:</b> FDO Internals Mail List<br>
<b>Subject:</b> [fdo-internals] RE: FDO RFC 37 - Detailed Exception is ready
for review.<o:p></o:p></span></p>
</div>
</div>
<p class=MsoNormal align=left style='text-align:left'><o:p> </o:p></p>
<div style='border:solid #D7D7D7 1.0pt;padding:3.0pt 3.0pt 3.0pt 3.0pt'>
<p class=MsoNormal align=left style='mso-margin-top-alt:12.0pt;margin-right:
28.5pt;margin-bottom:12.0pt;margin-left:28.5pt;text-align:left;background:#F7F7F7'><span
lang=EN style='font-size:10.0pt;font-family:"Courier New";color:black'>catch
(FdoException* e)<br>
{<br>
FdoInt64 errorCode = e->GetNativeErrorCode();<br>
e->Release();<o:p></o:p></span></p>
<p class=MsoNormal align=left style='mso-margin-top-alt:12.0pt;margin-right:
28.5pt;margin-bottom:12.0pt;margin-left:28.5pt;text-align:left;background:#F7F7F7'><span
lang=EN style='font-size:10.0pt;font-family:"Courier New";color:black'>
// Take some measures according to native error code<br>
......<br>
}<o:p></o:p></span></p>
</div>
<p class=MsoNormal><span style='font-size:11.0pt;color:#1F497D'>I think no matter
how many exception subclasses are invented, the only useful thing for handling
the error is the error code.<o:p></o:p></span></p>
<p class=MsoNormal><span style='font-size:11.0pt;color:#1F497D'><o:p> </o:p></span></p>
<p class=MsoNormal><span style='font-size:11.0pt;color:#1F497D'>And I said
before, another very useful thing to have is the ability to distinguish between
errors and warnings.<o:p></o:p></span></p>
<p class=MsoNormal><span style='font-size:11.0pt;color:#1F497D'><o:p> </o:p></span></p>
<p class=MsoNormal><span style='font-size:11.0pt;color:#1F497D'>Dan.<o:p></o:p></span></p>
<p class=MsoNormal><span style='font-size:11.0pt;color:#1F497D'><o:p> </o:p></span></p>
<div>
<div style='border:none;border-top:solid #B5C4DF 1.0pt;padding:3.0pt 0in 0in 0in'>
<p class=MsoNormal align=left style='text-align:left'><b><span
style='font-size:10.0pt;font-family:"Tahoma","sans-serif"'>From:</span></b><span
style='font-size:10.0pt;font-family:"Tahoma","sans-serif"'> fdo-internals-bounces@lists.osgeo.org
[mailto:fdo-internals-bounces@lists.osgeo.org] <b>On Behalf Of </b>Leaf Li<br>
<b>Sent:</b> Monday, June 15, 2009 9:37 PM<br>
<b>To:</b> fdo-internals@lists.osgeo.org<br>
<b>Subject:</b> [fdo-internals] FDO RFC 37 - Detailed Exception is ready for
review.<o:p></o:p></span></p>
</div>
</div>
<p class=MsoNormal align=left style='text-align:left'><o:p> </o:p></p>
<p class=MsoNormal>All,<o:p></o:p></p>
<p class=MsoNormal><o:p> </o:p></p>
<p class=MsoNormal>FDO RFC 37 - Detailed Exception is ready for review. Can you
review it?<o:p></o:p></p>
<p class=MsoNormal><a href="http://trac.osgeo.org/fdo/wiki/FDORfc37">http://trac.osgeo.org/fdo/wiki/FDORfc37</a><o:p></o:p></p>
<p class=MsoNormal><o:p> </o:p></p>
<p class=MsoNormal>Thanks,<o:p></o:p></p>
<p class=MsoNormal>Leaf Li<o:p></o:p></p>
</div>
</body>
</html>