A prop_values view is the cleanest solution. Any chance you can upgrade to
Postgres? :) Failing that, you could probably make a new relationship type
for this "pull values from many different tables depending on a column value
in another table" relationship, but I'm not sure how general-purpose it'd
be.
I wish. I have been pushing for it, but we kind of have about 300,000,000 records in mysql running a small broker-dealer. Changing databases is not exactly an easy one here.
I kind of like the relationship type, since i have a couple of instances of this kind of code
And in the end, your custom relationship would be running exactly the same
database queries that you'll run if you do it "manually" using Manager
queries and/or multiple standard relationships under the covers. If you
want the load(with => ...) magic to work too, just override load(), rummage
through the with => ... arguments, and do whatever you need to to before
passing control on to the base class load().
-John
ahh. yes. simplicity. why the hell didn't i think of that first?!
I really hope i get to publish this project as open once i am done with it. i want to show it off!
