quely identify each row in the table, it
should be made the primary key.
George Sexton
MH Software, Inc.
http://www.mhsoftware.com/
Voice: 303 438 9585
> -Original Message-
> From: Asad Habib [mailto:[EMAIL PROTECTED]
> Sent: Wednesday, June 15, 2005 5:19 AM
> To: Stefan
> -Original Message-
> From: Jay Blanchard [mailto:[EMAIL PROTECTED]
> Sent: Thursday, June 09, 2005 10:34 AM
> To: George Sexton; mysql@lists.mysql.com
> Subject: RE: Seriously.. When are we going to get subqueries?!
>
> [snip]
> > 1. Join the
> -Original Message-
> From: Jay Blanchard [mailto:[EMAIL PROTECTED]
> Sent: Thursday, June 09, 2005 8:30 AM
> To: George Sexton
> Cc: mysql@lists.mysql.com
> Subject: RE: Seriously.. When are we going to get subqueries?!
>
> If you are
> not pleased with
upport two
columns with default current_timestamp. Additionally, it looks like if you
default to current_timestamp then any time the record is modified, that
value is changed.
While tinker-toys were wildly popular (I had them), they are wholly unsuited
for large scale building projects.
George
lowercase setting? I wouldn't have
authority to change the setting in a hosted environment.
I have to say, MySQL still looks like a tinker-toy to me.
George Sexton
MH Software, Inc.
http://www.mhsoftware.com/
Voice: 303 438 9585
> -Original Message-
> From: Jay Blanchard [ma
g to control this issue. This
is really ridiculous. The SQL Standard says that identifiers are not case
sensitive. My application is probably OK, but this is just ridiculous. Even
if I fix my App, I'll have to verify every sql statement under MySQL to make
sure that it works with it.
Ge
