A Wetpaint Site

Sign in to Wetpaint

Sign in or

PL/SQL Best Practices

Page Versions

Key: additions deletions

Showing 6 pages

	Date/Time	Made By	Edit Note	Type	Scope
	May 3 2008, 2:53 AM EDT	tomcox		edit
Change: There were only format changes (bold, italics, etc.) in this version. See this version for details. (Word count: 308)
	May 3 2008, 2:52 AM EDT	tomcox	more on naming and coding stds	edit	110 words added 2 words deleted
Change: The purpose of a coding standard, of course, is not to make your code "better" in some abstract way (thought it might), but rather to View changes from previous version. (Word count: 308)
	May 3 2008, 2:49 AM EDT	tomcox	more details on a naming standard	edit	108 words added
Change: When multiple programmers on large projects use the same standard, their names for similar things will tend to converge - thus, when two people are View changes from previous version. (Word count: 201)
	Dec 7 2007, 1:43 AM EST	jonah.harris	SF Airport Update	edit	86 words added 24 words deleted
Change: As in any programming language, good practices help to ensure that code is developed properly and in a maintainable fashion; PL/SQL is no exception. Developing readable, understandable, and maintainable PL/SQL requires that developer take into account several basic concepts for good development. Several of the delay.common I'mbest in View changes from previous version. (Word count: 94)
	Dec 5 2007, 3:53 PM EST	jonah.harris	Temp edit.	edit	28 words added
Change: Sorry for the delay. I'm in SF performing a training right now and will post this soon. As always, if you want to add anything here, feel free. View changes from previous version. (Word count: 29)
	Dec 1 2007, 3:50 PM EST	jonah.harris		create	No content added or deleted.
Change: Created by jonah.harris Dec 1 2007, 3:50 PM EST for: no reason given

JavaScript must be enabled in order for you to contribute to this site.
To start contributing, enable JavaScript by changing your browser options, then try again.

Home