You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Copy file name to clipboardExpand all lines: archive/en/about-mariadb-connector-j/+comments/feed/index.html
+1-1
Original file line number
Diff line number
Diff line change
@@ -1,5 +1,5 @@
1
1
<?xml version="1.0" encoding="utf-8"?>
2
-
<rssxmlns:atom="http://www.w3.org/2005/Atom" version="2.0"><channel><title>MariaDB Knowledge Base Comments for: About MariaDB Connector/J</title><link>https://mariadb.com/kb/en/about-mariadb-connector-j/+comments/feed/</link><description></description><atom:linkhref="https://mariadb.com/kb/en/about-mariadb-connector-j/+comments/feed/" rel="self"></atom:link><language>en-us</language><lastBuildDate>Mon, 03 Mar 2025 07:12:49 +0000</lastBuildDate><item><title>MariaDB Connector/J Compatiblity</title><link>https://mariadb.com/kb/en/about-mariadb-connector-j/+comments/4919</link><description><p>Hi, I am using version of [ mariadb-java-client-1.4.6.jar ]</p>
2
+
<rssxmlns:atom="http://www.w3.org/2005/Atom" version="2.0"><channel><title>MariaDB Knowledge Base Comments for: About MariaDB Connector/J</title><link>https://mariadb.com/kb/en/about-mariadb-connector-j/+comments/feed/</link><description></description><atom:linkhref="https://mariadb.com/kb/en/about-mariadb-connector-j/+comments/feed/" rel="self"></atom:link><language>en-us</language><lastBuildDate>Tue, 04 Mar 2025 01:02:35 +0000</lastBuildDate><item><title>MariaDB Connector/J Compatiblity</title><link>https://mariadb.com/kb/en/about-mariadb-connector-j/+comments/4919</link><description><p>Hi, I am using version of [ mariadb-java-client-1.4.6.jar ]</p>
3
3
<p>And I wonder if this maria connector is compatible to which version of
* **Description:** When useServerPrepStmts is enabled, any positive value indicates that a prepared statement cache of the specified size will be used. If the value is less than or equal to zero, the cache will not be enabled. Before 3.0, an option cachePrepStmts was indicatin if cache has to be enable
1038
+
* **Data Type:** ##integer##
1039
+
* **Default Value:** ##250##
1040
+
* **Introduced:** 1.3.0
1041
+
1035
1042
----
1036
1043
==== ##transactionReplay##
1037
1044
* **Description:** Enables transaction caching. If a failover occurs before a transaction is committed or rolled back, the transaction's cached statements are re-executed on the new primary server. Connector/J requires that applications only use idempotent queries. If the number of statements in the transaction cache exceeds transactionReplaySize, caching will be disabled until the transaction is committed or rolled back.
| ##assureReadOnly## | When this parameter enabled when a Failover and Load Balancing Mode is in use, and a read-only connection is made to a host, assure that this connection is in read-only mode by setting the session to read-only.\\Default to false.\\Since 1.3.0, removed in 3.0.0|
1112
1119
| ##autoReconnect## |If this parameter is enabled and Failover and Load Balancing Mode is **not** in use, the connector will simply try to reconnect to its host after a failure. This is referred to as **Basic Failover**. \\If this parameter is enabled and Failover and Load Balancing Mode is in use, the connector will blacklist the failed host and try to connect to a different host of the same type. This is referred to as **Standard Failover**. \\Default is false.\\since 1.1.7, removed in 3.0.0|
1113
1120
| ##cachePrepStmts## | if useServerPrepStmts = true, cache the prepared informations in a LRU cache to avoid re-preparation of command. Next use of that command, only prepared identifier and parameters (if any) will be sent to server. This mainly permit for server to avoid reparsing query. \\//Default: true. Since 1.3.0, removed in 3.0.0//|
1114
-
| ##prepStmtCacheSize## | if useServerPrepStmts = true, defines the prepared statement cache size that option `cachePrepStmts` use. \\//Default: 250. Since 1.3.0, removed in 3.0.0//|
1115
1121
| ##callableStmtCacheSize## | This sets the number of callable statements that the driver will cache per VM if "cacheCallableStmts" is enabled.\\//Default: true. Since 1.4.0, removed in 3.0.0//|
1116
1122
| ##enablePacketDebug## |Driver will save the last 16 MySQL packet exchanges (limited to first 1000 bytes). Hexadecimal value of those packets will be added to stacktrace when an IOException occur.\\This option has no impact on performance but driver will then take 16kb more memory.\\//Default: false. Since 1.6.0, 2.0.1, removed in 3.0.0|
1117
1123
| ##failoverLoopRetries## |When the connector is searching silently for a valid host, this parameter defines the maximum number of connection attempts the connector will make before throwing an exception.\\This parameter differs from the "retriesAllDown" parameter because this silent search is used in situations where the connector can temporarily workaround the problem, such as by using the master connection to execute reads when the slave connection fails.\\Default: 120.\\since 1.2.0, removed in 3.0.0|
Copy file name to clipboardExpand all lines: archive/en/full-backup-and-restore-with-mariabackup/+comments/feed/index.html
+1-1
Original file line number
Diff line number
Diff line change
@@ -1,5 +1,5 @@
1
1
<?xml version="1.0" encoding="utf-8"?>
2
-
<rssxmlns:atom="http://www.w3.org/2005/Atom" version="2.0"><channel><title>MariaDB Knowledge Base Comments for: Full Backup and Restore with Mariabackup</title><link>https://mariadb.com/kb/en/full-backup-and-restore-with-mariabackup/+comments/feed/</link><description></description><atom:linkhref="https://mariadb.com/kb/en/full-backup-and-restore-with-mariabackup/+comments/feed/" rel="self"></atom:link><language>en-us</language><lastBuildDate>Mon, 03 Mar 2025 04:14:32 +0000</lastBuildDate><item><title>Re: Full Backup and Restore with Mariabackup</title><link>https://mariadb.com/kb/en/full-backup-and-restore-with-mariabackup/+comments/6855</link><description><p>Is it really necessary to stop the MariaDB Server process before restoring files into the <em>datadir</em>, even if that directory is not empty (expecting to only add new files inside it, and not override any existing file of course)?</p>
2
+
<rssxmlns:atom="http://www.w3.org/2005/Atom" version="2.0"><channel><title>MariaDB Knowledge Base Comments for: Full Backup and Restore with Mariadb-backup</title><link>https://mariadb.com/kb/en/full-backup-and-restore-with-mariabackup/+comments/feed/</link><description></description><atom:linkhref="https://mariadb.com/kb/en/full-backup-and-restore-with-mariabackup/+comments/feed/" rel="self"></atom:link><language>en-us</language><lastBuildDate>Tue, 04 Mar 2025 01:02:48 +0000</lastBuildDate><item><title>Re: Full Backup and Restore with Mariabackup</title><link>https://mariadb.com/kb/en/full-backup-and-restore-with-mariabackup/+comments/6855</link><description><p>Is it really necessary to stop the MariaDB Server process before restoring files into the <em>datadir</em>, even if that directory is not empty (expecting to only add new files inside it, and not override any existing file of course)?</p>
3
3
<p>I mean, the MariaDB Server process seems to scan the <em>datadir</em> contents only on start.<br>If new files are copied into it while the process is running, they don’t seem to be taken in account before the process is restarted.</p>
4
4
<p>Not needing to stop the server (and rather just restart it at end) should be a big advantage in terms of server unavailability time.</p>
5
5
<p>And my own tests running that way didn’t raise any problems doing that.</p>
0 commit comments