Forums before death by AOL, social media and spammers... "We can't have nice things"
|    comp.databases.oracle    |    Overblown overpriced overengineered SHIT    |    2,288 messages    |
[   << oldest   |   < older   |   list   |   newer >   |   newest >>   ]
|    Message 1,962 of 2,288    |
|    GreyBeard to Ira Baxter    |
|    Re: Looking for authoritative reference     |
|    31 Dec 04 16:56:52    |
      XPost: comp.databases.oracle.tools, comp.databases.oracle.marketplace       From: Fuzzy.GreyBeard@gmail.com              On Fri, 31 Dec 2004 09:51:32 -0600, Ira Baxter wrote:              > Hi. We are working on tools to process PL/SQL code.       > What we need are precise details on the full PL/SQL syntax.       >       > We have the Oracle 9/10 documentation, but it seems       > a little fuzzy on the details. As an example, we're unclear       > on whether ANSI 99 JOIN syntax is allowed or not.       > (Any direct answers on this topic would be appreciated).       >       > Is there a document which precisely defines the PL/SQL       > syntax?              With all due respect,              One could get the impression you are unclear about PL/SQL in general.       Your comment about the ANSI 99 Join syntax indicates that you do not       separate PL/SQL from SQL and therefore may not realize that PL/SQL does       perform any joins at all. Instead, it passes such requests to the SQL       processor, the syntax for which is documented in the SQL Reference       Manual.              I also hope you realize that the combination of SQL and PL/SQL allows a       developer to 'extend' SQL by adding new functions that can be used in       various places, extending the the SELECT clause, the inline view,       the WITH clause, the WHERE clause, etc. You may find this a challenge in       creating your tools as it implies you may need to catalog all stored       functions as well.              The actual PL/SQL language is documented fairly well in the "PL/SQL User's       Guide and Reference", which includes use, discussion of the above       concept, syntax and examples. Please indicate what is 'fuzzy' about       details such as the following syntax definition (from the manual) for the       CASE statement:                      searched_case_statement ::=               [ < |
[   << oldest   |   < older   |   list   |   newer >   |   newest >>   ]
(c) 1994, bbs@darkrealms.ca