Right now, although it is not used, we have added yields into the schedule table for the farm budget. The reason for that is that we can then have the same operation, but get different yields (as for poplar for example). The other advantage (also not yet used) is that we actually budget things on a per yield basis, and if we then have a yield in the schedule, we can use that in our budgeting.
The problem however, is we are going to end up with a ton of different farms that only differ in the yields on their schedule. If we could separate the yields from the schedule, that wouldn't be the case. The problem with that however is that different budgets can have different operations, and we don't know their yields should be the same. What we need is to somehow assign yields on operations specific method, but this means we'd need to have unique ids for the operations lists, which we really don't have right now.
Right now, although it is not used, we have added yields into the schedule table for the farm budget. The reason for that is that we can then have the same operation, but get different yields (as for poplar for example). The other advantage (also not yet used) is that we actually budget things on a per yield basis, and if we then have a yield in the schedule, we can use that in our budgeting.
The problem however, is we are going to end up with a ton of different farms that only differ in the yields on their schedule. If we could separate the yields from the schedule, that wouldn't be the case. The problem with that however is that different budgets can have different operations, and we don't know their yields should be the same. What we need is to somehow assign yields on operations specific method, but this means we'd need to have unique ids for the operations lists, which we really don't have right now.
@jrmerz any thoughts?