mysql@lists.mysql.com
Objet : Re: mysql old 4.* query fails on 5.*
> Anyone know whats wrong here?
Try as
...
>From (Klienter AS K, Tid As Td, Personal AS P)
JOIN Uppdrag AS U ON K.Klient_ID = U.Klient_ID
...
or
...
>From Tid As Td, Personal AS P, Klienter AS K
JOIN Uppdrag AS U
> Anyone know whats wrong here?
Try as
...
>From (Klienter AS K, Tid As Td, Personal AS P)
JOIN Uppdrag AS U ON K.Klient_ID = U.Klient_ID
...
or
...
>From Tid As Td, Personal AS P, Klienter AS K
JOIN Uppdrag AS U ON K.Klient_ID = U.Klient_ID
...
This is the problem I had in one of my queries
Hi,
consiglieri wrote:
Hi
I have upgraded to 5.0.22 and after a while I discovered that the
following query no longer works.. it fails claiming " Unknown column
'K.Klient_ID' in 'on clause' " which seems entirely wrong.
The query is as follows
select Td.Datum, Td.Text AS Action, Td.Enhet AS
Hi
I have upgraded to 5.0.22 and after a while I discovered that the
following query no longer works.. it fails claiming " Unknown column
'K.Klient_ID' in 'on clause' " which seems entirely wrong.
The query is as follows
select Td.Datum, Td.Text AS Action, Td.Enhet AS Tid, P.Fornamn AS Person
be aware... linux/unix table names are case sensitive. if you're using Win32 MySQL
on your system, the query might work, but on the ISP side, if it's a *NIX system...
you must have the correct capitalization.
moreover, if any of your variables contain a single quote character ( ' ), it will
scre
Hi everyone!
Are there any limitations on update queries, like on how many fields one
can update at the same time?
The first update query works just fine, the second does not work at all:
working :
" update memberscopy set password='$password' where name =
'$f_name' and surname ='$f_
Maciek,
>Hi,
>
>Is this correct for MySQL to increment the auto_increment counter if the
>INSERT query fails? For example:
>
>mysql> CREATE TABLE test ( i INT NOT NULL AUTO_INCREMENT, c CHAR(16) NOT
>NULL, PRIMARY KEY(i), UNIQUE(c)) type=InnoDB;
>Query OK, 0 rows a
Maciek,
>Hi,
>
>Is this correct for MySQL to increment the auto_increment counter if the
>INSERT query fails? For example:
>
>mysql> CREATE TABLE test ( i INT NOT NULL AUTO_INCREMENT, c CHAR(16) NOT
>NULL, PRIMARY KEY(i), UNIQUE(c)) type=InnoDB;
>Query OK, 0 rows a
Maciek,
>Hi,
>
>Is this correct for MySQL to increment the auto_increment counter if the
>INSERT query fails? For example:
>
>mysql> CREATE TABLE test ( i INT NOT NULL AUTO_INCREMENT, c CHAR(16) NOT
>NULL, PRIMARY KEY(i), UNIQUE(c)) type=InnoDB;
>Query OK, 0 rows a
Maciek,
>Hi,
>
>Is this correct for MySQL to increment the auto_increment counter if the
>INSERT query fails? For example:
>
>mysql> CREATE TABLE test ( i INT NOT NULL AUTO_INCREMENT, c CHAR(16) NOT
>NULL, PRIMARY KEY(i), UNIQUE(c)) type=InnoDB;
>Query OK, 0 rows a
Maciek,
>Hi,
>
>Is this correct for MySQL to increment the auto_increment counter if the
>INSERT query fails? For example:
>
>mysql> CREATE TABLE test ( i INT NOT NULL AUTO_INCREMENT, c CHAR(16) NOT
>NULL, PRIMARY KEY(i), UNIQUE(c)) type=InnoDB;
>Query OK, 0 rows a
Maciek,
>Hi,
>
>Is this correct for MySQL to increment the auto_increment counter if the
>INSERT query fails? For example:
>
>mysql> CREATE TABLE test ( i INT NOT NULL AUTO_INCREMENT, c CHAR(16) NOT
>NULL, PRIMARY KEY(i), UNIQUE(c)) type=InnoDB;
>Query OK, 0 rows a
Hi,
Is this correct for MySQL to increment the auto_increment counter if the
INSERT query fails? For example:
mysql> CREATE TABLE test ( i INT NOT NULL AUTO_INCREMENT, c CHAR(16) NOT
NULL, PRIMARY KEY(i), UNIQUE(c)) type=InnoDB;
Query OK, 0 rows affected (0.25 sec)
mysql> INSERT INT
> CREATE TABLE MSJOURNL (ACCT INT(3),
> DESC CHAR(29),
> DTE DATE)
>
> This query fails when MySQL encouters DESC. Changing DESC to DESCRIP
causes
> the query to work. I'm wondering if filtering for the reserved word
DESCRIBE
> causes DESC not to be legal for use in fiel
On Sun, Aug 26, 2001 at 01:58:23PM -0700, Bill Angus wrote:
> CREATE TABLE MSJOURNL (ACCT INT(3),
> DESC CHAR(29),
> DTE DATE)
>
> This query fails when MySQL encouters DESC. Changing DESC to DESCRIP
> causes the query to work. I'm wondering if filtering for the
> res
Hi !!
)-Original Message-
)From: Bill Angus [mailto:[EMAIL PROTECTED]]
)Sent: Sunday, August 26, 2001 1:58 PM
)To: [EMAIL PROTECTED]
)Subject: Query fails
)
)
)CREATE TABLE MSJOURNL (ACCT INT(3),
)DESC CHAR(29),
)DTE DATE)
)
)This query fails when MySQL encouters DESC. Changing DESC to
CREATE TABLE MSJOURNL (ACCT INT(3),
DESC CHAR(29),
DTE DATE)
This query fails when MySQL encouters DESC. Changing DESC to DESCRIP causes
the query to work. I'm wondering if filtering for the reserved word DESCRIBE
causes DESC not to be legal for use in field
17 matches
Mail list logo
