Tripp,
thanks for your prompt response, however I would like
to keep the FOREIGN_KEY_CHECKS enabled so I dont shoot
myself on the foot.
unless, as it looks right now, it turns impossible to
delete stuff from the table.
thanks,
esv.
--- Tripp Bishop <[EMAIL PROTECTED]> wrote:
> Enrique,
>
> Tr
From: "starofframe" <[EMAIL PROTECTED]>
> CanIt Vote for ID 62298InnoDB still has the major issue about the slow
access of database...
> I use mysql database for website..
For a new application we're building we performed some tests to decide upon
MyISAM/InnoDB and two table lay-outs. We ran two pr
CanIt Vote for ID 62298InnoDB still has the major issue about the slow access of
database...
I use mysql database for website..
- Original Message -
From: Daniel Kasak
To: starofframe ; [EMAIL PROTECTED]
Sent: Friday, July 02, 2004 11:08 AM
Subject: Re: referential integrity
starofframe wrote:
Hi All,
I've read that MyIsam type table doesnt have the "referential integrity" function...
I hav tried to find other 3rd party s/w that can solve the issue.
Finally I read from PhpMyAdmin documentation that "recently PhpMyAdmin can check
referential Integrity"
but I still
At 16:20 +0100 28-07-2003, Tom Gazzini wrote:
I need to have a table that supports FULLTEXT searches. This implies
that this table should be a MyISAM table.
However, I also require that this table act as a parent for child tables
in order to support referential integrity. If I create the child tabl
> I need to have a table that supports FULLTEXT searches. This
> implies that this table should be a MyISAM table.
>
> However, I also require that this table act as a parent for
> child tables in order to support referential integrity. If I
> create the child tables as INNODB tables, will ref
Adnan,
Tuesday, July 16, 2002, 2:18:22 PM, you wrote:
AY> I am having a problem in referential Integrity in mySQL. I have
AY> created a parent table which have deptno from 1-10. When i insert a row in
AY> child table that has deptno as foreign key it accept a value 11 which is
AY> actuall
At 11:02 PM 8/12/01 -0300, you wrote:
>I read that MySQL doesn't support the referential integrity, so i wan to
>know if you recommend to use it in systems with complex relationated
>tables in a database.
>If yes, where can i find helpfull documentation about that.
>thanks
>PD: sorry about my gr
Well, dunno about that, but I've got a system here which I designed round
the fact that MySQL *doesn't* have RI.
When a customer gets deleted (or changes it's reference id), the data for
the old id has to remain in the system. I know that if I was using a
product which enforces RI I'd design it d
uot; <[EMAIL PROTECTED]>
Cc: <[EMAIL PROTECTED]>
Sent: Wednesday, July 11, 2001 10:20 AM
Subject: RE: Referential Integrity
>
> In my experience, most "large corporate" databases
> are not implemented with RI enabled. The RI constraints
> often interfere with user
0.596.1443|
||
--
|__|__|
|| ||
ooO Ooo
-Original Message-
From: pak [mailto:[EMAIL PROTECTED]]
Sent: Tuesday, July 10, 2001 11:31 PM
To: Ken Sommers; [EMAIL PROTECTED]
Subject: Re: Referential Integrity
So is MySQL not suitable for large corporate database ?
- Original Message -
2001 11:58 PM
To: Michael Bacarella; pak
Cc: [EMAIL PROTECTED]
Subject: Re: Referential Integrity
Please give some examples of 'bad' design where a "foreign key" would have
to be changed..
ken
- Original Message -
From: "Michael Bacarella" <[EMAIL PROTECTED
On Wed, Jul 11, 2001 at 01:31:15PM +1000, pak wrote:
>
> So is MySQL not suitable for large corporate database ?
It often depends on the corporation and who makes the decisions. In
many corporations, it's the folks who know little about the
technology. In the minority of them, it appears to be
ECTED]>; <[EMAIL PROTECTED]>
Sent: Tuesday, July 10, 2001 8:53 PM
Subject: Re: Referential Integrity
> On Wed, Jul 11, 2001 at 01:31:15PM +1000, pak wrote:
>
> > So is MySQL not suitable for large corporate database ?
>
> That depends more on what you feel is suitable, r
On Wed, Jul 11, 2001 at 01:31:15PM +1000, pak wrote:
> So is MySQL not suitable for large corporate database ?
That depends more on what you feel is suitable, rather than
someone else trying to tell you objectively what is suitable.
You can argue for and against the use of foreign keys and both
Please give some examples where you would need the dbms to do the
referential integrity?
Ken
- Original Message -
From: "pak" <[EMAIL PROTECTED]>
To: "Ken Sommers" <[EMAIL PROTECTED]>; <[EMAIL PROTECTED]>
Sent: Tuesday, July 10, 2001 8:31 PM
Subjec
So is MySQL not suitable for large corporate database ?
- Original Message -
From: "Ken Sommers" <[EMAIL PROTECTED]>
To: "pak" <[EMAIL PROTECTED]>; <[EMAIL PROTECTED]>
Sent: Wednesday, July 11, 2001 1:24 PM
Subject: Re: Referential Integrity
| hello
hello,
Do simple input validation.
If the user is entering what is supposed to be a primary key value,
make sure it is a valid key before sticking it in any where, If it's a bogus
key .tell the user to try again.
If user wants you to delete rows from a primary table (customer)that have
"foreign
18 matches
Mail list logo
