Only time you would even need to worry about doing JOIN for those tables is if you were going to show information that is from both tables. I can't see why you would need to show that information. If they are in the UI looking to place a bet, you simply
have a label control that shows their available balance. Then below, you display their bets in a gridview. Two separate data sources displaying information, no joins needed. If they were to place a bet with a negative balance, your programs logic should throw
an error and not let them proceed with betting until they purchase credits. Make sense?
bbcompent1
All-Star
32978 Points
8502 Posts
Moderator
Re: deposit/withdraw
Apr 25, 2011 01:29 PM|LINK
Only time you would even need to worry about doing JOIN for those tables is if you were going to show information that is from both tables. I can't see why you would need to show that information. If they are in the UI looking to place a bet, you simply have a label control that shows their available balance. Then below, you display their bets in a gridview. Two separate data sources displaying information, no joins needed. If they were to place a bet with a negative balance, your programs logic should throw an error and not let them proceed with betting until they purchase credits. Make sense?