Skip to content
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

Can I read state variables or not? #37

Open
georgek146 opened this issue Mar 29, 2018 · 9 comments
Open

Can I read state variables or not? #37

georgek146 opened this issue Mar 29, 2018 · 9 comments

Comments

@georgek146
Copy link

I'm confused can I only read events or state variables too?

@xiaoyao1991
Copy link
Owner

xiaoyao1991 commented Mar 29, 2018 via email

@georgek146
Copy link
Author

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?

@xiaoyao1991
Copy link
Owner

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.

@georgek146
Copy link
Author

Why not just abstract some of the calls to web3?

@georgek146
Copy link
Author

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.

@xiaoyao1991
Copy link
Owner

@georgek146
"Why not just abstract some of the calls to web3?"

  • It can be done, but I wonder how useful it is. Essentially it only allows you to select right? No aggregation can be done.

"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."

  • Very interesting thought. I have actually thought about this too. Create a SQL-based ethereum client. Inserting record could be sending tx or mining blocks :) Just didn't have the time to dig into the "write" part of presto yet. Would you like to take lead on that?

@georgek146
Copy link
Author

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.

@georgek146
Copy link
Author

I could write the contract, however I would not know how to take a SQL statement and convert that into calling solidity functions.

@georgek146
Copy link
Author

Creating a new client would be beyond my skill level

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

2 participants