From: Alex B. <en...@tu...> - 2001-08-20 19:33:34
|
>> I don't see why not. I don't _think_ entityManager supprts that currently >> but I have no problem with the idea as long as its implemented properly :) >> > > It does support that; you have to specify the joins in a hierarchical array > structure in the entity definition (that syntax could use some rethinking > before we release as it was imported from an earlier abstraction layer). I can > supply an example entity definition if there is interest. That would be great. >> Actually, along these lines: does anyone have any qualms about making this >> assumption?: >> >> -Entity Field names must correspond exactly to table field names (we >> could get rid of the schema map if we did this) >> > > The schema structure is optional; if it's not present, we use the object > structure, which is single-dimensional, instead. Odysseas or John C. will > probably have better rationale for this than I do, but at least one example of > where the schema mapping comes in useful is in building a generic public data > access structure which could be used to automatically generate, for example, > dtd's for XML access to these objects. Having a degree of independance between > your data access structure's element names and your database field names could > prove useful for cases like this. Agreed. _a |