Martijn,
- Alkuperäinen viesti -
Lähettäjä: "Martijn Tonies" <[EMAIL PROTECTED]>
Vastaanottaja: <[EMAIL PROTECTED]>
Kopio: <[EMAIL PROTECTED]>
Lähetetty: Wednesday, October 20, 2004 11:34 AM
Aihe: Re: Innodb foreign keys names
> Hello Heikki,
>
...
&
trine : www.cedricom.com
""Heikki Tuuri"" <[EMAIL PROTECTED]> a écrit dans le message news:
[EMAIL PROTECTED]
> Martijn,
>
> - Original Message -
> From: ""Martijn Tonies"" <[EMAIL PROTECTED]>
> Newsgroups: mailing.database.m
Hello Heikki,
> >> >> you have to use a fairly recent 4.0 or 4.1 version of MySQL.
> >> >
> >> >Does a newer version allow you to change/set the names yourself?
> >>
> >> you can give the name yourself in new versions. Please look at the
InnoDB
> >> manual section.
> >
> > "A constraint name can
Martijn,
- Original Message -
From: ""Martijn Tonies"" <[EMAIL PROTECTED]>
Newsgroups: mailing.database.myodbc
Sent: Wednesday, October 20, 2004 10:08 AM
Subject: Re: Innodb foreign keys names
Hello Heikki,
>
>> you have to use a fairly recent 4.0 or 4.
Hello Heikki,
> >
> >> you have to use a fairly recent 4.0 or 4.1 version of MySQL.
> >
> >Does a newer version allow you to change/set the names yourself?
>
> you can give the name yourself in new versions. Please look at the InnoDB
> manual section.
"A constraint name can be given as of MySQL 4.
Martijn,
List: mysql
Subject:Re: Innodb foreign keys names
From: "Martijn Tonies"
Date: 2004-10-19 9:53:28
Message-ID: <01ad01c4b5c1$7c1e69a0$0a02a8c0 () martijn>
[Download message RAW]
>Heikki,
>
>> you have to use a fairly recent 4.0 or 4.1
Heikki,
> you have to use a fairly recent 4.0 or 4.1 version of MySQL.
Does a newer version allow you to change/set the names yourself?
With regards,
Martijn Tonies
Database Workbench - developer tool for InterBase, Firebird, MySQL & MS SQL
Server.
Upscene Productions
http://www.upscene.com
>
Richard,
you have to use a fairly recent 4.0 or 4.1 version of MySQL.
Best regards,
Heikki Tuuri
Innobase Oy
Foreign keys, transactions, and row level locking for MySQL
InnoDB Hot Backup - a hot backup tool for InnoDB which also backs up MyISAM
tables
http://www.innodb.com/order.php
Order MySQL t
> If possible, what is the syntax?
It's possible, but if you can't search, I'm not sure you can handle it. ;P
http://www.innodb.com/ibman.html#InnoDB_foreign_keys
Edward Dudlik
Becoming Digital
www.becomingdigital.com
Did I help you? Want to show your thanks?
www.amazon.com/o/registry/EGDXEBBWT
# [EMAIL PROTECTED] / 2003-03-24 23:49:59 +0100:
> this is what Mysql Reference Manual tells me about creating foreign
> keys.
> I understood how to use them, except for the restrict here ---\
> |
> [CONSTRAINT symbol] FOREIGN KE
"Scott Wong" <[EMAIL PROTECTED]>,
Do you think the following links may help?
* http://www.mysql.com/doc/en/example-Foreign_keys.html
* http://www.mysql.com/doc/en/ANSI_diff_Foreign_Keys.html
* http://www.mysql.com/doc/en/ALTER_TABLE.html
* http://www.mysql.com/doc/
Scott,
I would like to declare this as a 'feature'. You should not define multiple
foreign key constraints on the same foreign key/referenced key pair.
I could, of course, add an error message if someone tries to do that.
The algorithm in ON UPDATE CASCADE and ON DELETE CASCADE is this: InnoDB
t
Heikki Tuuri wrote:
In the future, MySQL might do the following: in
CREATE TABLE abbaguu (
...
FOREIGN KEY (column1) REFERENCES frobboz (column2)
) TYPE=InnoDB;
it could check if there is a suitable index in abbaguu. If not, it would
create the index automatically.
For what its worth, and I
te: Saturday, February 09, 2002 3:59 PM
Subject: Re: InnoDB foreign keys crash MySQL
>> Harald,
>
>Hi, Heikki!
>
...
>
>> I tested now with the official Linux binary of 4.0.1 (not -max) and it
>> worked ok on our dual Xeon Linux-2.4.16-SMP-64GB. I did not define any
>
ages 1
FIELDS: t2id id
FOREIGN KEY CONSTRAINT 0_17: test/t3 ( t2id )
REFERENCES test/t2 ( id )
---
END OF INNODB TABLE MONITOR OUTPUT
==
-Original Message-
From: Harald Fuchs <[EMAIL PROTECTED]>
To: Heikki Tuuri <[EMAIL PROTECTED]>
Cc:
In article <003b01c1b0a4$351665f0$540ec5c2@omnibook>,
"Heikki Tuuri" <[EMAIL PROTECTED]> writes:
> Harald,
> I tested the below with 3.23.48, and it worked ok.
> Could it be that you have not used DROP TABLE or DROP DATABASE to remove
> InnoDB tables? Then the internal data dictionary may be out
Harald,
I tested the below with 3.23.48, and it worked ok.
Could it be that you have not used DROP TABLE or DROP DATABASE to remove
InnoDB tables? Then the internal data dictionary may be out-of-sync from the
.frm files of your tables.
Please use innodb_table_monitor (section 9.1 in
http://www.
te: Saturday, February 09, 2002 3:59 PM
Subject: Re: InnoDB foreign keys crash MySQL
>> Harald,
>
>Hi, Heikki!
>
...
>
>> I tested now with the official Linux binary of 4.0.1 (not -max) and it
>> worked ok on our dual Xeon Linux-2.4.16-SMP-64GB. I did not define any
>
ages 1
FIELDS: t2id id
FOREIGN KEY CONSTRAINT 0_17: test/t3 ( t2id )
REFERENCES test/t2 ( id )
---
END OF INNODB TABLE MONITOR OUTPUT
==
-Original Message-
From: Harald Fuchs <[EMAIL PROTECTED]>
To: Heikki Tuuri <[EMAIL PROTECTED]>
Cc:
Harald,
I tested the below with 3.23.48, and it worked ok.
Could it be that you have not used DROP TABLE or DROP DATABASE to remove
InnoDB tables? Then the internal data dictionary may be out-of-sync from the
.frm files of your tables.
Please use innodb_table_monitor (section 9.1 in
http://www.
20 matches
Mail list logo
