Currently a link refers to a single row of a db. It would be very valuable if a link would specify a
key-field of the referred db. Under this aspect the reference of multiple rows would be possible.
Calculated fields should be able to act upon data of the joined subset of the referred db.
Logged In: YES
user_id=334809
Yikes! This is many, many steps away from being possible.
- First, we need a more advanced filtering method (I'm
looking into this now)
- Then we need the types of links you describe (based on a
key field and value)
- Next, we need scripts that operate on a set of data, as
opposed to individual records (possible, but may have
significant constraints under the current implementation)
- Finally we need scripts operations that can gather data
from other databases.
The first two steps are definitely possible.
The third is potentially very complicated, and may run into
memory issues, or an explosion in the number of script
operators. I need to think more about it.
The last step may also have memory implications, and is
significantly more difficult that operating on linked fields
as they currently exist.
Logged In: YES
user_id=136200
I want it too. And script that run over all fields in the
another table with given value in the choosen column. So,
only sum, min, max and average of values in selected column
child table will be verry useful.