Natale,
- Original Message -
From: Natale Babbo [EMAIL PROTECTED]
Newsgroups: mailing.database.mysql
Sent: Wednesday, January 15, 2003 9:33 AM
Subject: innofb foreign keys problem
# - 3rd post - #
# - PLEASE HELP -- #
hi to all,
is it still true
# - 3rd post - #
# - 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
On Tue, 14 Jan 2003 16:41:06 +0100 (CET)
Natale Babbo [EMAIL PROTECTED] wrote:
# - 3rd post - #
# - PLEASE HELP -- #
hi to all,
is it still true that mysql/innodb needs explicit
index creation on foreign keys?
Yes
why can't i use a standard syntax
CIMEN [EMAIL PROTECTED] ha scritto:
There are no other way
you have to create the index first
- Original Message -
From: Natale Babbo [EMAIL PROTECTED]
To: [EMAIL PROTECTED]
Sent: Tuesday, January 14, 2003 5:41 PM
Subject: innofb foreign keys problem
# - 3rd post
To: Okan CIMEN; [EMAIL PROTECTED]
Subject: Re: innofb foreign keys problem
many thanks for your reply.
then i ask me: why mysql needs explicit creation
instead of create itself what it needs?
manually creating the index seems to be a big
complication (for big databases) and a waste of time.
don't you
then i ask me: why mysql needs explicit creation
instead of create itself what it needs?
manually creating the index seems to be a big
complication (for big databases) and a waste of time.
don't you think so?
it's a bug or a wanted feature? why?
I agree with you 100%.
A foreign key,as its
it's easy
to *think* your app is working correctly when it could in fact be trashing referential
integrity.
From: Natale Babbo [EMAIL PROTECTED]
Subject: innofb foreign keys problem
Date: 15/01/2003 2:41:06
To: [EMAIL PROTECTED]
# - 3rd post - #
# - PLEASE
