-
Notifications
You must be signed in to change notification settings - Fork 38
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Empty account_to_state_refs table #85
Comments
Please hold-off from investigating this for a bit; I have one idea that I want to test before I waste your time. |
Can you query the vault specifying the account IDs of the accounts you want to return states for? E.g.
Does it return the expected states? If so, there are no problems. |
Also see these tests in the main Corda repo where this functionality is tested: The tests are run for every build in the Corda repo and don't seem to be failing. |
I created my own flow in your project called
Then I ran it from the shell of the wallet node and I get:
Which leads me to believe this is all working as expected. I.e. the mapping table is working as expected. |
Thanx Roger for looking into this; I never had an issue querying the vault by accounts inside my flows. My only observation is that when I use a SQL editor (e.g. pgAdmin) and I query that table; it's always empty. |
Ah, that's because it's a view created by Liquibase at run-time. Cheers |
Makes sense now. Thanx Roger. |
Corda Open Source 4.3
Tokens 1.1-RC01
Accounts 1.0
Confidential Identities 1.0
I assume that when you assign (e.g. issue, transfer) a state (e.g. FungibleToken) to an account; a new entry should appear in the
account_to_state_refs
table.I noticed that this table is empty in my case, I assign FungibleTokens to accounts; I tested it with H2 and Postgres, locally and on GCP. In all cases, the table was empty.
Roger Willis mentioned that they tested this table and they didn't have any problems with it.
I create a repo (for a different issue), but I was able to recreate the issue in it; so please have a look: https://github.com/adelRestom/tokens-sdk-issue-172
Follow these steps to reproduce:
./gradlew deployNodes
cd build/nodes/
java -jar corda.jar
start MintFixedToken
. This will mint 800.867681.start IssueFixedToken
. This will issue 0.867681 to an Account123 on Wallet node.cd /bin/h2/bin
,sh h2.sh
, the DB port for Wallet node is 10091You will see that the account is created inside
accounts
table, and the token is insidefungible_token
table, but theaccount_to_state_refs
table is empty.The logs didn't show any errors.
The text was updated successfully, but these errors were encountered: