Databases
StackOverflow2013
Postsdbo
PO
 

Note that there are some explanatory texts on larger screens.

plurals
  1. PO
    primarykey
    data
    text
    <p><strong>1:</strong> The most important thing to understand about PL/SQL is why you don't want to be a PL/SQL Developer.</p> <p>To get the most out of your database you need to use declarative programming with sets, also known as SQL. PL/SQL is procedural programming with rows. If you only use SQL your code will be simpler and usually about an order of magnitude faster.</p> <p>Your time is much better spent learning about Oracle and SQL concepts first, and then PL/SQL. You'll probably be better off as an Oracle Developer who just happens to write some PL/SQL.</p> <p><strong>2:</strong> Almost every good Oracle blog is by someone who is a member of the <a href="http://www.oaktable.net/members" rel="nofollow">OakTable</a>. But you won't find a lot of PL/SQL there because PL/SQL is not very interesting. I'm not trying to rant about PL/SQL, I think it's a fine language, but it's massively over-used. 90% of all PL/SQL code should probably be re-written in either SQL or Java/C#/etc.</p> <p>BUT... before you start looking at blogs or Googling you absolutely need to become familiar with a few books from the Oracle documentation library.</p> <ul> <li><a href="http://download.oracle.com/docs/cd/B19306_01/server.102/b14220/toc.htm" rel="nofollow">Concepts</a></li> <li><a href="http://download.oracle.com/docs/cd/B19306_01/server.102/b14200/toc.htm" rel="nofollow">SQL Reference</a> </li> <li><a href="http://download.oracle.com/docs/cd/B19306_01/appdev.102/b14261/toc.htm" rel="nofollow">PL/SQL User's Guide and Reference</a></li> <li><a href="http://download.oracle.com/docs/cd/B19306_01/appdev.102/b14258/toc.htm" rel="nofollow">PL/SQL Packages and Types Reference</a> (this one is huge and is mostly weird stuff nobody uses, but there's also some really important stuff in there)</li> </ul> <p>You need to at least be familiar with the structure of those books, especially the SQL and PL/SQL reference, so you can look up things later. Although they are large and complicated they are also extremely thorough and accurate. The syntax diagrams alone will save you many hours of Googling.</p>
    singulars
    1. This table or related slice is empty.
    1. POInfo Needed: What are some of the best PL/SQL Blogs to follow?
      singulars
      1. PTQuestion
    1. PTAnswer
    1. This table or related slice is empty.
    1. USJon Heller
    plurals
    1. This table or related slice is empty.
    1. This table or related slice is empty.
    1. This table or related slice is empty.
    1. This table or related slice is empty.
    1. VO
      singulars
      1. PO
      1. This table or related slice is empty.
      1. VTDownMod
    2. VO
      singulars
      1. PO
      1. This table or related slice is empty.
      1. VTUpMod
    1. COnot sure why this was downvoted. As a PL/SQL developer I agree with every line, except for the idea of rewriting PL/SQL in Java/C#/etc... :)
      singulars
      1. PO
      1. USJeffrey Kemp
    2. COI dont like perspective where people try to make everything inside SQL. The maintenance is horrible and usually logic is developed further and further and the result is definitely against every good programming practice.
      singulars
      1. PO
      1. USJokke Heikkilä
    3. CO@Jeff: and that line is exactly the reason why a downvote had crossed my mind as well. The other lines are pretty sensible so I'll leave it untouched.
      singulars
      1. PO
      1. USRob van Wijk
 

Querying!

 
Guidance
A row detail

Detail views are divided into sections. All the information in the data section comes from columns in the selected row. The other sections display data from other, related rows.

Related data can be related in a to-one or a to-many fashion. Captions of data related in a to-many fashion link to a list view showing a filtered view of the table.

Try moving around until you find a non-empty to-many entry and click on the label to get to one. You can move back to the root by clicking on the database name in the header.

SQuiL has stopped working due to an internal error.

If you are curious you may find further information in the browser console, which is accessible through the devtools (F12).

Reload