From: kashani <kashani-list@badapple.net>
To: gentoo-user@lists.gentoo.org
Subject: Re: [gentoo-user] [OT] Looking for a tool to produce 'reverse' SQL
Date: Thu, 15 Jun 2006 14:16:44 -0700 [thread overview]
Message-ID: <4491CE3C.9030202@badapple.net> (raw)
In-Reply-To: <20060615205451.27681.qmail@web53204.mail.yahoo.com>
Benjamin Blazke wrote:
>
> --- kashani <kashani-list@badapple.net> wrote:
>
>> The tool you're looking for is called a DBA. :-)
>
> I see. So it's up to QA to test extensively and up to
> the DBA to recover from a disaster.
>
> I hoped there would be a more automated solution but
> it seems that it's not really doable. Thanks for such
> a quick answer ;-)
That's pretty much the way we've been doing it, but if there is a
better way I'd like to hear it too as I'm a poor imitation of a DBA.
However I don't see any easy solutions for combined application, data,
schema change rollbacks especially when changes to one cause
dependencies in others.
As an illustration you change u_user.login_name to varchar(64) from
varchar(32). Users start creating longer users names. A few hours later
you find some problems in how your application handles longer names. If
you needed to rollback the alter table command is easy, but some of your
data would now be invalid. Rather than rollback the easier fix is to
update the application and hopefully the change is a single file update.
I still think there are cases when you could rollback, but they'd have
to be so simple that having a tool to generate the sql would be overkill.
Ramin
--
gentoo-user@gentoo.org mailing list
next parent reply other threads:[~2006-06-15 21:28 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <20060615205451.27681.qmail@web53204.mail.yahoo.com>
2006-06-15 21:16 ` kashani [this message]
2006-06-15 18:15 [gentoo-user] [OT] Looking for a tool to produce 'reverse' SQL Benjamin Blazke
2006-06-15 18:55 ` kashani
2006-06-17 20:31 ` Daniel Iliev
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=4491CE3C.9030202@badapple.net \
--to=kashani-list@badapple.net \
--cc=gentoo-user@lists.gentoo.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox