<br><br><div class="gmail_quote">On Fri, Oct 30, 2009 at 1:10 AM, Brent Robinson <span dir="ltr"><<a href="mailto:brent.robinson@autodesk.com">brent.robinson@autodesk.com</a>></span> wrote:<br><blockquote class="gmail_quote" style="border-left: 1px solid rgb(204, 204, 204); margin: 0pt 0pt 0pt 0.8ex; padding-left: 1ex;">
<div link="blue" vlink="purple" lang="EN-US">
<div>
<p class="MsoNormal"><span style="font-size: 11pt; color: rgb(31, 73, 125);">Hi Zac,</span></p>
<p class="MsoNormal"><span style="font-size: 11pt; color: rgb(31, 73, 125);"> </span></p>
<p class="MsoNormal"><span style="font-size: 11pt; color: rgb(31, 73, 125);">I had a look at RFC 43 and had a few questions regarding the
MySQL provider:</span></p>
<p class="MsoNormal" style="margin-left: 0.5in;"><span style="font-size: 11pt; color: rgb(31, 73, 125);"> </span></p>
<p style="margin-left: 29.25pt;"><span style="font-size: 11pt; color: rgb(31, 73, 125);"><span>1.<span style="font-family: "Times New Roman"; font-style: normal; font-variant: normal; font-weight: normal; font-size: 7pt; line-height: normal; font-size-adjust: none; font-stretch: normal;"> </span></span></span><span style="font-size: 11pt; color: rgb(31, 73, 125);">Do
the naming conventions apply only to MySQL databases that do not have FDO
MetaData? </span></p></div></div></blockquote><div>FDO meta data describes a secondary set, I would assume the underlying tables would be always <br>exposed in the same fashion.. <br></div><blockquote class="gmail_quote" style="border-left: 1px solid rgb(204, 204, 204); margin: 0pt 0pt 0pt 0.8ex; padding-left: 1ex;">
<div link="blue" vlink="purple" lang="EN-US"><div>
<p class="MsoNormal" style="margin-left: 0.5in;"><span style="font-size: 11pt; color: rgb(31, 73, 125);"> <span>2.<span style="font-family: "Times New Roman"; font-style: normal; font-variant: normal; font-weight: normal; font-size: 7pt; line-height: normal; font-size-adjust: none; font-stretch: normal;"> </span></span></span><span style="font-size: 11pt; color: rgb(31, 73, 125);">For
the statement: <br></span></p>
<p class="MsoNormal" style="margin-left: 1in;"><span style="font-size: 11pt; color: rgb(31, 73, 125);">“MySql? returns
schema:tablename or if connected as "schema" then just tablename”</span></p>
<p class="MsoNormal" style="margin-left: 1in;"><span style="font-size: 11pt; color: rgb(31, 73, 125);"> </span></p>
<p class="MsoNormal" style="margin-left: 0.5in;"><span style="font-size: 11pt; color: rgb(31, 73, 125);">Is “schema”
equivalent to a MySQL database?</span></p></div></div></blockquote><div>That was my intention, I rarely use MySQL myself.. similiar to the oracle n sql server discussions <br></div><blockquote class="gmail_quote" style="border-left: 1px solid rgb(204, 204, 204); margin: 0pt 0pt 0pt 0.8ex; padding-left: 1ex;">
<div link="blue" vlink="purple" lang="EN-US"><div>
<p style="margin-left: 29.25pt;"><span style="font-size: 11pt; color: rgb(31, 73, 125);"> <span>3.<span style="font-family: "Times New Roman"; font-style: normal; font-variant: normal; font-weight: normal; font-size: 7pt; line-height: normal; font-size-adjust: none; font-stretch: normal;"> </span></span></span><span style="font-size: 11pt; color: rgb(31, 73, 125);">For
the case where the tables are exposed as in an empty schema, would that mean
that the DescribeSchema command would return a Feature Schema with blank name?
Or would there be a special name to represent the empty schema (e.g. “default”
or “none”).</span></p></div></div></blockquote><div>thats a really good question! We would want it describable if it's accessible, blank doesn't seem quite right,<br>but it does imply the default or none or current... <br>
<br>the unqualified name is a synonym for current_user.table_name <br> </div><blockquote class="gmail_quote" style="border-left: 1px solid rgb(204, 204, 204); margin: 0pt 0pt 0pt 0.8ex; padding-left: 1ex;"><div link="blue" vlink="purple" lang="EN-US">
<div>
<p class="MsoNormal"><span style="font-size: 11pt; color: rgb(31, 73, 125);"></span></p>
<p style="margin-left: 29.25pt;"><span style="font-size: 11pt; color: rgb(31, 73, 125);"><span>4.<span style="font-family: "Times New Roman"; font-style: normal; font-variant: normal; font-weight: normal; font-size: 7pt; line-height: normal; font-size-adjust: none; font-stretch: normal;"> </span></span></span><span style="font-size: 11pt; color: rgb(31, 73, 125);">What
sort of problems are you currently encountering without these naming conventions
being in place?</span></p></div></div></blockquote><div>As jackie mentioned at the top to the thread, the same data loaded under a different provider appears different <br>and thus cannot be just accessed without provider specific knowledge and coding workarounds<br>
</div><blockquote class="gmail_quote" style="border-left: 1px solid rgb(204, 204, 204); margin: 0pt 0pt 0pt 0.8ex; padding-left: 1ex;"><div link="blue" vlink="purple" lang="EN-US"><div>
<p style="margin-left: 47.25pt;"><span style="font-size: 11pt; color: rgb(31, 73, 125);"> <span>a.<span style="font-family: "Times New Roman"; font-style: normal; font-variant: normal; font-weight: normal; font-size: 7pt; line-height: normal; font-size-adjust: none; font-stretch: normal;"> </span></span></span><span style="font-size: 11pt; color: rgb(31, 73, 125);">Problems
copying schemas and features between providers?</span></p></div></div></blockquote><div>yes <br></div><blockquote class="gmail_quote" style="border-left: 1px solid rgb(204, 204, 204); margin: 0pt 0pt 0pt 0.8ex; padding-left: 1ex;">
<div link="blue" vlink="purple" lang="EN-US"><div>
<p style="margin-left: 47.25pt;"><span style="font-size: 11pt; color: rgb(31, 73, 125);"><span>b.<span style="font-family: "Times New Roman"; font-style: normal; font-variant: normal; font-weight: normal; font-size: 7pt; line-height: normal; font-size-adjust: none; font-stretch: normal;"> </span></span></span><span style="font-size: 11pt; color: rgb(31, 73, 125);">Problems
generating statements for the ISQLCommand?</span></p></div></div></blockquote><div>yes <br></div><blockquote class="gmail_quote" style="border-left: 1px solid rgb(204, 204, 204); margin: 0pt 0pt 0pt 0.8ex; padding-left: 1ex;">
<div link="blue" vlink="purple" lang="EN-US"><div>
<p class="MsoNormal"><span style="font-size: 11pt; color: rgb(31, 73, 125);"> </span></p>
<p class="MsoNormal"><span style="font-size: 11pt; color: rgb(31, 73, 125);">and a general question: are the conventions intended as
standards for all DBMS or file base providers or just the ones mentioned in the
RFC?</span></p></div></div></blockquote><div>It is intended as a standard for all providers, I have updated the RFC to reflect that <br></div><blockquote class="gmail_quote" style="border-left: 1px solid rgb(204, 204, 204); margin: 0pt 0pt 0pt 0.8ex; padding-left: 1ex;">
<div link="blue" vlink="purple" lang="EN-US"><div>
<p class="MsoNormal"><span style="font-size: 11pt; color: rgb(31, 73, 125);"> </span></p>
<p class="MsoNormal"><span style="font-size: 11pt; color: rgb(31, 73, 125);">If the answer to question 2 is yes then the MySQL provider is
currently close. The feature schema name is:</span></p>
<p class="MsoNormal"><span style="font-size: 11pt; color: rgb(31, 73, 125);"> </span></p>
<p class="MsoNormal" style="margin-left: 0.5in;"><span style="font-size: 11pt; color: rgb(31, 73, 125);">FDO<database_name></span></p>
<p class="MsoNormal" style="margin-left: 0.5in;"><span style="font-size: 11pt; color: rgb(31, 73, 125);"> </span></p>
<p class="MsoNormal"><span style="font-size: 11pt; color: rgb(31, 73, 125);">FDO is prepended to the database name to handle a particular use
case which, in hindsight, is not likely very common (I’ll describe the
use case details later). This prefix could therefore be dropped from the feature
schema name. </span></p>
<p class="MsoNormal"><span style="font-size: 11pt; color: rgb(31, 73, 125);"> </span></p>
<p class="MsoNormal"><span style="font-size: 11pt; color: rgb(31, 73, 125);">Exposing tables in the current database in an empty schema
sounds reasonable conceptually. Some users might not necessarily separate each
logical schema into a different MySQL database; a database might simply have a
collection of tables not tied to a particular schema. I have a few
implementation concerns but I’ll wait for the answer to question 3.</span></p>
<p class="MsoNormal"><span style="font-size: 11pt; color: rgb(31, 73, 125);"> </span></p>
<p class="MsoNormal"><span style="font-size: 11pt; color: rgb(31, 73, 125);">Switching to the SQLServerSpatial provider, when the database
has no FDO Metadata, each SQL Server schema is presented as an FDO Feature
Schema. No special handling is done for the dbo schema. I was curious as to why
the dbo schema would be non-portable. It would be an unusual name for a logical
schema but could be copied to a provider, such as SDF, without having to rename
it. </span></p></div></div></blockquote><div>dbo implies the unqualified schema naming and is meaningless out side sql server.. <br><br>ie a database called dbo on mysql or an oracle user called dbo <br><br>challenging problem<br>
</div><blockquote class="gmail_quote" style="border-left: 1px solid rgb(204, 204, 204); margin: 0pt 0pt 0pt 0.8ex; padding-left: 1ex;"><div link="blue" vlink="purple" lang="EN-US"><div>
<p class="MsoNormal"><span style="font-size: 11pt; color: rgb(31, 73, 125);"></span></p>
<p class="MsoNormal"><span style="font-size: 11pt; color: rgb(31, 73, 125);">Getting back to the user case mentioned above, it would be the
case where the schema is copied from a MySQL database without FDO MetaData to a
database with Metadata, where the two databases have the same name but are in
different servers. The FDO-enabled databases have a special feature schema
(with same name as the database) which stores the datastore descriptions. This
schema is not directly modifiable so the copy would fail if the feature schema
being copied is named after the source database. To handle this, the FDO prefix
was added to the schema name. However, as mentioned above, this use case is not
likely very common.</span></p></div></div></blockquote><div>If you are using meta data, maybe turning it around and exposing metadata under FDO, also not very pretty <br></div><blockquote class="gmail_quote" style="border-left: 1px solid rgb(204, 204, 204); margin: 0pt 0pt 0pt 0.8ex; padding-left: 1ex;">
<div link="blue" vlink="purple" lang="EN-US"><div>
<p class="MsoNormal"><span style="font-size: 11pt; color: rgb(31, 73, 125);"> </span></p>
<p class="MsoNormal"><span style="font-size: 11pt; color: rgb(31, 73, 125);">Brent.</span></p>
<p class="MsoNormal"><span style="font-size: 11pt; color: rgb(31, 73, 125);"> </span></p>
<p class="MsoNormal" style="margin-left: 0.5in;"><span style="font-size: 11pt; color: rgb(31, 73, 125);"> </span></p>
<p class="MsoNormal"><span style="font-size: 11pt; color: rgb(31, 73, 125);"> </span></p>
<p class="MsoNormal"><span style="font-size: 11pt; color: rgb(31, 73, 125);"> </span></p>
<p class="MsoNormal"><span style="font-size: 11pt; color: rgb(31, 73, 125);"> </span></p>
<div style="border-style: solid none none; border-color: rgb(181, 196, 223) -moz-use-text-color -moz-use-text-color; border-width: 1pt medium medium; padding: 3pt 0in 0in;">
<p class="MsoNormal"><b><span style="font-size: 10pt;">From:</span></b><span style="font-size: 10pt;">
<a href="mailto:fdo-internals-bounces@lists.osgeo.org" target="_blank">fdo-internals-bounces@lists.osgeo.org</a>
[mailto:<a href="mailto:fdo-internals-bounces@lists.osgeo.org" target="_blank">fdo-internals-bounces@lists.osgeo.org</a>] <b>On Behalf Of </b>Zac Spitzer<br>
<b>Sent:</b> Wednesday, October 28, 2009 10:28 PM<div><div></div><div class="h5"><br>
<b>To:</b> FDO Internals Mail List<br>
<b>Subject:</b> Re: [fdo-internals] RE: [mapguide-internals] FDO RFC 43 -
Standard FDO Class Naming Conventions</div></div></span></p>
</div><div><div></div><div class="h5">
<p class="MsoNormal"> </p>
<p class="MsoNormal" style="margin-bottom: 12pt;">would introducing the concept
of a default schema resolve the issue of multiple <br>
tables having the same name in different schemas? ie GetDefaultSchema()<br>
<br>
Sorry about my confusion about the datastore stuff, my FDO experience <br>
is predominately from working with MapGuide which doesn't expose them.<br>
<br>
Datastores (databases/instances) also are potentially named differently, <br>
where as a schema tends to be more consistant.<br>
<br>
If we introduce datastores into FDO Class names I fear things will become<br>
even more inconsistent. It's easy enough to change the name of a schema,<br>
but renaming a database is a much bigger change.<br>
<br>
As I described in the Proposed Test case:<br>
"Expose the Sheboygan dataset via FDO matching the standard
conventions"<br>
<br>
is all about achieving the goal of making FDO provider agnostic<br>
<br>
SQL server does present a challenge here with it's three levels, but it if it <br>
has schema shouldn't we present them as schema's? well no because then<br>
we will be oft returning dbo which is completely non portable.<br>
<br>
z</p>
<div>
<p class="MsoNormal">On Thu, Oct 29, 2009 at 12:21 PM, Zac Spitzer <<a href="mailto:zac.spitzer@gmail.com" target="_blank">zac.spitzer@gmail.com</a>> wrote:</p>
<p class="MsoNormal">sounds like another RFC ?</p>
<div>
<div>
<p class="MsoNormal" style="margin-bottom: 12pt;"> </p>
<div>
<p class="MsoNormal">On Thu, Oct 29, 2009 at 1:04 AM, Orest Halustchak <<a href="mailto:orest.halustchak@autodesk.com" target="_blank">orest.halustchak@autodesk.com</a>>
wrote:</p>
<div>
<div>
<p class="MsoNormal"><span style="font-size: 11pt; color: rgb(31, 73, 125);">Hi,</span></p>
<p class="MsoNormal"><span style="font-size: 11pt; color: rgb(31, 73, 125);"> </span></p>
<p class="MsoNormal"><span style="font-size: 11pt; color: rgb(31, 73, 125);">I’d also like to add a comment
about something that Haris said in a separate reply.</span></p>
<p class="MsoNormal"><span style="font-size: 11pt; color: rgb(31, 73, 125);"> </span></p>
<p style="margin-left: 0.5in;"><span style="font-family: Wingdings;">Ø</span><span style="font-size: 7pt;"> </span>Perhaps, providers could return
additional info about names of newly created classes.</p>
<p class="MsoNormal"><span style="font-size: 11pt; color: rgb(31, 73, 125);"> </span></p>
<p class="MsoNormal"><span style="font-size: 11pt; color: rgb(31, 73, 125);">I think that’s a good idea, maybe
a way for ApplySchema to return information about anything that was changed
from the user’s input.</span></p>
<p class="MsoNormal"><span style="font-size: 11pt; color: rgb(31, 73, 125);"> </span></p>
<p class="MsoNormal"><span style="font-size: 11pt; color: rgb(31, 73, 125);">Thanks,</span></p>
<p class="MsoNormal"><span style="font-size: 11pt; color: rgb(31, 73, 125);">Orest.</span></p>
<p class="MsoNormal"><span style="font-size: 11pt; color: rgb(31, 73, 125);"> </span></p>
<div>
<div style="border-style: solid none none; border-color: -moz-use-text-color; border-width: 1pt medium medium; padding: 3pt 0in 0in;">
<p class="MsoNormal"><b><span style="font-size: 10pt;">From:</span></b><span style="font-size: 10pt;"> <a href="mailto:fdo-internals-bounces@lists.osgeo.org" target="_blank">fdo-internals-bounces@lists.osgeo.org</a>
[mailto:<a href="mailto:fdo-internals-bounces@lists.osgeo.org" target="_blank">fdo-internals-bounces@lists.osgeo.org</a>]
<b>On Behalf Of </b>Orest Halustchak<br>
<b>Sent:</b> Wednesday, October 28, 2009 9:39 AM</span></p>
<div>
<p class="MsoNormal"><span style="font-size: 10pt;"><br>
<b>To:</b> FDO Internals Mail List</span></p>
</div>
<p class="MsoNormal"><b><span style="font-size: 10pt;">Subject:</span></b><span style="font-size: 10pt;"> RE: [fdo-internals] RE: [mapguide-internals] FDO RFC
43 - Standard FDO Class Naming Conventions</span></p>
</div>
</div>
<div>
<div>
<p class="MsoNormal"> </p>
<p class="MsoNormal"><span style="font-size: 11pt; color: rgb(31, 73, 125);">Hi Zac,</span></p>
<p class="MsoNormal"><span style="font-size: 11pt; color: rgb(31, 73, 125);"> </span></p>
<p class="MsoNormal"><span style="font-size: 11pt; color: rgb(31, 73, 125);">FDO does have a concept of datastore.
There are FDO commands to create, destroy, and list datastores. A datastore is
also what you open with the connection command. It plays a role. My example is
meant to show a case of two separate FDO datastores that for an rdbms are
managed by one rdbms server.</span></p>
<p class="MsoNormal"><span style="font-size: 11pt; color: rgb(31, 73, 125);"> </span></p>
<p class="MsoNormal"><span style="font-size: 11pt; color: rgb(31, 73, 125);">Thanks,</span></p>
<p class="MsoNormal"><span style="font-size: 11pt; color: rgb(31, 73, 125);">Orest.</span></p>
<p class="MsoNormal"><span style="font-size: 11pt; color: rgb(31, 73, 125);"> </span></p>
<div style="border-style: solid none none; border-color: -moz-use-text-color; border-width: 1pt medium medium; padding: 3pt 0in 0in;">
<p class="MsoNormal"><b><span style="font-size: 10pt;">From:</span></b><span style="font-size: 10pt;"> <a href="mailto:fdo-internals-bounces@lists.osgeo.org" target="_blank">fdo-internals-bounces@lists.osgeo.org</a>
[mailto:<a href="mailto:fdo-internals-bounces@lists.osgeo.org" target="_blank">fdo-internals-bounces@lists.osgeo.org</a>]
<b>On Behalf Of </b>Zac Spitzer<br>
<b>Sent:</b> Wednesday, October 28, 2009 9:15 AM<br>
<b>To:</b> FDO Internals Mail List<br>
<b>Subject:</b> Re: [fdo-internals] RE: [mapguide-internals] FDO RFC 43 -
Standard FDO Class Naming Conventions</span></p>
</div>
<p class="MsoNormal"> </p>
<p class="MsoNormal">inline
<br>
<br>
On Wed, Oct 28, 2009 at 11:56 PM, Orest Halustchak <<a href="mailto:orest.halustchak@autodesk.com" target="_blank">orest.halustchak@autodesk.com</a>>
wrote:</p>
<div>
<blockquote style="border-style: none none none solid; border-color: -moz-use-text-color -moz-use-text-color -moz-use-text-color rgb(204, 204, 204); border-width: medium medium medium 1pt; margin: 5pt 0in 5pt 4.8pt; padding: 0in 0in 0in 6pt;">
<p class="MsoNormal">Hi,<br>
<br>
Note that there is another qualifier that should be taken into account in these
discussions and that is the datastore name. There are really three levels of
qualification: datastore name, schema name, class name. So, cases where it is
suggested to use the file name as the schema name, if the file name is already
used for the datastore name, it doesn't have to be used again for the schema
name.</p>
</blockquote>
<div>
<p class="MsoNormal"><br>
My understanding is that FDO has no concept of datastore, it starts with
schema's <br>
<br>
datastore is defined at the FDO connection level, why squeeze three levels into
<br>
a two tier structure?<br>
<br>
</p>
</div>
<blockquote style="border-style: none none none solid; border-color: -moz-use-text-color -moz-use-text-color -moz-use-text-color rgb(204, 204, 204); border-width: medium medium medium 1pt; margin: 5pt 0in 5pt 4.8pt; padding: 0in 0in 0in 6pt;">
<p class="MsoNormal">An
issue with rdbms is that some such as SQL Server include the three levels of
database, schema, and table. Others such as Oracle do not. So in the Oracle
case if we map the datastore name to the Oracle user/schema, then we should not
also use Oracle user/schema for FDO schema.<br>
<br>
Consider this example.<br>
FDO Datastore = CityOfNewYork<br>
FDO Schema = LandBase<br>
Class = Parcel<br>
Class = Road<br>
FDO Schema = Water<br>
Class = Pipe<br>
Class = Valve<br>
FDO Schema = Gas<br>
Class = Pipe<br>
<br>
FDO Datastore = CityOfAlbany<br>
Same schemas and classes<br>
<br>
We don't want to mix up the parcels from CityOfNewYork with the parcles from
CityOfAlbany, those should be in separate tables. Having the Oracle schema name
as LandBase, Water, and Gas doesn't handle this.</p>
</blockquote>
<div>
<p class="MsoNormal" style="margin-bottom: 12pt;"><br>
but that is a problem already solved when you follow the other way other <br>
database access layers work????<br>
<br>
based on the connection details, either by specifying a datastore, or not <br>
Pipe would only be accessible if it was the default for the user or the for <br>
specified datastore. There is a implied concept of the default schema?<br>
<br>
if there's no default and two schemas means there are no schema less tables <br>
to enumerate<br>
<br>
This is how databases normally work in my experience which is all I'm trying<br>
to suggest with this RFC.</p>
</div>
<blockquote style="border-style: none none none solid; border-color: -moz-use-text-color -moz-use-text-color -moz-use-text-color rgb(204, 204, 204); border-width: medium medium medium 1pt; margin: 5pt 0in 5pt 4.8pt; padding: 0in 0in 0in 6pt;">
<p class="MsoNormal">Also,
about the ~ColumnName convention being used for geometry columns, note that FDO
does allow more than one geometry column per class with one flagged as the main
geometry. I wouldn't want to require that these have to be exposed as separate
feature classes.</p>
</blockquote>
<div>
<p class="MsoNormal"><br>
<br>
</p>
</div>
<blockquote style="border-style: none none none solid; border-color: -moz-use-text-color -moz-use-text-color -moz-use-text-color rgb(204, 204, 204); border-width: medium medium medium 1pt; margin: 5pt 0in 5pt 4.8pt; padding: 0in 0in 0in 6pt;">
<p class="MsoNormal"><br>
Thanks,<br>
<span style="color: rgb(136, 136, 136);">Orest.</span></p>
<div>
<div>
<p class="MsoNormal"><br>
-----Original Message-----<br>
From: <a href="mailto:fdo-internals-bounces@lists.osgeo.org" target="_blank">fdo-internals-bounces@lists.osgeo.org</a>
[mailto:<a href="mailto:fdo-internals-bounces@lists.osgeo.org" target="_blank">fdo-internals-bounces@lists.osgeo.org</a>]
On Behalf Of Haris Kurtagic<br>
Sent: Wednesday, October 28, 2009 6:07 AM<br>
To: 'FDO Internals Mail List'<br>
Subject: [fdo-internals] RE: [mapguide-internals] FDO RFC 43 - Standard FDO
Class Naming Conventions<br>
<br>
there is another important case which is not covered in RFC.<br>
Same table name in multiple schemas. Also, how to not mess up when users<br>
logs using different credentials.<br>
<br>
One way to solve that could be to always use rdbms schema name as fdo schema<br>
name.<br>
<br>
I believe it is absolutely necessary that application using FDO to access<br>
rdbms can be sure exactly which table and column it is accessing.<br>
Because what FDO provider sees when connects to rdbms can change regarding<br>
which credentials are used to connect to rdbms. That menas that on same<br>
database it can see only one table, or two tables (same name) in two schemas<br>
or even one or more geometry columns in table.<br>
<br>
I am not keen on current naming in King.Oracle with this ~ sign, but I am<br>
very pleased that when using King.Oracle and FDO class trough it, I know<br>
every time exactly which Oracle schema, table and column I am hitting.<br>
<br>
<br>
<br>
<br>
Just when wanted to finish something else from RFC:<br>
"Class names for databases are normally tablename, unless qualified which<br>
then has ~COLUMN_NAME appended. (if the are multiple geometries, FDO<br>
requires to know which one is the identifier)"<br>
<br>
In King.Oracle ~COLUMN_NAME is appened to make sure resulting name would be<br>
unique. Which actuall oracle column is used is not parsed from name of class<br>
but it is kept inside provider. ~COLUMN_NAME could be anything.<br>
<br>
<br>
Haris<br>
<br>
-----Original Message-----<br>
From: <a href="mailto:mapguide-internals-bounces@lists.osgeo.org" target="_blank">mapguide-internals-bounces@lists.osgeo.org</a><br>
[mailto:<a href="mailto:mapguide-internals-bounces@lists.osgeo.org" target="_blank">mapguide-internals-bounces@lists.osgeo.org</a>] On Behalf Of
Zac Spitzer<br>
Sent: Wednesday, October 28, 2009 9:45 AM<br>
To: FDO Internals Mail List; MapGuide Internals Mail List<br>
Subject: [mapguide-internals] FDO RFC 43 - Standard FDO Class Naming<br>
Conventions<br>
<br>
I have posted RFC 43 for review<br>
<br>
<a href="http://trac.osgeo.org/fdo/wiki/FDORfc43" target="_blank">http://trac.osgeo.org/fdo/wiki/FDORfc43</a><br>
<br>
--<br>
Zac Spitzer -<br>
<a href="http://zacster.blogspot.com" target="_blank">http://zacster.blogspot.com</a><br>
+61 405 847 168<br>
_______________________________________________<br>
mapguide-internals mailing list<br>
<a href="mailto:mapguide-internals@lists.osgeo.org" target="_blank">mapguide-internals@lists.osgeo.org</a><br>
<a href="http://lists.osgeo.org/mailman/listinfo/mapguide-internals" target="_blank">http://lists.osgeo.org/mailman/listinfo/mapguide-internals</a><br>
<br>
_______________________________________________<br>
fdo-internals mailing list<br>
<a href="mailto:fdo-internals@lists.osgeo.org" target="_blank">fdo-internals@lists.osgeo.org</a><br>
<a href="http://lists.osgeo.org/mailman/listinfo/fdo-internals" target="_blank">http://lists.osgeo.org/mailman/listinfo/fdo-internals</a><br>
_______________________________________________<br>
fdo-internals mailing list<br>
<a href="mailto:fdo-internals@lists.osgeo.org" target="_blank">fdo-internals@lists.osgeo.org</a><br>
<a href="http://lists.osgeo.org/mailman/listinfo/fdo-internals" target="_blank">http://lists.osgeo.org/mailman/listinfo/fdo-internals</a></p>
</div>
</div>
</blockquote>
</div>
<p class="MsoNormal"><br>
<br clear="all">
<br>
-- <br>
Zac Spitzer -<br>
<a href="http://zacster.blogspot.com" target="_blank">http://zacster.blogspot.com</a><br>
+61 405 847 168</p>
</div>
</div>
</div>
</div>
<p class="MsoNormal" style="margin-bottom: 12pt;"><br>
_______________________________________________<br>
fdo-internals mailing list<br>
<a href="mailto:fdo-internals@lists.osgeo.org" target="_blank">fdo-internals@lists.osgeo.org</a><br>
<a href="http://lists.osgeo.org/mailman/listinfo/fdo-internals" target="_blank">http://lists.osgeo.org/mailman/listinfo/fdo-internals</a></p>
</div>
<p class="MsoNormal"><br>
<br clear="all">
<br>
-- <br>
Zac Spitzer -<br>
<a href="http://zacster.blogspot.com" target="_blank">http://zacster.blogspot.com</a><br>
+61 405 847 168</p>
</div>
</div>
</div>
<p class="MsoNormal"><br>
<br clear="all">
<br>
-- <br>
Zac Spitzer -<br>
<a href="http://zacster.blogspot.com" target="_blank">http://zacster.blogspot.com</a><br>
+61 405 847 168</p>
</div></div></div>
</div>
<br>_______________________________________________<br>
fdo-internals mailing list<br>
<a href="mailto:fdo-internals@lists.osgeo.org">fdo-internals@lists.osgeo.org</a><br>
<a href="http://lists.osgeo.org/mailman/listinfo/fdo-internals" target="_blank">http://lists.osgeo.org/mailman/listinfo/fdo-internals</a><br>
<br></blockquote></div><br><br clear="all"><br>-- <br>Zac Spitzer -<br><a href="http://zacster.blogspot.com">http://zacster.blogspot.com</a><br>+61 405 847 168<br>