WITH query_name and ODBC

Question

I'm playing around with the WITH query_name clause as in:
WITH FOO AS (SELECT 123 AS BAR FROM DUAL) SELECT * FROM FOO
I'm facing a curious issue. This query runs fine in SQL Developer and it runs fine from PHP if I use the OCI8 functions. However, it doesn't run from PHP using ODBC functions: odbc_exec() gives no error but all function calls that fetch rows, such as odbc_fetch_into(), generate a warning ("No tuples available at this result index") and no rows or columns.
But I face no problem if I enclose everything in a plain SELECT:
SELECT * FROM (
     WITH FOO AS (SELECT 123 AS BAR FROM DUAL) SELECT * FROM FOO
Does the WITH clause convert a query into something that needs special handling? Is it an issue with the ODBC driver?
I haven't been able to find anything relevant in Google, apart from learning that it seems to be an ODBC issue and not Oracle specific.
I connect to Oracle Database 10g Enterprise Edition Release 10.1.0.2.0 from Windows Server 2003 using PHP/5.2.6. (No access to Metalink or
Oracle support, though, it's a customer site.)

Answer 1

Actually, Dominic Brooks helped me with that a while back. You don't want the enclosing parentheses because it can throw odd errors, even in SQL*Plus. It's in this old post of mine here:
http://blog.mclaughlinsoftware.com/2008/10/19/inline-views-table-fabrication-and-the-with-clause/
As to differences on the parser between ODBC and OCI8, I'm not certain but believe that they use the same parser. To the best of my knowledge there are only two parsers (actually three but the other is old and only used by the Applications Division for their adpatch utility). There's the SQL parser and the PL/SQL parser. However, if somebody knows more, please chime in with the details.