Hi
There is some functionality which might be useful to the generated peer
classes, but I might need some slight changes to the table/column mapping
classes, so that columns know if they are used as foreign keys in other
tables.
My proposal is for 1:M relations: Basically the idea is that if a table
(call it A) has a column that is used as a foreign key in another table
(call it B) the A data object will have a method that does a query and
return a vector with related B data objects. The other way round B will
have a method that returns it's master A object.
To avoid overhead and the unnecessary loading of objects from database the
query is only done once the method is called. In other words only when A's
getBobjects() method is called the query is actually executed and the B
objects loaded. In fact these methods are merely utility methods that does
queries for that particular table's relations for you...
I haven't given this much though yet, and there might still be issues that
will need to be solved. It might take me some time to get started on this.
Is this feasible at all? Is it worth the trouble? Any other thoughts?
~ Leon
------------------------------------------------------------
To subscribe: [EMAIL PROTECTED]
To unsubscribe: [EMAIL PROTECTED]
Search: <http://www.mail-archive.com/turbine%40list.working-dogs.com/>
Problems?: [EMAIL PROTECTED]
