<!DOCTYPE HTML PUBLIC "-//W3C//DTD HTML 4.0 Transitional//EN">
<html>
<head>
<meta http-equiv=Content-Type content="text/html; charset=us-ascii">
<meta name=Generator content="Microsoft Word 10 (filtered)">
<style>
<!--
/* Font Definitions */
@font-face
{font-family:PMingLiU;
panose-1:2 2 3 0 0 0 0 0 0 0;}
@font-face
{font-family:Tahoma;
panose-1:2 11 6 4 3 5 4 4 2 4;}
@font-face
{font-family:"\@PMingLiU";
panose-1:2 2 3 0 0 0 0 0 0 0;}
/* Style Definitions */
p.MsoNormal, li.MsoNormal, div.MsoNormal
{margin:0cm;
margin-bottom:.0001pt;
font-size:12.0pt;
font-family:"Times New Roman";}
a:link, span.MsoHyperlink
{color:blue;
text-decoration:underline;}
a:visited, span.MsoHyperlinkFollowed
{color:blue;
text-decoration:underline;}
span.EmailStyle17
{font-family:Arial;
color:navy;}
@page Section1
{size:612.0pt 792.0pt;
margin:72.0pt 90.0pt 72.0pt 90.0pt;}
div.Section1
{page:Section1;}
-->
</style>
</head>
<body lang=EN-US link=blue vlink=blue>
<div class=Section1>
<p class=MsoNormal><font size=2 color=navy face=Arial><span style='font-size:
10.0pt;font-family:Arial;color:navy'>Hi Haris,</span></font></p>
<p class=MsoNormal><font size=2 color=navy face=Arial><span style='font-size:
10.0pt;font-family:Arial;color:navy'> </span></font></p>
<p class=MsoNormal><font size=2 color=navy face=Arial><span style='font-size:
10.0pt;font-family:Arial;color:navy'>The Schema Mappings tend to be
provider-specific, since they map feature schema elements onto physical
elements for the provider. There aren’t any mappings common to all
providers, for example, the Raster Provider maps elements onto files while the
RDBMS Providers maps them to tables and columns. Some providers, such as SDF,
don’t have any overridable schema mappings. Therefore the FdoPhysicalSchemaMapping
class doesn’t contain much other than schema name and provider name. Getting
to the actual mappings requires knowledge of the provider’s
implementation of FdoPhysicalSchemaMapping. </span></font></p>
<p class=MsoNormal><font size=2 color=navy face=Arial><span style='font-size:
10.0pt;font-family:Arial;color:navy'> </span></font></p>
<p class=MsoNormal><font size=2 color=navy face=Arial><span style='font-size:
10.0pt;font-family:Arial;color:navy'>There is a lot of commonality between the
RDBMS providers so there is an FdoRdbmsOverrides package where the common
mappings are defined. A lot of the schema mappings for RDBMS providers can be
retrieved through the FdoRdbmsOvPhysicalSchemaMapping class.</span></font></p>
<p class=MsoNormal><font size=2 color=navy face=Arial><span style='font-size:
10.0pt;font-family:Arial;color:navy'> </span></font></p>
<p class=MsoNormal><font size=2 color=navy face=Arial><span style='font-size:
10.0pt;font-family:Arial;color:navy'>Brent.</span></font></p>
<p class=MsoNormal><font size=2 color=navy face=Arial><span style='font-size:
10.0pt;font-family:Arial;color:navy'> </span></font></p>
<p class=MsoNormal style='margin-left:36.0pt'><font size=2 face=Tahoma><span
style='font-size:10.0pt;font-family:Tahoma'>-----Original Message-----<br>
<b><span style='font-weight:bold'>From:</span></b> Haris Kurtagic
[mailto:haris@sl-king.com] <br>
<b><span style='font-weight:bold'>Sent:</span></b> Wednesday, October 25, 2006
12:57 PM<br>
<b><span style='font-weight:bold'>To:</span></b> dev@fdo.osgeo.org<br>
<b><span style='font-weight:bold'>Subject:</span></b> RE: [fdo-dev] fdo 3.2</span></font></p>
<p class=MsoNormal style='margin-left:36.0pt'><font size=3
face="Times New Roman"><span style='font-size:12.0pt'> </span></font></p>
<p class=MsoNormal style='margin-left:36.0pt'><font size=2 color=blue
face=Arial><span style='font-size:10.0pt;font-family:Arial;color:blue'>Hi
Orest,</span></font></p>
<p class=MsoNormal style='margin-left:36.0pt'><font size=3
face="Times New Roman"><span style='font-size:12.0pt'> </span></font></p>
<p class=MsoNormal style='margin-left:36.0pt'><font size=2 color=blue
face=Arial><span style='font-size:10.0pt;font-family:Arial;color:blue'>1. I
agree that most provider would support it differently</span></font></p>
<p class=MsoNormal style='margin-left:36.0pt'><font size=2 color=blue
face=Arial><span style='font-size:10.0pt;font-family:Arial;color:blue'> I
suppose query of data based on rectangle of interest would be one of the most
common thing provider would do.</span></font></p>
<p class=MsoNormal style='margin-left:36.0pt'><font size=3
face="Times New Roman"><span style='font-size:12.0pt'> </span></font></p>
<p class=MsoNormal style='margin-left:36.0pt'><font size=2 color=blue
face=Arial><span style='font-size:10.0pt;font-family:Arial;color:blue'>2. So
allowing different character set could and up in different class name's
eventually.</span></font></p>
<p class=MsoNormal style='margin-left:36.0pt'><font size=3
face="Times New Roman"><span style='font-size:12.0pt'> </span></font><font
size=2 color=blue face=Arial><span style='font-size:10.0pt;font-family:Arial;
color:blue'>I am using Physical/logical mapping inside provider.</span></font></p>
<p class=MsoNormal style='margin-left:36.0pt'><font size=2 color=blue
face=Arial><span style='font-size:10.0pt;font-family:Arial;color:blue'>
</span></font></p>
<p class=MsoNormal style='margin-left:36.0pt'><font size=2 color=blue
face=Arial><span style='font-size:10.0pt;font-family:Arial;color:blue'>I would
appreciate if you can help me: I don't understand how to use <a
href="https://fdo.osgeo.org/nonav/docs/FDO_API/d7/d94/class_fdo_physical_schema_mapping.html"><font
size=3 face="Times New Roman"><span style='font-size:12.0pt;font-family:"Times New Roman"'>FdoPhysicalSchemaMapping</span></font></a> outside
provider or rather to say it, use it without knowing specific provider class
sub implementation.</span></font></p>
<p class=MsoNormal style='margin-left:36.0pt'><font size=2 color=blue
face=Arial><span style='font-size:10.0pt;font-family:Arial;color:blue'>I see in
interface functions like GetName or GetQualifiedName but don't see how to get
logical name and physical mapping for it.</span></font></p>
<p class=MsoNormal style='margin-left:36.0pt'><font size=3
face="Times New Roman"><span style='font-size:12.0pt'> </span></font></p>
<p class=MsoNormal style='margin-left:36.0pt'><font size=2 color=blue
face=Arial><span style='font-size:10.0pt;font-family:Arial;color:blue'>Haris</span></font></p>
<p class=MsoNormal style='margin-left:36.0pt'><font size=3
face="Times New Roman"><span style='font-size:12.0pt'> </span></font></p>
<div class=MsoNormal align=center style='margin-left:36.0pt;text-align:center'><font
size=3 face="Times New Roman"><span style='font-size:12.0pt'>
<hr size=2 width="100%" align=center>
</span></font></div>
<p class=MsoNormal style='margin-right:0cm;margin-bottom:12.0pt;margin-left:
36.0pt'><b><font size=2 face=Tahoma><span style='font-size:10.0pt;font-family:
Tahoma;font-weight:bold'>From:</span></font></b><font size=2 face=Tahoma><span
style='font-size:10.0pt;font-family:Tahoma'> Orest Halustchak
[mailto:orest.halustchak@autodesk.com] <br>
<b><span style='font-weight:bold'>Sent:</span></b> Wednesday, October 25, 2006
4:25 PM<br>
<b><span style='font-weight:bold'>To:</span></b> dev@fdo.osgeo.org<br>
<b><span style='font-weight:bold'>Subject:</span></b> RE: [fdo-dev] fdo 3.2</span></font></p>
<p class=MsoNormal style='margin-left:36.0pt'><font size=2 color=blue
face=Arial><span style='font-size:10.0pt;font-family:Arial;color:blue'>Hi
Haris,</span></font></p>
<p class=MsoNormal style='margin-left:36.0pt'><font size=3
face="Times New Roman"><span style='font-size:12.0pt'> </span></font></p>
<p class=MsoNormal style='margin-left:36.0pt'><font size=2 color=blue
face=Arial><span style='font-size:10.0pt;font-family:Arial;color:blue'>Comments
below ...</span></font></p>
<p class=MsoNormal style='margin-left:36.0pt'><font size=3
face="Times New Roman"><span style='font-size:12.0pt'> </span></font></p>
<p class=MsoNormal style='margin-left:36.0pt'><font size=2 color=blue
face=Arial><span style='font-size:10.0pt;font-family:Arial;color:blue'>Thanks,</span></font></p>
<p class=MsoNormal style='margin-left:36.0pt'><font size=2 color=blue
face=Arial><span style='font-size:10.0pt;font-family:Arial;color:blue'>Orest.</span></font></p>
<p class=MsoNormal style='margin-left:36.0pt'><font size=3
face="Times New Roman"><span style='font-size:12.0pt'> </span></font></p>
<div class=MsoNormal align=center style='margin-left:36.0pt;text-align:center'><font
size=3 face="Times New Roman"><span style='font-size:12.0pt'>
<hr size=2 width="100%" align=center>
</span></font></div>
<p class=MsoNormal style='margin-right:0cm;margin-bottom:12.0pt;margin-left:
36.0pt'><b><font size=2 face=Tahoma><span style='font-size:10.0pt;font-family:
Tahoma;font-weight:bold'>From:</span></font></b><font size=2 face=Tahoma><span
style='font-size:10.0pt;font-family:Tahoma'> Haris Kurtagic
[mailto:haris@sl-king.com] <br>
<b><span style='font-weight:bold'>Sent:</span></b> Wednesday, October 25, 2006
6:53 AM<br>
<b><span style='font-weight:bold'>To:</span></b> dev@fdo.osgeo.org<br>
<b><span style='font-weight:bold'>Subject:</span></b> [fdo-dev] fdo 3.2</span></font></p>
<div>
<p class=MsoNormal style='margin-left:36.0pt'><font size=2 face=Arial><span
style='font-size:10.0pt;font-family:Arial'>I've read FDO 3.2 changes, and it
looks like good changes.</span></font></p>
</div>
<div>
<p class=MsoNormal style='margin-left:36.0pt'><font size=2 face=Arial><span
style='font-size:10.0pt;font-family:Arial'>One of things if I understood
correctly is that we will be able to use any characters in schema.<font
color=blue><span style='color:blue'> </span></font></span></font></p>
</div>
<div>
<p class=MsoNormal style='margin-left:36.0pt'><font size=2 color=blue
face=Arial><span style='font-size:10.0pt;font-family:Arial;color:blue'>[Orest]
The provider can specify which characters are not allowed in a name. But, if
one provider decides to support a character that is not supported by other
providers, you may have problems applying schema used in one provider against
another provider unless you handle some sort of name mangling.</span></font></p>
</div>
<div>
<p class=MsoNormal style='margin-left:36.0pt'><font size=3
face="Times New Roman"><span style='font-size:12.0pt'> </span></font></p>
</div>
<div>
<p class=MsoNormal style='margin-left:36.0pt'><font size=2 face=Arial><span
style='font-size:10.0pt;font-family:Arial'>I have couple of comments:</span></font></p>
</div>
<div>
<p class=MsoNormal style='margin-left:36.0pt'><font size=3
face="Times New Roman"><span style='font-size:12.0pt'> </span></font></p>
</div>
<div>
<p class=MsoNormal style='margin-left:36.0pt'><font size=2 face=Arial><span
style='font-size:10.0pt;font-family:Arial'>1. I saw changes in defining more
exactly geometry type - good.</span></font></p>
</div>
<div>
<p class=MsoNormal style='margin-left:36.0pt'><font size=2 face=Arial><span
style='font-size:10.0pt;font-family:Arial'>I miss very much rectangle or
optimized rectangle especially in queries.</span></font></p>
</div>
<div>
<p class=MsoNormal style='margin-left:36.0pt'><font size=2 face=Arial><span
style='font-size:10.0pt;font-family:Arial'>Now in filter provider gets polygon
for some actions in MG, but basically it is rectangle and</span></font></p>
</div>
<div>
<p class=MsoNormal style='margin-left:36.0pt'><font size=2 face=Arial><span
style='font-size:10.0pt;font-family:Arial'>for some providers like for Oracle
is important to know if it is rectangle or really polygon.</span></font></p>
</div>
<div>
<p class=MsoNormal style='margin-left:36.0pt'><font size=2 face=Arial><span
style='font-size:10.0pt;font-family:Arial'>Of course, provider can figure it
out from points but it is no way it should be.<font color=blue><span
style='color:blue'> </span></font></span></font></p>
</div>
<div>
<p class=MsoNormal style='margin-left:36.0pt'><font size=3
face="Times New Roman"><span style='font-size:12.0pt'> </span></font></p>
</div>
<div>
<p class=MsoNormal style='margin-left:36.0pt'><font size=2 color=blue
face=Arial><span style='font-size:10.0pt;font-family:Arial;color:blue'>[Orest]
The FGF polygon in this case is derived from the OGC simple feature spec
which I don't believe has an explicit optimized rectangle representation such
as in Oracle. While this is something Oracle supports, other targets may
not have such capabilities. It is something that possibly could be added
to the FGF spec, but we would then need to add a capability for
providers to indicate that they don't handle that polygon representation.</span></font><font
size=2 face=Arial><span style='font-size:10.0pt;font-family:Arial'> </span></font></p>
</div>
<div>
<p class=MsoNormal style='margin-left:36.0pt'><font size=3
face="Times New Roman"><span style='font-size:12.0pt'> </span></font></p>
</div>
<div>
<p class=MsoNormal style='margin-left:36.0pt'><font size=2 face=Arial><span
style='font-size:10.0pt;font-family:Arial'>2. After coping fdo class from one
provider to another, trough AplySchema, it is difficult to get class
definitions from newly created classes.</span></font></p>
</div>
<div>
<p class=MsoNormal style='margin-left:36.0pt'><font size=2 face=Arial><span
style='font-size:10.0pt;font-family:Arial'> Geometry/Class/schema
name can be changed from one provider to another.</span></font></p>
</div>
<div>
<p class=MsoNormal style='margin-left:36.0pt'><font size=2 face=Arial><span
style='font-size:10.0pt;font-family:Arial'> It would be nice to
have reader (like for insert geometries) which would return map original
class-new class, so the procedure is not dependent on keeping same names.<font
color=blue><span style='color:blue'> </span></font></span></font></p>
</div>
<div>
<p class=MsoNormal style='margin-left:36.0pt'><font size=3
face="Times New Roman"><span style='font-size:12.0pt'> </span></font></p>
</div>
<div>
<p class=MsoNormal style='margin-left:36.0pt'><font size=2 color=blue
face=Arial><span style='font-size:10.0pt;font-family:Arial;color:blue'>[Orest]
Fdo does not expect that the class name would be changed by the provider. That
is, if you define a particular class name with apply schema, a subsequent
describe schema would return the same class name. A provider may
limit the allowable class names via length limits and valid characters. Note
that class names in FDO are logical schema concepts as opposed to
physical schema concepts such as table names. Providers that can support a
logical / physical mapping will map class names to table names where a
class name may not be identical to the physical table name.</span></font></p>
</div>
<div>
<p class=MsoNormal style='margin-left:36.0pt'><font size=3
face="Times New Roman"><span style='font-size:12.0pt'> </span></font></p>
</div>
<div>
<p class=MsoNormal style='margin-left:36.0pt'><font size=2 face=Arial><span
style='font-size:10.0pt;font-family:Arial'>Haris</span></font></p>
</div>
</div>
</body>
</html>