It's a rare effort of masang to improve data relationship database wise.
Basically ti_ItemMixingInfo got rid of all source items and only contains the target item together with all information on the mixing / combining process now. While ti_ItemMixingElement contains the source items. Connected via the "UniqueID", they are forming a one-to-many relationship. Looking at it for a while, it shouldn't be too hard to grasp at.
So you get the target item, then the UniqueID of the combination and can then relate all source items to it. Optimally you'd have an editor for stuff like that and not fiddle with DB data directly, however you can also write a View to display these in the "old fashion".
Joining the two tables on the Id might give you a better visualization of the combinations:
Code:
SELECT info.UniqueID, info.TargetItemNum, info.MixingProbability, info.MixingCost, info.Visible, elem.SourceItemNum, elem.SourceItemCount
FROM ti_ItemMixingInfo info
LEFT JOIN ti_ItemMixingElement elem
ON info.UniqueID = elem.UniqueID
ORDER BY info.UniqueID ASC
Should be easy from there