Re: Foreign Key Info error in manual

2001-01-16 Thread Jeremy D. Zawodny
On Tue, Jan 16, 2001 at 08:00:09PM -0600, Scott Gerhardt wrote: > Thanks for your responses Jeremy, I'm just trying to clarify any > misunderstandings I may have. > > So, as far as the example goes, the relationships between shirts and > people is maintained by using the LAST_INSERT_ID (in one c

RE: Foreign Key Info error in manual

2001-01-16 Thread Scott Gerhardt
Thanks Paul, And it doesn't really matter if the ID's are cronological that's what timestamps are for. ___ Scott A. Gerhardt P.Geo. Gerhardt Information Technologies [EMAIL PROTECTED] ___ > > On Tue, Jan 16, 2001 at 07:22:48PM -

RE: Foreign Key Info error in manual

2001-01-16 Thread Scott Gerhardt
Thanks for clearing that up Benjamin! It all makes sense now :-D - Scott > > On Tue, Jan 16, 2001 at 07:22:48PM -0600, [EMAIL PROTECTED] wrote: > > So referential integrity is maintained but AUTO_INCREMENT > values may not be > > chronological? > > > > Connection A's LAST_INSERT_ID()

Re: Foreign Key Info error in manual

2001-01-16 Thread Benjamin Pflugmann
Hi. On Tue, Jan 16, 2001 at 07:22:48PM -0600, [EMAIL PROTECTED] wrote: > So referential integrity is maintained but AUTO_INCREMENT values may not be > chronological? > > Connection A's LAST_INSERT_ID() may be 3 at 15:20 > AND > Connection B's LAST_INSERT_ID() may be 4 at 15:18 Hm, yes, but only

Re: Foreign Key Info error in manual

2001-01-16 Thread Paul DuBois
On Tue, Jan 16, 2001 at 07:22:48PM -0600, Scott Gerhardt wrote: > So referential integrity is maintained but AUTO_INCREMENT values may not be > chronological? > > Connection A's LAST_INSERT_ID() may be 3 at 15:20 > AND > Connection B's LAST_INSERT_ID() may be 4 at 15:18 The AUTO_INCREMENT values

RE: Foreign Key Info error in manual

2001-01-16 Thread Scott Gerhardt
Thanks for your responses Jeremy, I'm just trying to clarify any misunderstandings I may have. So, as far as the example goes, the relationships between shirts and people is maintained by using the LAST_INSERT_ID (in one connection) but referential integrity is not maintained in terms of foriegn

Re: Foreign Key Info error in manual

2001-01-16 Thread Jeremy D. Zawodny
On Tue, Jan 16, 2001 at 07:22:48PM -0600, Scott Gerhardt wrote: > So referential integrity is maintained but AUTO_INCREMENT values may > not be chronological? Nope. Referential integrity is not maintained. Jeremy -- Jeremy D. Zawodny, <[EMAIL PROTECTED]> Technical Yahoo - Yahoo Finance Desk: (

RE: Foreign Key Info error in manual

2001-01-16 Thread Scott Gerhardt
So referential integrity is maintained but AUTO_INCREMENT values may not be chronological? Connection A's LAST_INSERT_ID() may be 3 at 15:20 AND Connection B's LAST_INSERT_ID() may be 4 at 15:18 - Scott > In the last episode (Jan 16), Scott Gerhardt said: > > I was reading the informat

Re: Foreign Key Info error in manual

2001-01-16 Thread Jeremy D. Zawodny
On Tue, Jan 16, 2001 at 07:07:25PM -0600, Scott Gerhardt wrote: > I was reading the information on foreign keys in the manual > http://www.mysql.com/doc/e/x/example-Foreign_keys.html and noticed > that there is no mention of locking the tables. > > It seems to me that using the example verbatim

Re: Foreign Key Info error in manual

2001-01-16 Thread Dan Nelson
In the last episode (Jan 16), Scott Gerhardt said: > I was reading the information on foreign keys in the manual > http://www.mysql.com/doc/e/x/example-Foreign_keys.html > and noticed that there is no mention of locking the tables. > > It seems to me that using the example verbatim could lead to