[fdo-internals] RE: [mapguide-internals] FDO RFC 43 - Standard
FDO Class Naming Conventions
zac.spitzer at gmail.com
Wed Nov 4 20:50:50 EST 2009
going to avoid inline comments, as it getting rather long!
Adopting the 'default' schema is good, Default is usually a reserved word
which implies GetSchemas() will then always return at least default
The <schema_name>_<class_name> example can be solved via metadata,
which provides the lattitude required,
the ~column_name stuff, should we just have that as an optional convention
/ approach or drop it from the RFC altogether?
perhaps the schema -= database or user problem could be solved at the
connection definition level where the user can decide what to expose
approach to take?
Solution Architect / Director
Ennoble Consultancy Australia
+61 405 847 168
More information about the fdo-internals