Re: Code Review Process
- From: Niall Litchfield <niall.litchfield@xxxxxxxxx>
- To: malakshinovss@xxxxxxxxx
- Date: Fri, 8 Feb 2013 12:01:15 +0000
If you haven't read
http://www.toadworld.com/Portals/0/stevenf/Naming%20Conventions%20and%20Coding%20Standards.pdfthen
you really should. I'm not sure that I entirely agree with Steven's
recommendations, but they certainly cover the areas of concern.
On Fri, Feb 8, 2013 at 10:47 AM, Sayan Sergeevich Malakshinov <
malakshinovss@xxxxxxxxx> wrote:
> Hi all!
> I am interested in this topic too(except performance questions, because i
> monitor it on production and on performance stress testing).
> Sometimes it is very hard to read pl/sql code written by different teams
> (or, even worse, by sql generators like hibernate).
> Do anybody have same conventions for PL/SQL and SQL or db objects naming
> conventions?
> Or maybe set of restrictions/best practices for developers like 'do not do
> ...'?
> Could anybody share own code conventions/standards for oracle db?
> For example as java developer in past, i know sun's(oracle) code
> convention for java -
> http://www.oracle.com/technetwork/java/codeconv-138413.html
> In addition to parsing code in commit-hooks, we can do automatic check
> some code rules through pl/scope, and naming rules through data dictionary
> .
>
>
> Best regards,
> Sayan Malakshinov
> Performance tuning engineer
> http://orasql.org
>
> --
> //www.freelists.org/webpage/oracle-l
>
>
>
--
Niall Litchfield
Oracle DBA
http://www.orawin.info
--
//www.freelists.org/webpage/oracle-l
Other related posts:
