Q2K3 commented on issue #30754: URL: https://github.com/apache/shardingsphere/issues/30754#issuecomment-2034078138
> * Isn't this just a common name change? The memory mode is almost equivalent to the h2database storage in the standalone mode, and both use h2database to operate metadata. However, the standalone mode is designed to store metadata in relational databases other than h2database, such as MySQL and TiDB. > * If you don't understand, you can note [Update H2DataBase to 2.x and drop support for H2Database 1.x #19964](https://github.com/apache/shardingsphere/pull/19964) . As early as the 5.1.x milestone, the memory mode refers to using h2database to store metadata. > * If you expect to submit a PR for an old version of the document, this is impossible because the old versions of the document have been sealed as git tags and svn tags and submitted to the ASF side, and no further changes are allowed. Thks for so fast reply. I get your point that memory mode in the older version is actually a specific state of standalone mode with h2 db, so in the newer version it has been removed. In my situation, I'm using shardingshpere-jdbc-core-spring-boot-starter(V5.2.1) in my springboot project, I follow the official examples which I metioned above to combine data sharding features into my project. And I found those examples In V5.2.0/V5.2.1 still use memory mode in there configuration files. Then exception I metioned above occured. Then I started searching infomation about memory mode, there has no obivious log infomation about memory mode removing in offcial release log and document. At last, I found some discussion in the issues, then I got memory mode were removed and never used in higher version. I decide to suggest about clearly writing out that memory mode was replaced by standalone mode in normal and direct place like offcial release log or document, not just in issues list. That's all why I submit this issue. BYW, I know that code after tagging cannot be changed again, but official examples with obivious errors (like examples in V5.2.0/V5.2.1 still using memory mode) are very confusing. Maybe there can be some way to resolve this situation -- 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: [email protected] For queries about this service, please contact Infrastructure at: [email protected]
