Index: openacs-4/packages/acs-core-docs/www/eng-standards-plsql.html =================================================================== RCS file: /usr/local/cvsroot/openacs-4/packages/acs-core-docs/www/eng-standards-plsql.html,v diff -u -r1.49 -r1.50 --- openacs-4/packages/acs-core-docs/www/eng-standards-plsql.html 27 Oct 2014 16:39:18 -0000 1.49 +++ openacs-4/packages/acs-core-docs/www/eng-standards-plsql.html 7 Aug 2017 23:47:49 -0000 1.50 @@ -1,5 +1,5 @@ -PL/SQL Standards

PL/SQL Standards

+PL/SQL Standards

PL/SQL Standards

By Richard Li and Yon Feldman

OpenACS docs are written by the named authors, and may be edited @@ -26,7 +26,7 @@

Code

  1. Encapsulation of related fuctionality is key to maintainability and upgradeability of our software. Try to bundle your code into - packages + packages whenever possible. This will make upgrading, bug fixing, and customizing, among other things, a possibility.

  2. @@ -81,7 +81,7 @@

    - To achieve this we must fully qualify arguements passed into + To achieve this we must fully qualify arguments passed into procedures or functions when using them inside a SQL statement. This will get rid of any ambiguities in your code, i.e. it will tell the parser when you want the value of the column @@ -139,7 +139,7 @@

    takes the optional argument object_id. Do this to allow people to use the same API call when they are doing double - click protection, that is, tehy have already gotten an + click protection, that is, they have already gotten an object_id and now they want to create the object with that object_id.

Style

@@ -152,4 +152,4 @@ as possible to all source code readers.

  • Lowercase everything, with the exception of %TYPE and %ROWTYPE. -

  • ($Id$)
    View comments on this page at openacs.org
    +

    ($Id$)