bekomme Fehlermeldung beim Erzeugen des PDF-Kataloges
1054 Unknown column 'p.products_id' in 'on clause'
in:
[select p.products_id, pd.products_name, pd.products_description, p.products_image, p.products_model, p.products_price, p.products_tax_class_id, IF(s.status, s.specials_new_products_price, NULL) as specials_new_products_price, p.products_date_added, m.manufacturers_name from zzzproducts p left join zzzmanufacturers m on p.manufacturers_id = m.manufacturers_id, zzzproducts_description pd left join zzzspecials s on p.products_id = s.products_id, zzzcategories c, zzzproducts_to_categories p2c where products_status = '1' and p.products_id = pd.products_id and pd.language_id = '1' and p.products_id = p2c.products_id and p2c.categories_id = c.categories_id and p2c.categories_id='1' order by p.products_date_added DESC, pd.products_name]
If you were entering information, press the BACK button in your browser and re-check the information you had entered to be sure you left no blank fields.
Das Problem wurde ja schon mehrfach beschrieben. Aber in allen Beiträgen, die ich hier zu diesem Thema gefunden hab wurde als Lösung angegeben von SQL5 zurück auf SQL4 umzusteigen.
Bei der stundenlangen Suche im Netz bin ich unter http://dev.mysql.com/doc/refman/5.0/en/join.html
auf den Hinweis gestossen, dass das Problem ab SQl 5.0.??? mit dem join-Befehl zusammen hängt :
Previously, the SELECT was legal due to the implicit grouping of t1,t2 as (t1,t2). Now the JOIN takes precedence, so the operands for the ON clause are t2 and t3. Because t1.i1 is not a column in either of the operands, the result is an Unknown column 't1.i1' in 'on clause' error. To allow the join to be processed, group the first two tables explicitly with parentheses so that the operands for the ON clause are (t1,t2) and t3:
SELECT * FROM (t1, t2) JOIN t3 ON (t1.i1 = t3.i3);
Alternatively, avoid the use of the comma operator and use JOIN instead:
SELECT * FROM t1 JOIN t2 JOIN t3 ON (t1.i1 = t3.i3);
This change also applies to statements that mix the comma operator with INNER JOIN, CROSS JOIN, LEFT JOIN, and RIGHT JOIN, all of which now have higher precedence than the comma operator.
Previously, the ON clause could refer to columns in tables named to its right. Now an ON clause can refer only to its operands.
Example:
CREATE TABLE t1 (i1 INT);
CREATE TABLE t2 (i2 INT);
CREATE TABLE t3 (i3 INT);
SELECT * FROM t1 JOIN t2 ON (i1 = i3) JOIN t3;
Previously, the SELECT statement was legal. Now the statement fails with an Unknown column 'i3' in 'on clause' error because i3 is a column in t3, which is not an operand of the ON clause. The statement should be rewritten as follows:
SELECT * FROM t1 JOIN t2 JOIN t3 ON (i1 = i3);
Leider bin ich absoluter SQL-Neuling. Wenn ich das richtig interpretiert hab müssen nur Klammern an den richtigen Stellen in der Abfrage gesetzt werden. Wer kennt sich mit SQL 5 aus und kann mir helfen?
1054 Unknown column 'p.products_id' in 'on clause'
in:
[select p.products_id, pd.products_name, pd.products_description, p.products_image, p.products_model, p.products_price, p.products_tax_class_id, IF(s.status, s.specials_new_products_price, NULL) as specials_new_products_price, p.products_date_added, m.manufacturers_name from zzzproducts p left join zzzmanufacturers m on p.manufacturers_id = m.manufacturers_id, zzzproducts_description pd left join zzzspecials s on p.products_id = s.products_id, zzzcategories c, zzzproducts_to_categories p2c where products_status = '1' and p.products_id = pd.products_id and pd.language_id = '1' and p.products_id = p2c.products_id and p2c.categories_id = c.categories_id and p2c.categories_id='1' order by p.products_date_added DESC, pd.products_name]
If you were entering information, press the BACK button in your browser and re-check the information you had entered to be sure you left no blank fields.
Das Problem wurde ja schon mehrfach beschrieben. Aber in allen Beiträgen, die ich hier zu diesem Thema gefunden hab wurde als Lösung angegeben von SQL5 zurück auf SQL4 umzusteigen.
Bei der stundenlangen Suche im Netz bin ich unter http://dev.mysql.com/doc/refman/5.0/en/join.html
auf den Hinweis gestossen, dass das Problem ab SQl 5.0.??? mit dem join-Befehl zusammen hängt :
Previously, the SELECT was legal due to the implicit grouping of t1,t2 as (t1,t2). Now the JOIN takes precedence, so the operands for the ON clause are t2 and t3. Because t1.i1 is not a column in either of the operands, the result is an Unknown column 't1.i1' in 'on clause' error. To allow the join to be processed, group the first two tables explicitly with parentheses so that the operands for the ON clause are (t1,t2) and t3:
SELECT * FROM (t1, t2) JOIN t3 ON (t1.i1 = t3.i3);
Alternatively, avoid the use of the comma operator and use JOIN instead:
SELECT * FROM t1 JOIN t2 JOIN t3 ON (t1.i1 = t3.i3);
This change also applies to statements that mix the comma operator with INNER JOIN, CROSS JOIN, LEFT JOIN, and RIGHT JOIN, all of which now have higher precedence than the comma operator.
Previously, the ON clause could refer to columns in tables named to its right. Now an ON clause can refer only to its operands.
Example:
CREATE TABLE t1 (i1 INT);
CREATE TABLE t2 (i2 INT);
CREATE TABLE t3 (i3 INT);
SELECT * FROM t1 JOIN t2 ON (i1 = i3) JOIN t3;
Previously, the SELECT statement was legal. Now the statement fails with an Unknown column 'i3' in 'on clause' error because i3 is a column in t3, which is not an operand of the ON clause. The statement should be rewritten as follows:
SELECT * FROM t1 JOIN t2 JOIN t3 ON (i1 = i3);
Leider bin ich absoluter SQL-Neuling. Wenn ich das richtig interpretiert hab müssen nur Klammern an den richtigen Stellen in der Abfrage gesetzt werden. Wer kennt sich mit SQL 5 aus und kann mir helfen?
Kommentar