I'm looking for an O-R layer for the next version of our system;
somebody recommended that I evaluate Peers. I've identified 7
structural cases and a few other criteria that I'd like in an O-R tool.
Can an experienced Peers user or developer tell me how well it handles
these situations?
O-R structures:
1) simple (1 class, 1 table)
2) 1:n
3) n:m
4) self join 1:n (object trees)
5) self join n:m (object maps)
6) simple inheritance (S extends B, each maps to a table with a shared
primary key)
7) polymorphic inheritance (S and T extend B, the application works with
a collection of B)
The only other real requirement I've got is good documentation.
Thanks for your time,
J. Pulley
---------------------------------------------------------------------
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]
