frsty13 {"ops":[{"insert":"It'd be great if we could only see a single entry of a card, no matter which printings we own. The only time I really care about which printings I have is if I'm trying to sell, but when it comes to deck construction or knowing how many of a card I own, the printings almost always irrelevant. I can see a world where this is a toggle, a dropdown, or a number of other ways to swap between a \"consolidated view\" and \"detailed view\"\n"}]}
0
{"ops":[{"insert":"We already show that number in the collection records tab of any cards details. But soing it as it's own view (multiple cards at once) would be an extremely slow operation. Slow enough, where it's not worth doing. \n"}]}
Edited 6/1/2026, 9:42:37 PM
0
{"ops":[{"insert":"... as it's own view (multiple cards at once) would be an extremely slow operation ..."},{"attributes":{"blockquote":true},"insert":"\n"},{"insert":"Hear me out... What if it doesn't"},{"attributes":{"italic":true},"insert":" "},{"attributes":{"italic":true,"bold":true},"insert":"have "},{"insert":"to perform an operation like that to achieve this?\n\nPossible solution:\nAdd a database table to store card totals and make a couple more INSERT and UPDATE statements to it upon collection record edits and entries.\n\nExample:\nUID, Name (or UID for card if exists),\t\tScryfall ID (or other UID for printings),\t\t\t\t\tFoil,\t\tTotal\n1\t\t\tAnnul,\t\t\t\t\t\t\t\t\t\t\t\t\t\t\t\tnull (use nulls for overall total),\t\t\t\t\t\t\t\t\tnull,\t\t4\n2\t\t\tAnnul, \t\t\t\t\t\t\t\t\t\t\t\t\t\t\t26dd02c4-569b-437f-b9dd-bd2f1d86a968, \tfalse, \t2\n3\t\t\tAnnul, \t\t\t\t\t\t\t\t\t\t\t\t\t\t\t26dd02c4-569b-437f-b9dd-bd2f1d86a968, \ttrue, \t1\n4\t\t\tAnnul, \t\t\t\t\t\t\t\t\t\t\t\t\t\t\t8ba18ec8-e82f-41be-9ed8-b1a4ae9b7426, \tfalse, \t1\n\nThen you could re-run a new query using this table instead to provide a unique card view or a unique printing view.\n\nJust a thought I had. Feel free to take it or leave it. \n\n"}]}
0