12:42 a.m.
Hi,
I'm trying to create a new blog entry on in.relation.to
but an exception occurs about the violation of an integrity constraint.
Any idea on how to solve the issue?
Thanks,
Davide
10:36 a.m.
I ran into the same thing a couple of weeks ago when I deleted some spam comments before
trying to create new weblog. I asked Sanne about this and he mentioned that he's seen
this happen after deleting spam comments. He said it would require some clean up, but he
didn't have time.
Sanne, I know you're very busy. Can you point one of us in the right direction to
clean up what is necessary?
Thanks,
Gail
----- Original Message -----
From: "Davide D'Alto" <davide(a)hibernate.org>
To: "hibernate-dev" <hibernate-dev(a)lists.jboss.org>
Sent: Wednesday, February 11, 2015 7:42:52 AM
Subject: [hibernate-dev] in.relation.to error when posting a new blog entry
Hi,
I'm trying to create a new blog entry on in.relation.to
but an exception occurs about the violation of an integrity constraint.
Any idea on how to solve the issue?
Thanks,
Davide
_______________________________________________
hibernate-dev mailing list
hibernate-dev(a)lists.jboss.org
https://lists.jboss.org/mailman/listinfo/hibernate-dev
3:57 p.m.
Hi, sorry I forgot about this and I'm currently away so if someone could
look at it that would be great.
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.
You'll have to ssh into in.relation.to and from there connect to the MySQL
console. The connection details are in the datasource description deployed
in the AS (I don't remember them but that's a good place to read the
hostname and access credentials to the db).
The firewall on the db server will not allow you to connect from your own
place, so make sure you use the MySQL console from the in.relation.to
server.
An alternative might be to use the AWS dashboard, maybe it has some tools
for db maintenance? I usually use the terminal myself.
Thanks
Sanne
On Thu, 12 Feb 2015 02:36 Gail Badner <gbadner(a)redhat.com> wrote:
I ran into the same thing a couple of weeks ago when I deleted some
spam
comments before trying to create new weblog. I asked Sanne about this and
he mentioned that he's seen this happen after deleting spam comments. He
said it would require some clean up, but he didn't have time.
Sanne, I know you're very busy. Can you point one of us in the right
direction to clean up what is necessary?
Thanks,
Gail
----- Original Message -----
> From: "Davide D'Alto" <davide(a)hibernate.org>
> To: "hibernate-dev" <hibernate-dev(a)lists.jboss.org>
> Sent: Wednesday, February 11, 2015 7:42:52 AM
> Subject: [hibernate-dev] in.relation.to error when posting a new blog
entry
>
> Hi,
> I'm trying to create a new blog entry on in.relation.to
> but an exception occurs about the violation of an integrity constraint.
>
> Any idea on how to solve the issue?
>
> Thanks,
> Davide
>
> _______________________________________________
> hibernate-dev mailing list
> hibernate-dev(a)lists.jboss.org
> https://lists.jboss.org/mailman/listinfo/hibernate-dev
3:40 p.m.
I can look into this tomorrow. Please let me know if someone is already working on this.
Thanks,
Gail
----- Original Message -----
From: "Sanne Grinovero" <sanne(a)hibernate.org>
To: "Gail Badner" <gbadner(a)redhat.com>, "Davide D'Alto"
<davide(a)hibernate.org>
Cc: "hibernate-dev" <hibernate-dev(a)lists.jboss.org>, "Sanne
Grinovero" <sanne(a)hibernate.org>
Sent: Wednesday, February 11, 2015 10:57:55 PM
Subject: Re: [hibernate-dev] in.relation.to error when posting a new blog entry
Hi, sorry I forgot about this and I'm currently away so if someone could
look at it that would be great.
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.
You'll have to ssh into in.relation.to and from there connect to the MySQL
console. The connection details are in the datasource description deployed
in the AS (I don't remember them but that's a good place to read the
hostname and access credentials to the db).
The firewall on the db server will not allow you to connect from your own
place, so make sure you use the MySQL console from the in.relation.to
server.
An alternative might be to use the AWS dashboard, maybe it has some tools
for db maintenance? I usually use the terminal myself.
Thanks
Sanne
On Thu, 12 Feb 2015 02:36 Gail Badner <gbadner(a)redhat.com> wrote:
> I ran into the same thing a couple of weeks ago when I deleted some spam
> comments before trying to create new weblog. I asked Sanne about this and
> he mentioned that he's seen this happen after deleting spam comments. He
> said it would require some clean up, but he didn't have time.
>
> Sanne, I know you're very busy. Can you point one of us in the right
> direction to clean up what is necessary?
>
> Thanks,
> Gail
> ----- Original Message -----
> > From: "Davide D'Alto" <davide(a)hibernate.org>
> > To: "hibernate-dev" <hibernate-dev(a)lists.jboss.org>
> > Sent: Wednesday, February 11, 2015 7:42:52 AM
> > Subject: [hibernate-dev] in.relation.to error when posting a new blog
> entry
> >
> > Hi,
> > I'm trying to create a new blog entry on in.relation.to
> > but an exception occurs about the violation of an integrity constraint.
> >
> > Any idea on how to solve the issue?
> >
> > Thanks,
> > Davide
> >
> > _______________________________________________
> > hibernate-dev mailing list
> > hibernate-dev(a)lists.jboss.org
> > https://lists.jboss.org/mailman/listinfo/hibernate-dev
>
6:53 p.m.
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
10:13 a.m.
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
8:56 p.m.
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
>
9:34 p.m.
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
> >
3366
days inactive
3375
days old
7 comments
4 participants
participants (4)
-
Davide D'Alto -
Gail Badner -
Hardy Ferentschik -
Sanne Grinovero