Issue 71 in ardb: Cannot isolate cards that appear *only* in a single set.

1 view
Skip to first unread message

codesite...@google.com

unread,
May 19, 2010, 10:35:40 PM5/19/10
to ardb-...@googlegroups.com
Status: New
Owner: ----

New issue 71 by agupta.cs: Cannot isolate cards that appear *only* in a
single set.
http://code.google.com/p/ardb/issues/detail?id=71

What steps will reproduce the problem?
1. "Select" all library cards from set "Lords of Night", which also
includes reprints from other sets. (Correct)
2. "Remove" all library cards from sets not in "Lords of Night".
3. Removes no cards.

What is the expected output? What do you see instead?
I would want to see the list of 150 newly introduced cards in only that
set. I instead see cards from that set that have also been printed
elsewhere.

Another way to produce a similar error is to try to remove "Jyhad" cards
from a full database. Only one cards will be removed, but when "Jyhad"
cards are selected instead, we see 326 cards in the set.

What version of the product are you using? On what operating system?
Latest version, 3.1.1. Windows XP.

Please provide any additional information below.


--
You received this message because you are subscribed to the Google Groups "ardb-devel" group.
To post to this group, send email to ardb-...@googlegroups.com.
To unsubscribe from this group, send email to ardb-devel+...@googlegroups.com.
For more options, visit this group at http://groups.google.com/group/ardb-devel?hl=en.

codesite...@google.com

unread,
May 20, 2010, 4:36:27 PM5/20/10
to ardb-...@googlegroups.com
Updates:
Status: Accepted

Comment #1 on issue 71 by graham.r.smith: Cannot isolate cards that appear
This is a known issue. We hope to fix it at some point but it may take
some reworking
of the database todo.

codesite...@google.com

unread,
May 20, 2010, 5:02:23 PM5/20/10
to ardb-...@googlegroups.com
Updates:
Labels: Priority-Medium

Comment #2 on issue 71 by graham.r.smith: Cannot isolate cards that appear
(No comment was entered for this change.)

codesite...@google.com

unread,
May 20, 2010, 5:06:33 PM5/20/10
to ardb-...@googlegroups.com

Comment #3 on issue 71 by graham.r.smith: Cannot isolate cards that appear
I will add debug log tracing to all the SQL generation so I can see what
SQL queries
are being used.

codesite...@google.com

unread,
Feb 2, 2011, 4:36:45 PM2/2/11
to ardb-...@googlegroups.com

Comment #4 on issue 71 by agupta...@gmail.com: Cannot isolate cards that

Has there been any progress on this issue?

codesite...@google.com

unread,
Feb 3, 2011, 1:33:52 AM2/3/11
to ardb-...@googlegroups.com
Updates:
Status: Started

Comment #5 on issue 71 by Woodruffr1973: Cannot isolate cards that appear

Yes I have written a query that filters out one set and included a check
box called 'no duplicate' so when you select a set (Black Hand) for
example it only shows cards that appeared for the first time in black hand,
and no duplicate cards from other sets appear. However Im still trying to
get this added query to work properly within the default query/search.

SELECT cards_names.card_name
FROM cards_library,cards_sets,cards_names
WHERE cards_library.card_name=cards_names.record_num
AND cards_library.release_set=cards_sets.record_num
AND NOT cards_sets.full_name LIKE 'Proxy%'
GROUP BY cards_names.card_name
HAVING cards_sets.full_name = '%s' "
ORDER BY cards_names.card_name

This query I have tested and it works fine.
However getting it to intergrate with the built in default query has turned
difficult. Seems to be returning a NULL set result in the default query.

FYI I use sqlitebrowser to test queries directly to the database so I can
tell what results I am getting back. A very useful tool.

The completed working function should be done soon as I get the query to
output correctly with the default.


codesite...@google.com

unread,
Feb 3, 2011, 2:11:43 AM2/3/11
to ardb-...@googlegroups.com

Comment #6 on issue 71 by Woodruffr1973: Cannot isolate cards that appear

As an additional notice, the way the listed search in the original bug is
actually functioning as written. Because of how the database identifies a
card id.
Im actually adding this as a feature because I see it as useful for people
deck building (I would find it useful myself). In the database, it does
not identify the card name with any other set because you removed the card
id with the other sets with the initial search.
I have written a more advanced query (above) so it functions more the way
the user intends.
And the 'No Duplicates' Box seems logical. So you can simply search for
Black Hand No Duplicates and get the desired effect. Which are card that
were originally printed in Black Hand.

Reply all
Reply to author
Forward
0 new messages