<html>
<head>
<meta content="text/html; charset=utf-8" http-equiv="Content-Type">
</head>
<body bgcolor="#FFFFFF" text="#000000">
<div class="moz-cite-prefix">Usually more a problem of people using
"features" of a db over another, and when migration to the "other"
finding their dbi code doesn't work against it. <br>
<br>
I've this this trying to adapt with a blunt object code to work
with postgres vs. mysql. They used some math function in mysql or
the perl dbi for it that I'd have had to rewrite in a function
outside to do. I just ended up having to run both db's for some
network monitoring suites that liked one or the other sadly.<br>
<br>
Use of an abstraction layer like sqlalchemy helps that, but i am
not a dba or developer to extol virtues (or detractors) beyond
that.<br>
<br>
-mb<br>
<br>
<br>
On 05/28/2015 08:25 AM, Mark Phillips wrote:<br>
</div>
<blockquote
cite="mid:CAEqej2MpM8pPRGiGY1T2sk_Siw_Psj7GBAJnndzdd4a8FKei9g@mail.gmail.com"
type="cite">
<div dir="ltr">
<div>Are there easy ways to migrate from SQLite to MySQL if I
find I have under estimated what I need for a database?<br>
<br>
</div>
Mark<br>
</div>
<div class="gmail_extra"><br>
<div class="gmail_quote">On Thu, May 28, 2015 at 8:01 AM,
Michael Butash <span dir="ltr"><<a moz-do-not-send="true"
href="mailto:michael@butash.net" target="_blank">michael@butash.net</a>></span>
wrote:<br>
<blockquote class="gmail_quote" style="margin:0 0 0
.8ex;border-left:1px #ccc solid;padding-left:1ex">Consider
also the redundancy aspect, expect drives to fail and things
like that. Do you want a production website down while you
restore the os, reinstall everything, and presume to have an
up to date backup of the db right before it died? Rather
have a copy on a partner replication slave a cluster can
start feeding clients when the first dies.<br>
<br>
Also consider if you're ever going to need to scale the
website outside a monolithic single server, say with
haproxy, dedicated hardware load-balancers, etc in front of
mulitiple app servers. You need a way to scale data
horizontally, maybe replicating between regions, replicating
state of an in-use transaction (think shopping carts), etc.<br>
<br>
SQLite is usually for a down/dirty local install of
something that needs a db regardless of a real one or not,
or used as local scratch for performance reasons.<span
class="HOEnZb"><font color="#888888"><br>
<br>
-mb</font></span><span class="im HOEnZb"><br>
<br>
<br>
On 05/28/2015 03:17 AM, Joseph Sinclair wrote:<br>
<blockquote class="gmail_quote" style="margin:0 0 0
.8ex;border-left:1px #ccc solid;padding-left:1ex">
It really is a matter of preference most of the time,
but there are still some situations where one or the
other has a significant advantage.<br>
<br>
As one example:<br>
PostgreSQL (and it's forks) has some high availability
clustering support that isn't available currently for
MySQL (and it's forks).<br>
MySQL has some sharding support that isn't yet matched
in the Postgres world.<br>
</blockquote>
<br>
</span>
<div class="HOEnZb">
<div class="h5">
---------------------------------------------------<br>
PLUG-discuss mailing list - <a moz-do-not-send="true"
href="mailto:PLUG-discuss@lists.phxlinux.org"
target="_blank">PLUG-discuss@lists.phxlinux.org</a><br>
To subscribe, unsubscribe, or to change your mail
settings:<br>
<a moz-do-not-send="true"
href="http://lists.phxlinux.org/mailman/listinfo/plug-discuss"
target="_blank">http://lists.phxlinux.org/mailman/listinfo/plug-discuss</a><br>
</div>
</div>
</blockquote>
</div>
<br>
</div>
</blockquote>
<br>
</body>
</html>