What I am saying is there is nothing that currently ties the prize.db to a trivial, which as understood , the trivials are in the master recipe table. I am also saying the prize.db was and is intended to be modified by the user to their liking. All that said I would have to either add a field to prize.db for the trivial going forward which would wreck everyone who already has it set up, because it would need to be overwritten.
Or I could get the trivial and sort when I read the unknown list, which would add.. a bit of time, probably palpable time, probably unbearable time. The caveat being if I use array manipulation.
If I do it the SQL way, it should be way faster, or the hope.
Essentially, I need to think about if I want to do this, and if so, what is a painless, expedient way, I also need to think about the ramifications of the order, is it counter-productive to make a rod, wheel, and a window in a specific order , or if it will cause an issue. I know there are instances where an item that is needed is made prior to when it is called for to be learned in the list. However, I would make this an option, I wouldn't make it do it all day every day unless it has user input.
The value proposition isn't there for me, if one recipe is 400 and the other is 450 and I am at 300 for the skill, the chance is a couple of percent difference.