I've successfully tested the in-app billing example, Dungeons, and have
observed an apparent error in its implementation (or in the documentation).
In PurchaseDatabase.java the insertOrder method does not insert multiple
rows in the table as the documentation points out:
> * Inserts a purchased product into the database. There may be multiple
> * rows in the table for the same product if it was purchased multiple
> * or if it was refunded.
I expected the purchase counter to increment every time I made a test
purchase, but because the HISTORY_ORDER_ID_COL is defined as the primary
key, multiple purchases of the same test product will NOT add a row, it
simply updates the current row's information. In order to keep track of
purchases, the primary key should be unique, ideally an auto-incremented