Search Results

}; So if you want to access the count for a particular scope, then you are doing it the correct way by saying result.rows[0].count, which will give you the number of rows in the first scope of the table … as expected using something like cleos get table …

I would say that this is then unreliable, because if the scope of the table is, say, 7, you can't then see the number 7 as that can't be included in an valid eosio::name. … count always seems to return double the value of the actual rows Because your table has secondary indices. If you have more than just the primary index, then the row count is doubled. …

If I understand correctly, and your code is implemented correctly, this can only happen in the case of a fork in the chain. Correctly implemented code would look something like this: auto itr = getT …

So I have been in discussion with Todd Fleming from B1, and he said that this is currently not possible. The solution is to include the other classes as members within the concrete class: class A { …

As a general rule there are 3 ways to use the scope: Globally - all table entries are kept in one scope (usually with the name of the contract) cleos get table censuscensus global population Groups … access) cleos get table censuscensus phillhamnett population Seeing all table rows To see all table rows, just add -l -1 (minus el, minus one) somewhere after get table. …

The scope can be used to narrow down a table list to contain only some fraction of the total entries available. …

Macros should work, but you'd have to edit the eosiocpp script in order to be able to use them when you compile the code. You can't just do eosiocpp -DGEN_TABLE like in normal c++.

Yes, this should be possible due to implicit conversion. It is safe to do this going from low precision to high precision, i.e. from 8-bit to 64-bit. However, doing it in the other direction may cau …