Skip to main content

Quick Guide to Some Sources for Naming Conventions for Oracle Database Development

I occasionally am asked about naming conventions for PL/SQL program units.

I did publish a document back in 2009 (link below), but there are also other sources for naming conventions from others, offering different ideas and excellent motivation for standardizing the way you write your code. I have collected links to them here.

The most important thing about naming conventions is BE CONSISTENT.

PL/SQL Naming Conventions and Coding Standards - Steven Feuerstein 2009

Coding Standards for SQL and PL/SQL - William Robertson

ORACLE-BASE / Tim Hall / Oracle Naming Conventions

Trivadis PL/SQL and SQL Coding Guidelines Version 2.0

Ask Tom on Naming Conventions

 PL/SQL and SQL naming conventions

Oracle SQL and PL/SQL Coding Standards – Cat Herding for Dummies

Slideshare Presentation on PL/SQL Coding Conventions

Labels:

Comments

  1. SanthoshOctober 24, 2016 at 10:51 AM

    Thanks Steven for the post.

    The first link which you have published back in 2009,is not working and giving "404 Not Found!" error.

    Could you please check.

    Thanks
    Santhosh

    ReplyDelete
  2. Steven FeuersteinOctober 24, 2016 at 11:00 AM

    Apologies. That SHOULD have worked, but I should have tested it. I have uploaded the document to OTN, and the link now reflects that.

    ReplyDelete
    Replies
    1. SanthoshOctober 24, 2016 at 11:02 AM

      Thanks for the quick action, will check it now.

      Thanks again Steven.

      Delete
  3. DanielOctober 26, 2016 at 12:52 AM

    "The most important factor in a name is that it concisely (not that we have any choice about that with a limit of 30 characters!) " What about 12.2 :=)

    ReplyDelete
    Replies
    1. Steven FeuersteinOctober 26, 2016 at 5:24 AM

      You are right, Daniel. Now we have choice AND responsibility. Of course, a name can be concise when using 50 characters. It depends on what you are trying or need to say - or you are using German. :-)

      Delete
    2. DanielOctober 26, 2016 at 6:59 AM

      Responsibility was the word. The total length of an identifier, schema.tabel.column might be veeeery long. :)
      Gonna be interesting to see how people use this "feature"

      Delete
    3. Steven FeuersteinOctober 26, 2016 at 11:15 AM

      I expect that it will be used as follows: I type a name, it's kinda long - 32, 35, maybe 40 characters - but the compiler no longer complains so I use it.

      Delete

Post a Comment

Popular posts from this blog

Why DBMS_OUTPUT.PUT_LINE should not be in your application code

A database developer recently came across my  Bulletproof PL/SQL  presentation, which includes this slide. That first item in the list caught his attention: Never put calls to DBMS_OUTPUT.PUT_LINE in your application code. So he sent me an email asking why I would say that. Well, I suppose that is the problem with publishing slide decks. All the explanatory verbiage is missing. I suppose maybe I should do a video. :-) But in the meantime, allow me to explain. First, what does DBMS_OUTPUT.PUT_LINE do? It writes text out to a buffer, and when your current PL/SQL block terminates, the buffer is displayed on your screen. [Note: there can be more to it than that. For example, you could in your own code call DBMS_OUTPUT.GET_LINE(S) to get the contents of the buffer and do something with it, but I will keep things simple right now.] Second, if I am telling you not to use this built-in, how could text from your program be displayed on your screen? Not without a lot o...
4 comments
Read more

How to Pick the Limit for BULK COLLECT

This question rolled into my In Box today: In the case of using the LIMIT clause of BULK COLLECT, how do we decide what value to use for the limit? First I give the quick answer, then I provide support for that answer Quick Answer Start with 100. That's the default (and only) setting for cursor FOR loop optimizations. It offers a sweet spot of improved performance over row-by-row and not-too-much PGA memory consumption. Test to see if that's fast enough (likely will be for many cases). If not, try higher values until you reach the performance level you need - and you are not consuming too much PGA memory.  Don't hard-code the limit value: make it a parameter to your subprogram or a constant in a package specification. Don't put anything in the collection you don't need. [from Giulio Dottorini] Remember: each session that runs this code will use that amount of memory. Background When you use BULK COLLECT, you retrieve more than row with each fetch, ...
4 comments
Read more

Table Functions, Part 1: Introduction and Exploration

Please do feel encouraged to read this and my other posts on table functions, but you will learn much more about table functions by taking my Get Started with PL/SQL Table Functions class at the Oracle Dev Gym. Videos, tutorials and quizzes - then print a certificate when you are done! Table functions - functions that can be called in the FROM clause of a query from inside the TABLE operator - are fascinating and incredibly helpful constructs. So I've decided to write a series of blog posts on them: how to build them, how to use them, issues you might run into. Of course, I am not the first to do so. I encourage to check out the  documentation , as well as excellent posts from Adrian Billington (search for "table functions") and Tim Hall . Adrian and Tim mostly focus on pipelined table functions, a specialized variant of table functions designed to improve performance and reduce PGA consumption. I will take a look at pipelined table functions in the latter part...
31 comments
Read more