You are viewing a plain text version of this content. The canonical link for it is here.
Posted to notifications@shardingsphere.apache.org by "RaigorJiang (via GitHub)" <gi...@apache.org> on 2023/04/17 03:07:12 UTC

[GitHub] [shardingsphere] RaigorJiang commented on issue #23768: Shradding-jdbc Problem occurs after spring xml is configured

RaigorJiang commented on issue #23768:
URL: https://github.com/apache/shardingsphere/issues/23768#issuecomment-1510627842

   Hi @zhaojinchao95 ,
   When the mode is not configured, it is stored in memory by default, and there is no need to interact with H2, right?
   
   > I have another question. My project uses an internal DataSource of the company. This data source has many extra functions. When serializing and deserializing the data source, I encounter various problems. Why does shardingsphere store the serialized data source into db2? Can I configure not to perform this step? My application scenario is very simple and does not require distributed configuration management.
   > 
   > For example, my DataSource has a getXXX static method that causes deserialization to fail, and another example is that there are some monitoring and other connections in the data source, and serialization and deserialization cause initializing the data source (a very heavy process) to be executed twice.
   
   


-- 
This is an automated message from the Apache Git Service.
To respond to the message, please log on to GitHub and use the
URL above to go to the specific comment.

To unsubscribe, e-mail: notifications-unsubscribe@shardingsphere.apache.org

For queries about this service, please contact Infrastructure at:
users@infra.apache.org