You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@openjpa.apache.org by "Pinaki Poddar (JIRA)" <ji...@apache.org> on 2009/05/09 18:44:45 UTC
[jira] Resolved: (OPENJPA-966) Support Replication-enabled MySQL
[ https://issues.apache.org/jira/browse/OPENJPA-966?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Pinaki Poddar resolved OPENJPA-966.
-----------------------------------
Resolution: Fixed
> Support Replication-enabled MySQL
> -----------------------------------
>
> Key: OPENJPA-966
> URL: https://issues.apache.org/jira/browse/OPENJPA-966
> Project: OpenJPA
> Issue Type: New Feature
> Components: jdbc
> Affects Versions: 2.0.0-M1, 2.0.0
> Environment: MySQL
> Reporter: Pinaki Poddar
> Assignee: Pinaki Poddar
> Fix For: 2.0.0-M1, 2.0.0
>
> Original Estimate: 24h
> Remaining Estimate: 24h
>
> Starting with Connector/J 3.1.7, a MySQL JDBC driver is available [2] that will automatically send queries to a read/write master, or a failover or round-robin loadbalanced set of slaves based on the state of Connection.getReadOnly() .
> OpenJPA can take advantage of this driver by setting up read-only property of the connection based on the dirty nature of the current transaction [1].
> [1] http://n2.nabble.com/Mysql-Connector-J-ReplicantConnection-tc2431984.html
> [2] http://dev.mysql.com/doc/refman/5.1/en/connector-j-reference-replication-connection.html
--
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.