[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]
[no subject]
- <!--x-content-type: text/plain -->
- <!--x-date: Wed Feb 9 08:43:02 2005 -->
- <!--x-from-r13: psbjyre ng bhgcbfgfragvary.pbz (Quevfgbcure Tbjyre) -->
- <!--x-message-id: [email protected] -->
- <!--x-reference: [email protected] -->
- <!--x-reference: [email protected] --> "http://www.w3.org/TR/html4/loose.dtd">
- <!--x-subject: [ale] database conversion -->
- <li><em>date</em>: Wed Feb 9 08:43:02 2005</li>
- <li><em>from</em>: cfowler at outpostsentinel.com (Christopher Fowler)</li>
- <li><em>in-reply-to</em>: <<a href="msg00256.html">[email protected]</a>></li>
- <li><em>references</em>: <<a href="msg00253.html">[email protected]</a>> <<a href="msg00256.html">[email protected]</a>></li>
- <li><em>subject</em>: [ale] database conversion</li>
In the MySQL realm all that was done with a Master -> Slave and done
with binary data. I'm not looking for Master->Slave. I've have had so
many problems getting the Master->Slave working and continue to work
under MySQL. I want backup databases and possible even load balancing.
Where I can have 2 database servers and then my application can contact
the first one available.
Maybe Oracle has this and not Postgress or MySQL?
On Wed, 2005-02-09 at 06:25, David Corbin wrote:
> Not that I have anything against PostgreSql, but when the database is built
> 'properly' MySql does have transactional support. Have you considered
> sticking with MySql and using the InnoDB engine? It would probably mean much
> less concern about 'switching'.
>
> David
>
> On Tuesday 08 February 2005 09:35 pm, James P. Kinney III wrote:
> > I am looking at a project that will involve migration of a MySql
> > database to PostgreSQL. The original db has numerous design errors that
> > are beginning to cause problems. The move to PostgreSQL will add the
> > transaction capabilities that would have prevented the current problem
> > causing the project (seqential transaction ID's would have been a great
> > start!)
> >
> > As this will need to be a parallel pair of db's for a while to run final
> > tests, I'm looking at pitfalls and processes others have used to migrate
> > from one 24x7 db to another seamlessly. I'm also looking for pointers on
> > getting identical data simultaneously into two seperate db's without
> > having to rewrite the entire app first.
> _______________________________________________
> Ale mailing list
> Ale at ale.org
> <a rel="nofollow" href="http://www.ale.org/mailman/listinfo/ale">http://www.ale.org/mailman/listinfo/ale</a>
</pre>
<!--X-Body-of-Message-End-->
<!--X-MsgBody-End-->
<!--X-Follow-Ups-->
<hr>
<ul><li><strong>Follow-Ups</strong>:
<ul>
<li><strong><a name="00263" href="msg00263.html">[ale] database conversion</a></strong>
<ul><li><em>From:</em> kaboom at gatech.edu (Chris Ricker)</li></ul></li>
</ul></li></ul>
<!--X-Follow-Ups-End-->
<!--X-References-->
<ul><li><strong>References</strong>:
<ul>
<li><strong><a name="00253" href="msg00253.html">[ale] database conversion</a></strong>
<ul><li><em>From:</em> jkinney at localnetsolutions.com (James P. Kinney III)</li></ul></li>
<li><strong><a name="00256" href="msg00256.html">[ale] database conversion</a></strong>
<ul><li><em>From:</em> dcorbin at machturtle.com (David Corbin)</li></ul></li>
</ul></li></ul>
<!--X-References-End-->
<!--X-BotPNI-->
<ul>
<li>Prev by Date:
<strong><a href="msg00258.html">[ale] Procmail rule</a></strong>
</li>
<li>Next by Date:
<strong><a href="msg00260.html">[ale] gmail invites - rediculous</a></strong>
</li>
<li>Previous by thread:
<strong><a href="msg00256.html">[ale] database conversion</a></strong>
</li>
<li>Next by thread:
<strong><a href="msg00263.html">[ale] database conversion</a></strong>
</li>
<li>Index(es):
<ul>
<li><a href="maillist.html#00259"><strong>Date</strong></a></li>
<li><a href="threads.html#00259"><strong>Thread</strong></a></li>
</ul>
</li>
</ul>
<!--X-BotPNI-End-->
<!--X-User-Footer-->
<!--X-User-Footer-End-->
</body>
</html>