02-28-2023, 12:50 AM
Are you looking for database joins?
We have some ideas about this down the road.
In our apps, we currently store the recordIDs as foreign keys.
Eg:
Table - Employees with the keys: firstName, lastName, tasks
Table - Tasks
In Employees we have a list of names. Each record may look like this:
firstName: Dan
lastName: Jones
tasks: recordID45, recordID77
In our Tasks tabler we have many records describing potential tasks for employees. RecordID45 and recordID77 are relevant to our example employee.
recordID45: Take out the trash
recordID77: Power the cold fusion system
Thus, our Employee record will have: RecordID45,recordID77 in the tasks key for table Employees.
When we do a read on the employee record, we will do a secondary read on records recordID45 and recordID77 to get the tasks and display this nicely in a form or some other view.
We have some ideas about this down the road.
In our apps, we currently store the recordIDs as foreign keys.
Eg:
Table - Employees with the keys: firstName, lastName, tasks
Table - Tasks
In Employees we have a list of names. Each record may look like this:
firstName: Dan
lastName: Jones
tasks: recordID45, recordID77
In our Tasks tabler we have many records describing potential tasks for employees. RecordID45 and recordID77 are relevant to our example employee.
recordID45: Take out the trash
recordID77: Power the cold fusion system
Thus, our Employee record will have: RecordID45,recordID77 in the tasks key for table Employees.
When we do a read on the employee record, we will do a secondary read on records recordID45 and recordID77 to get the tasks and display this nicely in a form or some other view.