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
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 -
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()
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
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
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
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: (
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
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
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
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 loss of
referencial integrity if INSERTS did not occur in seq
11 matches
Mail list logo
