[fdo-users] Is there a Feature class naming convention

[Jason Birch]

I believe that the PostGIS provider only implements the native PostGIS
data access, and has no way of storing FDO-specific logical/physical
mappings (not sure if I have the right terminology here).  I believe
that the second scenario would require the PostGIS provider to implement
some way of persisting this information?

Jason

-----Original Message-----
From: Orest Halustchak
Subject: RE: [fdo-users] Is there a Feature class naming convention

If the provider is accessing an existing schema, e.g. not created by
fdo, then the provider decides how to map the table / file to a class
and schema. The main thing is that the mapping is unique and unambiguous
as Traian said.

The other scenario is if a new class is defined via fdo. In this case,
the caller is specifying an explicit schema name and class name. A
describe of that class then should come back with the same names as long
as the input names were valid (FdoISchemaCapabilities has methods to get
information about valid names such as name size limits and valid
characters).