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,
>
...
&
yodbc
> 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.1 version of MySQL.
> >> >
> >> >Does a newer version allow you
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
>
technical support from https://order.mysql.com/
.
From: "Richard - CEDRICOM" ([EMAIL PROTECTED])
Subject: Innodb foreign keys names
This is the only article in this thread
View: Original Format
Newsgroups: mailing.database.myodbc
Date: 2004-10-0
Hi everybody,
Still have a problem with naming "foreign key" constraints on innodb tables.
Can't retrieve any of the name that was given to the constraints.
"Internally generated" IDs are always given to the foreign keys... no way to
apply a "drop foreign key 0_" on a replicated server or ger
On Thu, 13 May 2004 10:34:37 -0700 (PDT)
David Blomstrom <[EMAIL PROTECTED]> wrote:
> I thought that only InnoDB tables could be joined -
> and only if they had foreign keys. But it sounds like
> any kind of table can be joined, and it doesn't need a
> foreign key.
Exactly, you can do a join with
> I thought that only InnoDB tables could be joined -
> and only if they had foreign keys. But it sounds like
> any kind of table can be joined, and it doesn't need a
> foreign key.
The ability to join a bunch of tables in a query is different from foreign
keys. A foreign key is a relationhip be
I thought that only InnoDB tables could be joined -
and only if they had foreign keys. But it sounds like
any kind of table can be joined, and it doesn't need a
foreign key.
Can someone explain InnoDB, MyISAM and foreign keys in
plain English? If I understand correctly, foreign keys
simply help en
zon.com/o/registry/EGDXEBBWTYUU
- Original Message -
From: "Mikael Engdahl" <[EMAIL PROTECTED]>
To: <[EMAIL PROTECTED]>
Sent: Tuesday, 24 June, 2003 15:36
Subject: InnoDB foreign keys
Hello,
Is it possible to create a foreign key that referencestwo columns, if
the refere
Hello,
Is it possible to create a foreign key that referencestwo columns, if
the referenced table uses more two colums for it's primary key?
If possible, what is the syntax?
Mikael Engdahl
--
MySQL General Mailing List
For list archives: http://lists.mysql.com/mysql
To unsubscribe:http://li
# [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
--- Begin Message ---
Hi all
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 KEY (index_col_name, ...)
Hi all
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 KEY (index_col_name, ...) |
On Thursday 20 March 2003 23:25, Andreas wrote:
> I'm trying to get going with InnoDB.
> As for now I created several tables which relate to each other with some
> foreign key restrictions.
>
> mysqldump --all --opt writes 6++ MB stuff in a textfile that mysqld
> won't accept without SET FOREIG
I'm trying to get going with InnoDB.
As for now I created several tables which relate to each other with some
foreign key restrictions.
mysqldump --all --opt writes 6++ MB stuff in a textfile that mysqld
won't accept without SET FOREIGN_KEY_CHECKS=0;
After SET FOREIGN_KEY_CHECKS=1; is my
ww.mysql.com/doc/en/Using_InnoDB_tables.html
* http://www.mysql.com/doc/en/Indexes.html
This was an automated response to your email 'InnoDB foreign keys bug'.
Final search keyword used to query the manual was 'InnoDB foreign keys bug'.
Feedbacks, suggestions and compla
ct: InnoDB foreign keys bug
From: Scott Wong
Date: Thu, 6 Feb 2003 15:25:12 -0800
Version: Mysql 4.0.10-gamma
Description: Innodb fails to follow the foreign key rules after alter table.
This bug can be done
Version: Mysql 4.0.10-gamma
Description: Innodb fails to follow the foreign key rules after alter table.
This bug can be done in several ways.
How to repeat
These variations gives same errors.
1st bug example:
drop table if exists parent;
drop table if exists child;
CREATE TABLE parent(id INT
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
table scan.
Regards,
Heikki
Innobase Oy
sql query
- Original Message -
From: "Natale Babbo" <[EMAIL PROTECTED]>
To: <[EMAIL PROTECTED]>
Sent: Tuesday, January 14, 2003 5:52 PM
Subject: please help me - problem with innodb foreign keys
> # - PLEASE HELP
# - PLEASE HELP -- #
hi to all,
is it still true that mysql/innodb needs explicit
index creation on foreign keys?
why can't i use a standard syntax for foreign keys
creations?
i have a database schema (ddl) with over 50 tables and
i was trying to create the database on mysql when
Hello all,
I am testing MySql Max 4.0.1 alpha. I have configured innodb tablespace and created
the two manual tables example.
But when I try to do a mysqldump to re-create the tables on another DB or 'SHOW CREATE
TABLE child', NO-FOREIGN key information is gathered on results.
However 'SHOW
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.
(MySQL 4.0.1-alpha-Max-log, your Linux binary)
The following works fine (just a slight variation of what is in the manual):
CREATE TABLE t1 (
id INT UNSIGNED NOT NULL AUTO_INCREMENT,
PRIMARY KEY (id)
) TYPE=InnoDB;
CREATE TABLE t2 (
id INT UNSIGNED NOT NULL AUTO_INCREMENT,
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.
34 matches
Mail list logo
