entityMap|0|type|LINK|mutability|MUTABLE|data|url|http://www.mysqltutorial.org/mysql-json/|blocks|key|foher|text|可以，您可以将JSON保存到mysql数据库中。Mysql增加了5.7版本以上的JSON数据类型。|unstyled|depth|inlineStyleRanges|entityRanges|8fnmg|请参考http://www.mysqltutorial.org/mysql-json/|offset|length|45mog^0|0|3|14|0|0^^$0|$1|$2|3|4|5|6|$7|8]]]|9|@$A|B|C|D|2|E|F|N|G|@]|H|@]|6|$]]|$A|I|C|J|2|E|F|O|G|@]|H|@$K|P|L|Q|A|R]]|6|$]]|$A|M|C|-4|2|E|F|S|G|@]|H|@]|6|$]]]]

Yes you can save JSON to mysql database. Mysql added the JSON datatype above 5.7 version.

Please refer <a href="http://www.mysqltutorial.org/mysql-json/" rel="nofollow noreferrer">http://www.mysqltutorial.org/mysql-json/</a>

entityMap|blocks|key|eb864|text|可以，您可以将JSON响应保存在表本身中。|type|unstyled|depth|inlineStyleRanges|entityRanges|data|5gfac|但它将是简单的字符串格式，并且需要在代码级对JSON字符串进行解析。|49est|您可以使用CLOB来实现相同的目的。|bhpbt^0|0|0|0^^$0|$]|1|@$2|3|4|5|6|7|8|H|9|@]|A|@]|B|$]]|$2|C|4|D|6|7|8|I|9|@]|A|@]|B|$]]|$2|E|4|F|6|7|8|J|9|@]|A|@]|B|$]]|$2|G|4|-4|6|7|8|K|9|@]|A|@]|B|$]]]]

Yes, you can save JSON response inside the table itself.

But It will be in simple string format and parsing of JSON string required to be done at code level. 

You can use CLOB for the same.

entityMap|blocks|key|25nig|text|它只是一个BLOB，没有什么固有的错误，它是一个受支持的数据类型。|type|unstyled|depth|inlineStyleRanges|entityRanges|data|1hsbo|但是，我强烈建议您将JSON保存到一个文件中，并保留一个路径列表。很简单，因为它会更快。|deoqe^0|0|0^^$0|$]|1|@$2|3|4|5|6|7|8|F|9|@]|A|@]|B|$]]|$2|C|4|D|6|7|8|G|9|@]|A|@]|B|$]]|$2|E|4|-4|6|7|8|H|9|@]|A|@]|B|$]]]]

It would just be a BLOB and theres nothing inheriently wrong with that, its a supported datatype.

However, i would urge you to save the JSON to a file and keep a list of paths instead. simply because it will be quicker.

entityMap|0|type|LINK|mutability|MUTABLE|data|url|https://dev.mysql.com/doc/refman/5.7/en/json.html|blocks|key|41vgr|text|是的，这是可能的。从5.7版本开始，MySQL就实现了JSON数据类型。|unstyled|depth|inlineStyleRanges|entityRanges|dt9s7|如果您询问有关如何操作此数据类型的技术细节，请参阅excellent+shortcut。|offset|length|je52|仅举几个例子：|adiu1|创建：|d6gbo|mysql>+CREATE+TABLE+facts+(sentence+JSON);|code-block|syntax|javascript|7kae0|插入：|d1m7|mysql>+INSERT+INTO+facts+VALUES
+++++>+++('{"mascot":+"Our+mascot+is+a+dolphin+named+\\"Sakila\\"."}');|a4gke|阅读：|ctvgh|mysql>+SELECT+sentence->"$.mascot"+FROM+facts;|cbe9r|但我敢打赌，一个真正的问题是，在数据库中存储JSON有多明智。|6arah|所以一般的答案是：|3omqh|if+developers+of+particular+RDBMS+included+such+aproach+in+their+implementation,+it+is+intended+and+desired+for+use.|style|CODE|17f8|因此，只要将数据格式化为JSON是一个好主意，那么将该数据存储在RDBMS的JSON列中也是一个好主意。我没有这个实现的经验(我更喜欢Postgresql而不是MySQL)，但是我在需要的时候就开始使用JSON数据类型了，但我仍然不认为这是一个糟糕的决定。|celot|特别是，当您考虑将JSON格式的数据存储在文件中并仅挂钩数据库中的路径时，使用JSON类型应该是一个好主意。在文件中存储JSON格式的数据几乎总是比插入和查询JSON慢，特别是当您只需要访问特定的键值对时(您可以在普通的selects中只查询特定的键)。|8mmmd|但是，如果您的数据根本没有集成到以JSON格式存储，那么使用JSON数据类型也不是一个好主意。JSON不喜欢哪种数据？基本上，当number-of-keys+:TO:+overall-size比率非常小时，所有类型的非结构化流。举个例子，字典有一个键，值存储了500个kByte的长字符串：|8fl4k|{"file":+"a+very+very+very+...+long+string,+perhaps+just+encoded+file"}|bb3kk|在这种情况下-是的，一个更好的方法是将其存储为常规文件。|av32r|因此，与往常一样，这一切都取决于特定的用例:)|17f1i^0|0|P|I|0|0|0|0|0|0|0|0|0|0|0|0|38|0|0|0|1S|W|0|0|0|0^^$0|$1|$2|3|4|5|6|$7|8]]]|9|@$A|B|C|D|2|E|F|1O|G|@]|H|@]|6|$]]|$A|I|C|J|2|E|F|1P|G|@]|H|@$K|1Q|L|1R|A|1S]]|6|$]]|$A|M|C|N|2|E|F|1T|G|@]|H|@]|6|$]]|$A|O|C|P|2|E|F|1U|G|@]|H|@]|6|$]]|$A|Q|C|R|2|S|F|1V|G|@]|H|@]|6|$T|U]]|$A|V|C|W|2|E|F|1W|G|@]|H|@]|6|$]]|$A|X|C|Y|2|S|F|1X|G|@]|H|@]|6|$T|U]]|$A|Z|C|10|2|E|F|1Y|G|@]|H|@]|6|$]]|$A|11|C|12|2|S|F|1Z|G|@]|H|@]|6|$T|U]]|$A|13|C|14|2|E|F|20|G|@]|H|@]|6|$]]|$A|15|C|16|2|E|F|21|G|@]|H|@]|6|$]]|$A|17|C|18|2|E|F|22|G|@$K|23|L|24|19|1A]]|H|@]|6|$]]|$A|1B|C|1C|2|E|F|25|G|@]|H|@]|6|$]]|$A|1D|C|1E|2|E|F|26|G|@]|H|@]|6|$]]|$A|1F|C|1G|2|E|F|27|G|@$K|28|L|29|19|1A]]|H|@]|6|$]]|$A|1H|C|1I|2|S|F|2A|G|@]|H|@]|6|$T|U]]|$A|1J|C|1K|2|E|F|2B|G|@]|H|@]|6|$]]|$A|1L|C|1M|2|E|F|2C|G|@]|H|@]|6|$]]|$A|1N|C|-4|2|E|F|2D|G|@]|H|@]|6|$]]]]

Yes, this is possible. MySQL implements JSON datatype since 5.7 version.

If You are asking about technical details about how to operate with this datatype, here is <a href="https://dev.mysql.com/doc/refman/5.7/en/json.html" rel="nofollow noreferrer">excellent shortcut</a>.

Just quoting few examples:

CREATING:

<pre><code>mysql&gt; CREATE TABLE facts (sentence JSON);
</code></pre>

INSERTING:

<pre><code>mysql&gt; INSERT INTO facts VALUES
 &gt; ('{"mascot": "Our mascot is a dolphin named \\"Sakila\\"."}');
</code></pre>

READING:

<pre><code>mysql&gt; SELECT sentence-&gt;"$.mascot" FROM facts;
</code></pre>

But I bet that a real question is about how wise it is to store a JSON in database.

So the general answer is: 

<code>if developers of particular RDBMS included such aproach in their implementation, it is intended and desired for use.</code>

So, as long as it is good idea to format your data as a JSON at all, it should be also a good idea to store this data in JSON column in RDBMS. I do not have an experience in that particular implementation (prefer Postgresql rather than MySQL), but I had started using JSON datatype as soon as I've needed it and still I do not consider it as a bad decision or something.

Epecially, when you consider storing JSON formated data inside a file and hooking just paths inside database, using a JSON type instead should be a good idea. Almost always storing JSON formated data in files WILL be slower than inserting and querying JSON, Especially, when You need access only to a particular key-value pairs (you can query just a particular keys in ordinary selects). 

HOWEVER, when Your data is not inteded to be stored as a JSON format AT ALL, it will be a bad idea to use a JSON datatype also. What kind of data does JSON not like? Basically, all sorts of unstructured streams, when a <code>number-of-keys :TO: overall-size</code> ratio is very small. An example would be a dictionary with one key, and value storing 500 kByte long string:

<pre><code>{"file": "a very very very ... long string, perhaps just encoded file"}
</code></pre>

In such case - yes, a better aproach is to store it as a regular files.

So as always, it all depends on a particular use case :)

Here's the deal, I currently have an application that uses a third party API whose endpoints return JSON. Currently when a component on the front-end is mounted, I execute a function which makes a GET request to my own back-end and in return my back-end makes a GET request to the third party API, then the response from the API is returned as JSON to the front-end. 

Now this is all fine and dandy, however, I have a limited amount of allowed requests to that API so I want to make sure to save the response to my database so that when a future requests are made, my back-end would return whats in my database instead of making a whole new GET request.

Now the thing is I'm not sure if storing JSON is wise or possible and this is why I decided to consult you fellas first since you're very helpful. Under what data type should the JSON be saved and would there be any drawbacks to what I'm doing?

Can I store JSON in a MySQL database table field? Is it a good idea in my case? And if so, how?

翻译质量差，导致语言生硬或混乱。

没有提供实际的解决方法或示例。

解答不清晰，无法理解或解决问题。

页面排版不美观，阅读体验差。

文章

问答

视频

学习中心

腾讯云实验室

直播

竞赛

腾讯云代码分析专区

腾讯iOA零信任安全管理系统专区

腾讯云架构师技术同盟交流圈

腾讯云数据库专区

腾讯云顾问专区

腾讯云原生专区

腾讯混元专区

腾讯云TCE专区

腾讯云Lighthouse专区

腾讯云HAI专区

腾讯云Edgeone专区

腾讯云存储专区

腾讯云智能专区

腾讯轻联专区 

腾讯云开发专区

TAPD专区

腾讯轻量云游戏服专区

腾讯云最具价值专家

腾讯云架构师技术同盟

腾讯云创作之星

腾讯云开发者先锋

腾讯云代码助手

云原生构建

TAPD 敏捷项目管理

Cloud Studio

SDK中心

API中心

命令行工具

涵盖代码开发、场景应用、自动测试全流程，助你从零构建专属AI助手

一站式MCP教程库，解锁AI应用新玩法

 事情是这样的，我目前有一个应用程序，它使用第三方API，它的端点返回JSON。目前，当在前端挂载组件时，我执行一个函数，该函数向我自己的后端发出GET请求，作为回报，我的后端向第三方API发出GET请求，然后来自API的响应以JSON的形式返回给前端。 现在这一切都很好，但是，我对该API的允许请求数量是有限的，所以我希望确保将响应保存到我的数据库中，这样当将来发出请求时，我的后端将返回数据库中

问是否可以将JSON存储在MySQL数据库表字段中？这对我来说是个好主意吗？如果是这样的话，是如何做到的呢？
EN

回答 4

Stack Overflow用户

Stack Overflow用户

Stack Overflow用户

社区

活动

圈层

关于

腾讯云开发者

热门产品

热门推荐

更多推荐

问是否可以将JSON存储在MySQL数据库表字段中？这对我来说是个好主意吗？如果是这样的话，是如何做到的呢？EN

回答 4

Stack Overflow用户

Stack Overflow用户

Stack Overflow用户

社区

活动

圈层

关于

腾讯云开发者

热门产品

热门推荐

更多推荐

问是否可以将JSON存储在MySQL数据库表字段中？这对我来说是个好主意吗？如果是这样的话，是如何做到的呢？
EN