Is this a bug in 7.1?

Is this a bug in 7.1?

Post by Oliver Elphic » Wed, 14 Mar 2001 20:58:01



Is this a bug or missing feature in 7.1? or have I got the SQL
wrong?

bray=# SELECT DISTINCT p.id, p.name, a.town
bray-#   FROM (
bray(#         SELECT id, name
bray(#           FROM customer
bray(#         UNION
bray(#         SELECT id, name
bray(#           FROM supplier
bray(#        ) AS p
bray-#        LEFT OUTER JOIN address AS a
bray-#          ON p.address = a.id
bray-#   WHERE p.id = '22002';
ERROR:  function applied to tuple is not supported for subSELECTs

What does the error message mean?  I can't see where a function
is involved.

--

Isle of Wight                              http://www.lfix.co.uk/oliver
PGP: 1024R/32B8FAA1: 97 EA 1D 47 72 3F 28 47  6B 7E 39 CC 56 E4 C1 47
GPG: 1024D/3E1D0C1C: CA12 09E0 E8D5 8870 5839  932A 614D 4C34 3E1D 0C1C
                 ========================================
     "Who is like Thee among the gods, O Lord? Who is like
      Thee, majestic in holiness, awesome in praises,
      working wonders?"
                              Exodus 15:11

---------------------------(end of broadcast)---------------------------
TIP 5: Have you checked our extensive FAQ?

http://www.postgresql.org/users-lounge/docs/faq.html

 
 
 

Is this a bug in 7.1?

Post by Tom La » Thu, 15 Mar 2001 01:16:00



> bray=# SELECT DISTINCT p.id, p.name, a.town
> bray-#   FROM (
> bray(#         SELECT id, name
> bray(#           FROM customer
> bray(#         UNION
> bray(#         SELECT id, name
> bray(#           FROM supplier
> bray(#        ) AS p
> bray-#        LEFT OUTER JOIN address AS a
> bray-#          ON p.address = a.id
> bray-#   WHERE p.id = '22002';
> ERROR:  function applied to tuple is not supported for subSELECTs
> What does the error message mean?

table.functionname is an ancient PostQUEL notation for functions that
take whole tuples --- think "address(p)" and you'll have a better idea
what the parser is seeing here.

This notation is something we're probably going to have to retire soon,
since I doubt it will play well with schema notation (too hard to guess
what foo.bar.baz means).  I doubt anyone but the regression tests still
use the PostQUEL notation for function calls anyway.

                        regards, tom lane

---------------------------(end of broadcast)---------------------------
TIP 6: Have you searched our list archives?

http://www.postgresql.org/search.mpl

 
 
 

1. 7.1: to_char() bug fix

Thanks.  Applied.

Content-Description:

[ application/x-gzip is not supported, skipping... ]

--
  Bruce Momjian                        |  http://candle.pha.pa.us

  +  If your life is a hard drive,     |  830 Blythe Avenue
  +  Christ can be your backup.        |  Drexel Hill, Pennsylvania 19026

2. Select content from a column of type 'long'

3. PG 7.1 pre-beta bug ...

4. binding to a query-based DE recordset

5. DEC Alpha, OL 7.1 bug

6. Conditional RecordSource

7. Timestamp bug WAS: Problem with restore on upgrading to 7.1

8. 7.1 odbc bug & patch

9. Bug in DB2 7.1 FP7?

10. PG 7.1 pre-beta bug ...

11. Is this a bug in 7.1?

12. Postgres SQL 7.1 a thank you and a possible bug