Solidity: Storing JSON data. Any advantage in using a Struct type vs a String?
I must store JSON formatted data in my Solidity contract. I don't need to do any operations on the data. I simply need to store it, update it, and return it.
Let's say I have JSON formatted data such as:
{'name': 'Nike', 'size':'12', 'color':'blue'}
I'm currently passing the data to the constructor as a string:
constructor(string _data) public {
data = _data;
}
And updating the data by simply replacing the entire string:
function updateData(string _data) public {
data = _data;
}
I'm debating whether I should create a Struct type, named say "Shoe", and pass each property as an argument:
constructor(string _name, uint size, string _color) public {
Shoe memory newShoe = Shoe({
name: _name,
size: _size,
color: _color
})
data = newShoe;
}
I'll never need to store more than one shoe object, and it seems much simpler and easier to pass the data as a String, but I'm wondering if there's an advantage to using a Struct type.
ethereum solidity
asked Nov 16 '18 at 3:43
SteveSteve
159212
add a comment |
I must store JSON formatted data in my Solidity contract. I don't need to do any operations on the data. I simply need to store it, update it, and return it.
Let's say I have JSON formatted data such as:
{'name': 'Nike', 'size':'12', 'color':'blue'}
I'm currently passing the data to the constructor as a string:
constructor(string _data) public {
data = _data;
}
And updating the data by simply replacing the entire string:
function updateData(string _data) public {
data = _data;
}
I'm debating whether I should create a Struct type, named say "Shoe", and pass each property as an argument:
constructor(string _name, uint size, string _color) public {
Shoe memory newShoe = Shoe({
name: _name,
size: _size,
color: _color
})
data = newShoe;
}
I'll never need to store more than one shoe object, and it seems much simpler and easier to pass the data as a String, but I'm wondering if there's an advantage to using a Struct type.
ethereum solidity
asked Nov 16 '18 at 3:43
SteveSteve
159212
add a comment |
I must store JSON formatted data in my Solidity contract. I don't need to do any operations on the data. I simply need to store it, update it, and return it.
Let's say I have JSON formatted data such as:
{'name': 'Nike', 'size':'12', 'color':'blue'}
I'm currently passing the data to the constructor as a string:
constructor(string _data) public {
data = _data;
}
And updating the data by simply replacing the entire string:
function updateData(string _data) public {
data = _data;
}
I'm debating whether I should create a Struct type, named say "Shoe", and pass each property as an argument:
constructor(string _name, uint size, string _color) public {
Shoe memory newShoe = Shoe({
name: _name,
size: _size,
color: _color
})
data = newShoe;
}
I'll never need to store more than one shoe object, and it seems much simpler and easier to pass the data as a String, but I'm wondering if there's an advantage to using a Struct type.
ethereum solidity
asked Nov 16 '18 at 3:43
SteveSteve
159212
I must store JSON formatted data in my Solidity contract. I don't need to do any operations on the data. I simply need to store it, update it, and return it.
Let's say I have JSON formatted data such as:
{'name': 'Nike', 'size':'12', 'color':'blue'}
I'm currently passing the data to the constructor as a string:
constructor(string _data) public {
data = _data;
}
And updating the data by simply replacing the entire string:
function updateData(string _data) public {
data = _data;
}
I'm debating whether I should create a Struct type, named say "Shoe", and pass each property as an argument:
constructor(string _name, uint size, string _color) public {
Shoe memory newShoe = Shoe({
name: _name,
size: _size,
color: _color
})
data = newShoe;
}
I'll never need to store more than one shoe object, and it seems much simpler and easier to pass the data as a String, but I'm wondering if there's an advantage to using a Struct type.
ethereum solidity
ethereum solidity
asked Nov 16 '18 at 3:43
SteveSteve
159212
asked Nov 16 '18 at 3:43
SteveSteve
159212
asked Nov 16 '18 at 3:43
SteveSteve
159212
asked Nov 16 '18 at 3:43
SteveSteve
159212
asked Nov 16 '18 at 3:43
SteveSteve
159212
159212
add a comment |
add a comment |
1 Answer
1
active
oldest
votes
Passing data as a string seems more appropriate since you don't need to manipulate them on the contract. It will be easier and less prone to mistakes and bugs. It will also be cheaper in terms of gas, that is if you are concerned about gas anyway.
answered Nov 16 '18 at 23:02
nikos fotiadisnikos fotiadis
7912515
add a comment |
Your Answer
StackExchange.ifUsing("editor", function () {
StackExchange.using("externalEditor", function () {
StackExchange.using("snippets", function () {
StackExchange.snippets.init();
});
});
}, "code-snippets");
StackExchange.ready(function() {
var channelOptions = {
tags: "".split(" "),
id: "1"
};
initTagRenderer("".split(" "), "".split(" "), channelOptions);
StackExchange.using("externalEditor", function() {
// Have to fire editor after snippets, if snippets enabled
if (StackExchange.settings.snippets.snippetsEnabled) {
StackExchange.using("snippets", function() {
createEditor();
});
}
else {
createEditor();
}
});
function createEditor() {
StackExchange.prepareEditor({
heartbeatType: 'answer',
autoActivateHeartbeat: false,
convertImagesToLinks: true,
noModals: true,
showLowRepImageUploadWarning: true,
reputationToPostImages: 10,
bindNavPrevention: true,
postfix: "",
imageUploader: {
brandingHtml: "Powered by u003ca class="icon-imgur-white" href="https://imgur.com/"u003eu003c/au003e",
contentPolicyHtml: "User contributions licensed under u003ca href="https://creativecommons.org/licenses/by-sa/3.0/"u003ecc by-sa 3.0 with attribution requiredu003c/au003e u003ca href="https://stackoverflow.com/legal/content-policy"u003e(content policy)u003c/au003e",
allowUrls: true
},
onDemand: true,
discardSelector: ".discard-answer"
,immediatelyShowMarkdownHelp:true
});
}
});
Sign up or log in
StackExchange.ready(function () {
StackExchange.helpers.onClickDraftSave('#login-link');
});
Sign up using Google
Sign up using Facebook
Sign up using Email and Password
Post as a guest
Required, but never shown
StackExchange.ready(
function () {
StackExchange.openid.initPostLogin('.new-post-login', 'https%3a%2f%2fstackoverflow.com%2fquestions%2f53331100%2fsolidity-storing-json-data-any-advantage-in-using-a-struct-type-vs-a-string%23new-answer', 'question_page');
}
);
Post as a guest
Required, but never shown
1 Answer
1
active
oldest
votes
1 Answer
1
active
oldest
votes
active
oldest
votes
active
oldest
votes
Passing data as a string seems more appropriate since you don't need to manipulate them on the contract. It will be easier and less prone to mistakes and bugs. It will also be cheaper in terms of gas, that is if you are concerned about gas anyway.
answered Nov 16 '18 at 23:02
nikos fotiadisnikos fotiadis
7912515
add a comment |
Passing data as a string seems more appropriate since you don't need to manipulate them on the contract. It will be easier and less prone to mistakes and bugs. It will also be cheaper in terms of gas, that is if you are concerned about gas anyway.
answered Nov 16 '18 at 23:02
nikos fotiadisnikos fotiadis
7912515
add a comment |
Passing data as a string seems more appropriate since you don't need to manipulate them on the contract. It will be easier and less prone to mistakes and bugs. It will also be cheaper in terms of gas, that is if you are concerned about gas anyway.
answered Nov 16 '18 at 23:02
nikos fotiadisnikos fotiadis
7912515
Passing data as a string seems more appropriate since you don't need to manipulate them on the contract. It will be easier and less prone to mistakes and bugs. It will also be cheaper in terms of gas, that is if you are concerned about gas anyway.
answered Nov 16 '18 at 23:02
nikos fotiadisnikos fotiadis
7912515
answered Nov 16 '18 at 23:02
nikos fotiadisnikos fotiadis
7912515
answered Nov 16 '18 at 23:02
nikos fotiadisnikos fotiadis
7912515
answered Nov 16 '18 at 23:02
nikos fotiadisnikos fotiadis
7912515
7912515
add a comment |
add a comment |
Thanks for contributing an answer to Stack Overflow!
- Please be sure to answer the question. Provide details and share your research!
But avoid …
- Asking for help, clarification, or responding to other answers.
- Making statements based on opinion; back them up with references or personal experience.
To learn more, see our tips on writing great answers.
Sign up or log in
StackExchange.ready(function () {
StackExchange.helpers.onClickDraftSave('#login-link');
});
Sign up using Google
Sign up using Facebook
Sign up using Email and Password
Post as a guest
Required, but never shown
StackExchange.ready(
function () {
StackExchange.openid.initPostLogin('.new-post-login', 'https%3a%2f%2fstackoverflow.com%2fquestions%2f53331100%2fsolidity-storing-json-data-any-advantage-in-using-a-struct-type-vs-a-string%23new-answer', 'question_page');
}
);
Post as a guest
Required, but never shown
Sign up or log in
StackExchange.ready(function () {
StackExchange.helpers.onClickDraftSave('#login-link');
});
Sign up using Google
Sign up using Facebook
Sign up using Email and Password
Post as a guest
Required, but never shown
Sign up or log in
StackExchange.ready(function () {
StackExchange.helpers.onClickDraftSave('#login-link');
});
Sign up using Google
Sign up using Facebook
Sign up using Email and Password
Post as a guest
Required, but never shown
Sign up or log in
StackExchange.ready(function () {
StackExchange.helpers.onClickDraftSave('#login-link');
});
Sign up using Google
Sign up using Facebook
Sign up using Email and Password
Sign up using Google
Sign up using Facebook
Sign up using Email and Password
Post as a guest
Required, but never shown
Required, but never shown
Required, but never shown
Required, but never shown
Required, but never shown
Required, but never shown
Required, but never shown
Required, but never shown
Required, but never shown
