Thanks Davide :)
All: sorry I forgot the answer here. Still getting used to a new email client.
Since you work with databases professionally, I'm assuming you know
how to be careful. When you have console access to mysql, it's a one
liner to make your own backup, and it's two lines to create a staging
copy.
But also, I had put a daily snapshot job in place, so for most
operations there's no need to be too paranoid, I know nobody here will
type commands randomly.
Sanne
On 20 February 2015 at 11:56, Davide D'Alto <davide(a)hibernate.org> wrote:
I'm currently trying to fix it
On Sat, Feb 14, 2015 at 1:13 AM, Gail Badner <gbadner(a)redhat.com> wrote:
>
> Good questions. I'll wait for a reply...
>
> ----- Original Message -----
> > From: "Hardy Ferentschik" <hardy(a)hibernate.org>
> > To: "Sanne Grinovero" <sanne(a)hibernate.org>
> > Cc: "Gail Badner" <gbadner(a)redhat.com>, "Davide
D'Alto"
> > <davide(a)hibernate.org>, "hibernate-dev"
> > <hibernate-dev(a)lists.jboss.org>
> > Sent: Friday, February 13, 2015 1:53:21 AM
> > Subject: Re: [hibernate-dev] in.relation.to error when posting a new
> > blog entry
> >
> > On Thu, Feb 12, 2015 at 06:57:55AM +0000, Sanne Grinovero wrote:
> > > I suspect it's a broken foreign key on MySQL, hopefully the error
> > > message
> > > will have some details? Some table maintenance should do the trick.
> >
> > Do you literally talk about the table maintenance commands like
> > REPAIR TABLE
> > (
http://dev.mysql.com/doc/refman/5.1/en/table-maintenance-sql.html),
> > or do you have something else in mind?
> >
> > Is it not a bit dangerous to let the uninitiated work against the prod
> > database?
> > Is there at least a nightly or at least regular copy of the database
> > which
> > can be
> > restored in case something goes wrong? And if so where is it and how do
> > I get
> > hold
> > of it?
> >
> > --Hardy
> >