blocks|key|2757290|text|首先，请确保使用的Connector/J版本不早于v5.1.37，其中添加了对JSON数据类型的支持，并且最好不早于版本5.1.40，后者修复了一些与JSON相关的bug。但如果这对你来说是个问题，那它充其量就是次要的。|type|unstyled|depth|inlineStyleRanges|entityRanges|data|2757291|在这之前，JdbcTemplate需要理解您的JSONObject参数。您正在使用的特定方法文档表明变量参数(包括JSONObject+)是|offset|length|style|CODE|2757292|绑定到查询的参数(将其留给PreparedStatement来猜测相应的SQL类型)；还可能包含SqlParameterValue对象，这些对象不仅指示参数值，而且还指示SQL类型和可选比例。|blockquote|2757293|当它说PreparedStatement将猜测时，它只能表示PreparedStatement.setObject()：|2757294|规范指定了从Java类型到SQL的标准映射。在发送到数据库之前，给定的参数将被转换为相应的SQL类型。
请注意，通过使用特定于驱动程序的Java类型，此方法可用于传递特定于数据数据库的抽象数据类型。如果对象属于实现接口SQLData的类，则JDBC驱动程序应该调用方法SQLData.writeSQL将其写入SQL数据流。另一方面，如果对象属于实现Ref、Blob、Clob、NClob、Struct、java.net.URL、RowId、SQLXML或Array的类，则驱动程序应该将其作为相应SQL类型的值传递给数据库。|BOLD|2757295|(强调后加)|2757296|JDBC不支持JSON数据类型。这些文档确实允许Connector/J提供与JSON数据类型对应的驱动程序特定类型，但仅仅因为MySQL和Connector/J支持JSON并不意味着您可以从货架上提取一个随机的JSON--表示对象并呈现给它们，也不意味着它们提供或容纳JSON特定的Java数据类型。由于MySQL似乎没有在其连接器/J开发人员指南中发布或引用任何JDBC的文档，我倾向于怀疑它是否承认任何这类类型。|2757297|因此，您似乎应该使用MySQL的SQL方言直接编程时使用相同的技术：|2757298|在MySQL中，JSON值被写成字符串。MySQL解析需要JSON值的上下文中使用的任何字符串，如果该字符串作为JSON无效，则会产生错误。这些上下文包括在具有JSON数据类型的列中插入一个值，并将一个参数传递给一个期望JSON值的函数。|2757299|(MySQL+5.7参考手册，第11.6节)|2757300|也就是说，将JSONObject转换为JSON格式的String，并以这种方式呈现给模板。在检索方面，预期将不得不做相反的事情。|2757301|entityMap|0|LINK|mutability|MUTABLE|url|https://docs.spring.io/spring/docs/current/javadoc-api/org/springframework/jdbc/core/JdbcTemplate.html#update-java.lang.String-java.lang.Object...-|1|https://docs.oracle.com/javase/8/docs/api/java/sql/PreparedStatement.html#setObject-int-java.lang.Object-|2|https://dev.mysql.com/doc/connectors/en/connector-j-5.1.html|3|https://dev.mysql.com/doc/refman/5.7/en/json.html^0|0|5|C|N|A|1L|A|10|A|0|0|D|H|1C|H|0|3|H|U|T|U|T|1|0|0|1F|1G|5U|0|0|6|0|0|5S|4J|B|2|0|0|Y|0|0|3B|0|0|M|1|K|3|0|0|1S|6|A|Q|6|0^^$0|@$1|2|3|4|5|6|7|1F|8|@]|9|@]|A|$]]|$1|B|3|C|5|6|7|1G|8|@$D|1H|E|1I|F|G]|$D|1J|E|1K|F|G]|$D|1L|E|1M|F|G]]|9|@$D|1N|E|1O|1|1P]]|A|$]]|$1|H|3|I|5|J|7|1Q|8|@$D|1R|E|1S|F|G]|$D|1T|E|1U|F|G]]|9|@]|A|$]]|$1|K|3|L|5|6|7|1V|8|@$D|1W|E|1X|F|G]|$D|1Y|E|1Z|F|G]]|9|@$D|20|E|21|1|22]]|A|$]]|$1|M|3|N|5|J|7|23|8|@$D|24|E|25|F|O]|$D|26|E|27|F|O]]|9|@]|A|$]]|$1|P|3|Q|5|6|7|28|8|@$D|29|E|2A|F|O]]|9|@]|A|$]]|$1|R|3|S|5|6|7|2B|8|@$D|2C|E|2D|F|O]]|9|@$D|2E|E|2F|1|2G]]|A|$]]|$1|T|3|U|5|6|7|2H|8|@$D|2I|E|2J|F|O]]|9|@]|A|$]]|$1|V|3|W|5|J|7|2K|8|@$D|2L|E|2M|F|O]]|9|@]|A|$]]|$1|X|3|Y|5|6|7|2N|8|@$D|2O|E|2P|F|O]]|9|@$D|2Q|E|2R|1|2S]]|A|$]]|$1|Z|3|10|5|6|7|2T|8|@$D|2U|E|2V|F|O]|$D|2W|E|2X|F|G]|$D|2Y|E|2Z|F|G]]|9|@]|A|$]]|$1|11|3|-4|5|6|7|30|8|@]|9|@]|A|$]]]|12|$13|$5|14|15|16|A|$17|18]]|19|$5|14|15|16|A|$17|1A]]|1B|$5|14|15|16|A|$17|1C]]|1D|$5|14|15|16|A|$17|1E]]]]

In the first place, be sure to use a version of Connector/J no older than v5.1.37, where support for the JSON datatype was added, and preferrably no older than v5.1.40, which fixed some JSON-related bugs. But if that's an issue for you, then it is at best secondary.

Before that even matters, <code>JdbcTemplate</code> needs to understand your <code>JSONObject</code> argument. <a href="https://docs.spring.io/spring/docs/current/javadoc-api/org/springframework/jdbc/core/JdbcTemplate.html#update-java.lang.String-java.lang.Object...-" rel="nofollow noreferrer">The particular method you are using</a> documents that the variable arguments, including your <code>JSONObject</code> are

<blockquote>
 arguments to bind to the query (leaving it to the <code>PreparedStatement</code> to
 guess the corresponding SQL type); may also contain <code>SqlParameterValue</code>
 objects which indicate not only the argument value but also the SQL
 type and optionally the scale
</blockquote>

When it says the <code>PreparedStatement</code> will guess, it can only mean <a href="https://docs.oracle.com/javase/8/docs/api/java/sql/PreparedStatement.html#setObject-int-java.lang.Object-" rel="nofollow noreferrer">the two-arg version of <code>PreparedStatement.setObject()</code></a> which documents:

<blockquote>
 The JDBC specification specifies a standard mapping from Java Object
 types to SQL types. The given argument will be converted to the
 corresponding SQL type before being sent to the database.
 
 Note that this method may be used to pass datatabase- specific
 abstract data types, by using a driver-specific Java type. If the
 object is of a class implementing the interface SQLData, the JDBC
 driver should call the method SQLData.writeSQL to write it to the SQL
 data stream. If, on the other hand, the object is of a class
 implementing Ref, Blob, Clob, NClob, Struct, java.net.URL, RowId,
 SQLXML or Array, the driver should pass it to the database as a value
 of the corresponding SQL type.
</blockquote>

(Emphasis added.)

JDBC does not have built-in support for a JSON datatype. The docs do allow for Connector/J to provide a driver-specific type corresponding to the JSON SQL datatype, but just because MySQL and Connector/J support JSON does not mean you can pull a random JSON-representing object off the shelf and present it to them, nor indeed that they provide or accommodate a JSON-specific Java datatype at all. Inasmuch as MySQL seems not to publish or reference any documentation of JDBC extension APIs in its <a href="https://dev.mysql.com/doc/connectors/en/connector-j-5.1.html" rel="nofollow noreferrer">Connector/J developer guide</a>, I'm inclined to doubt that it recognizes any such type.

It seems, then, that you should rely on the same technique that you would do when programming directly in MySQL's SQL dialect:

<blockquote>
 In MySQL, JSON values are written as strings. MySQL parses any string
 used in a context that requires a JSON value, and produces an error if
 it is not valid as JSON. These contexts include inserting a value into
 a column that has the JSON data type and passing an argument to a
 function that expects a JSON value [...].
</blockquote>

(<a href="https://dev.mysql.com/doc/refman/5.7/en/json.html" rel="nofollow noreferrer">MySQL 5.7 Reference Manual, section 11.6</a>)

That is, convert your <code>JSONObject</code> to a JSON-format <code>String</code>, and present it to your template that way. On retrieval, expect to have to do the reverse.

JDBCTemplate and MYSQL JSON

I am writing a rest service where i need to add few details at mysql table.

My mysql table as a column <code>area_json</code> as type json.

I got a pojo object from post call in rest service and i tried to insert it using jdbctemplate like

<pre><code>jdbcTemplate.update("insert into site(area_id,area_json) values(?,?)", area.getareaID(), area.getareaJson());
</code></pre>

Once I do a post call using post man i get the below error

<pre><code>Invalid argument value: java.io.NotSerializableException;
nested exception is java.sql.SQLException: Invalid argument value: java.io.NotSerializableException"
</code></pre>

Please help

java.io.NotSerializableException: org.json.JSONObject

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

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

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

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

文章

问答

视频

学习中心

腾讯云实验室

直播

竞赛

腾讯云代码分析专区

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

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

腾讯云数据库专区

腾讯云顾问专区

腾讯云原生专区

腾讯混元专区

腾讯云TCE专区

腾讯云Lighthouse专区

腾讯云HAI专区

腾讯云Edgeone专区

腾讯云存储专区

腾讯云智能专区

腾讯轻联专区 

腾讯云开发专区

TAPD专区

腾讯轻量云游戏服专区

腾讯云最具价值专家

腾讯云架构师技术同盟

腾讯云创作之星

腾讯云开发者先锋

腾讯云代码助手

云原生构建

TAPD 敏捷项目管理

Cloud Studio

SDK中心

API中心

命令行工具

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

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

JDBCTemplate和MYSQL我正在编写一个rest服务，我需要在mysql表中添加一些细节。我的mysql表作为列area_json作为json类型。我从rest服务中的pojo调用中获得了一个pojo对象，并尝试使用jdbctemplate插入它，如下所示jdbcTemplate.update("insert...

java.io.NotSerializableException: org.json.JSONObject-腾讯云开发者社区-腾讯云

问java.io.NotSerializableException: org.json.JSONObject
EN

社区

活动

圈层

关于

腾讯云开发者

热门产品

热门推荐

更多推荐

问java.io.NotSerializableException: org.json.JSONObjectEN

社区

活动

圈层

关于

腾讯云开发者

热门产品

热门推荐

更多推荐

问java.io.NotSerializableException: org.json.JSONObject
EN