search

xiaoyao1991 / presto-ethereum

Presto Ethereum Connector -- SQL on Ethereum
Apache License 2.0
471 stars 56 forks source link

smart contract variables #28

Open bsollenb54 opened 6 years ago

bsollenb54 commented 6 years ago

Hi Xiaoyao,

I'm a big fan of this work! I'm curious if the transaction table has columns to support querying stated variables from a .sol when it's stamped onto an executed transaction. Is this all stored in the hexadecimal-stored input_value column only and indecipherable? Or is it possible to parse the stated variables into unique columns for querying?

Thanks!

xiaoyao1991 commented 6 years ago

Hi,

Thanks for the interest :) it's definitely possible, but I believe that would require having an instrumented ethereum client. I heard that's what etherscan did.

On the other hand, querying state variables is essentially making eth_call function against a client right? Can you think of a good SQL semantics around this?

On Thu, Jan 4, 2018 at 15:20 bsollenb54 notifications@github.com wrote:

Hi Xiaoyao,

I'm a big fan of this work! I'm curious if the transaction table has columns to support querying stated variables from a .sol when it's stamped onto an executed transaction. Is this all stored in the hexadecimal-stored input_value column only and indecipherable? Or is it possible to parse the stated variables into unique columns for querying?

Thanks!

— 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/28, or mute the thread https://github.com/notifications/unsubscribe-auth/AApJ5VNTw5cdeiXpBnEyG-CAxvegvKXMks5tHOxKgaJpZM4RTJv2 .

-- Xiaoyao Qian University of Illinois-Urbana-Champaign MS Computer Science Email: qian13@illinois.edu Tel: (217)-898-7641