[fdo-dev] using dot '.' in schema element name

[Haris Kurtagic]

Different geometry column could mean something different regarding
specific application.
And we have database schema also, and I think that if we look further
into examples like topology, naming could be more complex.
 
Yes, I understand very well that simply allowing '.' into current naming
procedure would end up with unexpected result.
 
I also know that it is not easy to change it now, but I wanted to
discuss if there are any possibilities. 
 
Thanks,
Haris
 
 
 
 
________________________________

From: Orest Halustchak [mailto:orest.halustchak at autodesk.com] 
Sent: Friday, September 29, 2006 3:25 PM
To: dev at fdo.osgeo.org
Subject: RE: [fdo-dev] using dot '.' in schema element name


Geometry columns would be properties and shouldn't have an impact on the
class name. E.g. if there are geometry columns called G1 and G2 in a
table called Road, the class could be called Road with properties G1,
G2, and others. You would reference these by Road.G1, Road.G2,
Road.Name, etc.
 
The issue with using '.' in a class name is that you can end up with
indeterminate situations. For instance:
    A.B.C.D currently would mean class A referring to Object property B
referring to Object property C referring to property D
 
If we allowed dot in the class name, then does this mean:
   Class A.B.C referring to property D, or
   Class A.B referring to object property C referring to property D, or
   Class A referring to object property B.C referring to property D,
   etc.
 
Thanks,
Orest.

________________________________

From: Haris Kurtagic [mailto:haris at sl-king.com] 
Sent: Friday, September 29, 2006 9:06 AM
To: dev at fdo.osgeo.org
Subject: RE: [fdo-dev] using dot '.' in schema element name


I put "DbSchema" because I mean database schema not fdo schema.
Eventually multiple database schemas can be mapped into one fdo schema.
And in one table there could be multiple geometry columns.
So having table name for fdo class name is not enough.
Basically unique name is database schema + table name + geometry column.
 
So right now I put ~ as delimiter, but it is not as "natural" as . could
be.
 
Haris

________________________________

From: Orest Halustchak [mailto:orest.halustchak at autodesk.com] 
Sent: Friday, September 29, 2006 2:45 PM
To: dev at fdo.osgeo.org
Subject: RE: [fdo-dev] using dot '.' in schema element name


Hi Haris,
 
I'm not sure about your example of DbSchema.TableName.ColumnName. There
is an existing delimeter to separate schema name from class name, which
seems to be the first part of your example. Why would the column name be
part of the class name rather than the column name being a property
name? Are you trying to handle a case where a column is an object type?
 
Thanks,
Orest.

________________________________

From: Haris Kurtagic [mailto:haris at sl-king.com] 
Sent: Friday, September 29, 2006 8:13 AM
To: dev at fdo.osgeo.org
Subject: RE: [fdo-dev] using dot '.' in schema element name


Yes, of course. 
 
I wanted to open discussion if that can be changed or extended, so the
class name could have dot as delimiter.
 
Haris

________________________________

From: Orest Halustchak [mailto:orest.halustchak at autodesk.com] 
Sent: Friday, September 29, 2006 1:56 PM
To: dev at fdo.osgeo.org
Subject: RE: [fdo-dev] using dot '.' in schema element name


Hi Haris,
 
Dot and colon are reserved and cannot be used for scheme element names.
Colon is used as a delimeter between schema name and class name (e.g.
LandBase:Road) and dot is used for accessing object properties (e.g.
Address.StreetNumber) or for associations.
 
Thanks,
Orest.

________________________________

From: Haris Kurtagic [mailto:haris at sl-king.com] 
Sent: Friday, September 29, 2006 7:21 AM
To: dev at fdo.osgeo.org
Subject: [fdo-dev] using dot '.' in schema element name


I am wondering is it possible to allow '.' dot character to be part of
FdoSchemaElement name ?
 
I realized that '.' is hard coded and used as scope delimiter for
fdoidentifer's but
I think it is important to be able to have class name  like:
'DbSchema.TableName.ColumnName'.
 
Right now I am using ~ character but more intuitive would be to use '.'
 
Haris
 
 
 
 
 
-------------- next part --------------
An HTML attachment was scrubbed...
URL: http://lists.osgeo.org/pipermail/fdo-internals/attachments/20060929/d22ddf0d/attachment.html