"Tucker, Gabriel" <[EMAIL PROTECTED]> wrote:
> Victoria=20
>
> That seemed to work well, thank you.
>
> However, I received another error that I am not sure how to troubleshoot =
> during the restore:
>ERROR 1114 at line 83 in file: =
> '/bb/bin/mysql/backups/archive_4320.sql': The table
Gabriel,
First of all, sorry for my poor english (I´m just a brazilian guy - eu
quase não sei falar o portugues, imaginem o ingles então.)
Tucker, Gabriel wrote:
Luciano
I am confused... As far as I can tell, the set foreign_key_checks=0; is used with the
load data infile command. I am not us
tk_sum' is full
What can I do here?
Thanks - Gabe
-Original Message-
From: Victoria Reznichenko [mailto:[EMAIL PROTECTED]
Sent: Tuesday, May 04, 2004 10:35 AM
To: [EMAIL PROTECTED]
Subject: Re: InnoDB - Foreign Key - Error 150.
"Tucker, Gabriel" <[EMAIL PROTECTED]>
n I do here?
Thanks - Gabe
-Original Message-
From: Victoria Reznichenko [mailto:[EMAIL PROTECTED]
Sent: Tuesday, May 04, 2004 10:35 AM
To: [EMAIL PROTECTED]
Subject: Re: InnoDB - Foreign Key - Error 150.
"Tucker, Gabriel" <[EMAIL PROTECTED]> wrote:
> Marvin
>
> I
On Tue, 4 May 2004 11:01:59 -0400
"Tucker, Gabriel" <[EMAIL PROTECTED]> wrote:
> Luciano
>
> I am confused... As far as I can tell, the set
> foreign_key_checks=0; is used with the load data infile command.
Actually, I think that it is used for all operations on the DBMS, not just load data
: [EMAIL PROTECTED]
Subject: Re: InnoDB - Foreign Key - Error 150.
"Tucker, Gabriel" <[EMAIL PROTECTED]> wrote:
> Marvin
>
> I believe that is the problem with the restore. When I create the =
> archive file using the mysqldump command and options previously listed, =
L PROTECTED]
Sent: Tuesday, May 04, 2004 10:03 AM
To: Tucker, Gabriel
Subject: Re: InnoDB - Foreign Key - Error 150.
Put in your script:
set foreign_key_checks=0;
in the first line.
mysqldump dumps tables in alphabetical order.
Tucker, Gabriel wrote:
> Hello All:
>
> I am having a p
"Tucker, Gabriel" <[EMAIL PROTECTED]> wrote:
> Marvin
>
> I believe that is the problem with the restore. When I create the =
> archive file using the mysqldump command and options previously listed, =
> I get the create table in the order listed below and thus, the foreign =
> key constraint is
e end!
Best of luck,
Ken
- Original Message -
From: "Marvin Wright" <[EMAIL PROTECTED]>
To: "Tucker, Gabriel" <[EMAIL PROTECTED]>; "Mysql General
(E-mail)" <[EMAIL PROTECTED]>
Sent: Tuesday, May 04, 2004 10:22 AM
Subject: RE: InnoDB - Foreign Key -
On Tue, 4 May 2004 09:46:27 -0400
"Tucker, Gabriel" <[EMAIL PROTECTED]> wrote:
> Hello All:
>
> I am having a problem with both V4.0.16 and 4.0.18. Let me explain:
>
> I have a database with two InnoDB tables in v4.0.16. I backup up
> this database every night using the following command:
>
>
---
From: Tucker, Gabriel [mailto:[EMAIL PROTECTED]
Sent: 04 May 2004 15:13
To: Mysql General (E-mail)
Subject: RE: InnoDB - Foreign Key - Error 150.
Marvin
I believe that is the problem with the restore. When I create the archive
file using the mysqldump command and options previously listed, I
l database on its own port and then run from the
prompt "mysql --port= --socket= -p < archive_file.sql"
Thanks again
Gabe
-Original Message-
From: Marvin Wright [mailto:[EMAIL PROTECTED]
Sent: Tuesday, May 04, 2004 9:59 AM
To: Tucker, Gabriel; Mysql General (E-mail)
Subject: R
Hi,
Are you creating them in the correct order ?
object_type must exist before you can create cur_reject_tk_sum otherwise the
foreign key will give errors.
Marvin
-Original Message-
From: Tucker, Gabriel [mailto:[EMAIL PROTECTED]
Sent: 04 May 2004 14:46
To: Mysql General (E-mail)
Subje
whoops, yes, thanks, missed that
Victor Pendleton wrote:
One thing that stands out is the data types are different sizes.
http://www.mysql.com/doc/en/InnoDB_foreign_key_constraints.html
-Original Message-
From: R.Dobson [mailto:[EMAIL PROTECTED]
Sent: Wednesday, September 24, 2003 8:42
One thing that stands out is the data types are different sizes.
http://www.mysql.com/doc/en/InnoDB_foreign_key_constraints.html
-Original Message-
From: R.Dobson [mailto:[EMAIL PROTECTED]
Sent: Wednesday, September 24, 2003 8:42 AM
To: [EMAIL PROTECTED]
Subject: innodb foreign key
Hi,
day, September 18, 2003 11:50 PM
Subject: Re: InnoDB Foreign Key Constraint Issue
> David,
>
> - Original Message -
> From: "David Griffiths" <[EMAIL PROTECTED]>
> Newsgroups: mailing.database.myodbc
> Sent: Friday, September 19, 2003 4:07 AM
> Subject: In
David,
- Original Message -
From: "David Griffiths" <[EMAIL PROTECTED]>
Newsgroups: mailing.database.myodbc
Sent: Friday, September 19, 2003 4:07 AM
Subject: InnoDB Foreign Key Constraint Issue
> The following constraint is failing:
>
> ALTER TABLE address_list ADD CONSTRAINT FOREIGN KE
On Wednesday 19 March 2003 15:19, Thorsten Schmidt wrote:
> how can I remove a foreign key in InnoDB?
> ALTER TABLE DROP (FOREIGN) KEY `key`
> isn't working (and also not specified in documentation)... : (
Currently you should recreate table to remove FOREIGN KEY CONSTRAINTS.
--
For technical
>
> > Dear all,
> > how can I remove a foreign key in InnoDB?
> > ALTER TABLE DROP (FOREIGN) KEY `key`
> > isn't working (and also not specified in documentation)... : (
> >
> >
> It's not implemented yet. You can copy your data to another table without
> the foreign key constraint, drop origin
Scott,
http://www.innodb.com/ibman.html#InnoDB_foreign_keys
"
Starting from version 3.23.50 you can also associate the ON DELETE CASCADE
or ON DELETE SET NULL clause with the foreign key constraint. Corresponding
ON UPDATE options are available starting from 4.0.8.
"
Regards,
Heikki
Innobase Oy
Muhammed,
- Original Message -
From: "Muhammed Syyid" <[EMAIL PROTECTED]>
Newsgroups: mailing.database.mysql
Sent: Thursday, January 16, 2003 3:06 PM
Subject: Re: InnoDB Foreign Key Questions
> Second the same question :). What does the CONSTRAINT keyword
> reg
Hi!
Please send your postings to [EMAIL PROTECTED] The newsgroup
mailing.database.mysql is only a mirror of that mailing list.
The error message below is misleading. It should really be 'Cannot update a
parent row...'. Internally InnoDB does the update by deleting and
reinserting the index record
From: Heikki Tuuri
To: Serdioukov Edouard
Cc: [EMAIL PROTECTED]
Sent: Tuesday, October 29, 2002 7:23 PM
Subject: Re: InnoDB, Foreign Key
Edouard,
I tested this on Linux using mysql-max-3.23.51, the .tar.gz distro. It
worked ok.
Are you sure you were using 3.23.51? Starting from 3.23.50, InnoDB
Edouard, you have a foreign key referencing a column in its own table.
PB
-
- Original Message -
From: "Serdioukov Edouard" <[EMAIL PROTECTED]>
To: <[EMAIL PROTECTED]>
Sent: Tuesday, October 29, 2002 3:23 AM
Subject: InnoDB, Foreign Key
Hello
I use Linux Red Hat 7.3 and MySQL-max
Markus,
the problem is that name_id is UNSIGNED in the first table and SIGNED in the
second.
As stated in the manual, integer columns must have the same signedness and
size in a foreign key constraint.
Regards,
Heikki
Innobase Oy
- Original Message -
From: "Markus Lervik" <[EMAIL PROT
on't
agree to these terms, you should return this email in no more than 24 hours
stating the reason of disagreement.
-Oorspronkelijk bericht-----
Van: Markus Lervik [mailto:[EMAIL PROTECTED]]
Verzonden: maandag 10 juni 2002 10:45
Aan: Kiss Dániel
CC: [EMAIL PROTECTED]
Onderwerp: Re: Inno
On Monday 10 Jun 2002 11:44 am, Markus Lervik wrote:
> mysql> show create table ip_name_tbl\G
> *** 1. row ***
>Table: ip_name_tbl
> Create Table: CREATE TABLE `ip_name_tbl` (
[snip]
> `name_id` int(11) NOT NULL default '0',
[snip]
> mysq
On Monday 10 Jun 2002 11:17 am, you wrote:
> First of all the referenced key must be on PRIMARY KEY.
...which means my 'id' -field can't be a primary key, right?
> But I've seen in your table definition a quite strange thing. You have a
> UNIQUE and an ORDINARY key definition on the same field.
Heya!
You need an INDEX.
Try doing this first :
alter table ip_name_tbl add INDEX(name_id);
And add then your constraint.
EG
mysql> SHOW CREATE TABLE ip_name_tbl\G
*** 1. row ***
Table: ip_name_tbl
Create Table: CREATE TABLE `ip_name_tbl
First of all the referenced key must be on PRIMARY KEY.
But I've seen in your table definition a quite strange thing. You have a
UNIQUE and an ORDINARY key definition on the same field.
Here:
...
> UNIQUE KEY `name_id` (`name_id`), <- THIS IS THE FIRST DEFINITION
> UNIQUE KEY `comp_name` (`
Daniel,
- Original Message -
From: "Daniel Rand" <[EMAIL PROTECTED]>
Newsgroups: mailing.database.mysql
Sent: Monday, May 13, 2002 5:24 PM
Subject: InnoDB Foreign Key Constraints
> Hi,
>
> Does anyone know if it's possible to set up a foreign key constraint where
> one table references
31 matches
Mail list logo
