Open georgek146 opened 6 years ago
In short, no you can't read state variables.
On Thu, Mar 29, 2018 at 06:18 George K notifications@github.com wrote:
I'm confused can I only read events or state variables too?
— You are receiving this because you are subscribed to this thread. Reply to this email directly, view it on GitHub https://github.com/xiaoyao1991/presto-ethereum/issues/37, or mute the thread https://github.com/notifications/unsubscribe-auth/AApJ5ekOkbqHPob6eOy06IFxwLj56ayuks5tjMMAgaJpZM4TAKhH .
-- Xiaoyao Qian University of Illinois-Urbana-Champaign MS Computer Science Email: qian13@illinois.edu Tel: (217)-898-7641
Ok. In the other issue you say this is possible. What do you mean by having a having an instrumented ethereum client? What is that?
An instrumented client could be, for example, a modified geth client where you store the EVM traces, decode the traces so that those info can be queried through presto.
Why not just abstract some of the calls to web3?
Also what would it take to be able to create a transaction on ethereum with sql? If we could build that that would be extremely valuable.
@georgek146 "Why not just abstract some of the calls to web3?"
"Also what would it take to be able to create a transaction on ethereum with sql? If we could build that that would be extremely valuable."
The problem that I see many contract developers face is storage organization. I was thinking that we write a contract that basically represents a table. A user could deploy the contract by using an SQL statement, and then be able to execute further state changes through SQL.
I could write the contract, however I would not know how to take a SQL statement and convert that into calling solidity functions.
Creating a new client would be beyond my skill level
I'm confused can I only read events or state variables too?