Changing preferences by executing a report in SQL Developer

I've upgraded from SQL Developer 1 (version to 1.1 (version One of mine favorite features in SQL Developer is the drill down capability within Reports. Just add three columns to your query and SQL Developer knows which database object properties to display if you double click a row in the report output. This feature is explained in detail in the article Making the Most of Oracle SQL Developer Reports by Lewis Cunningham. However Oracle changed the behavior a little...

Let's illustrate this behavior with an example. Execute the report All Objects for owner SCOTT and leave tables empty. The left picture below shows the result and after a double clicking on the EMP row.

SQL Developer 1.0 all objects reportDouble click the EMP row and SQL Developer shows the properties of the EMP table.

SQL Developer 1.0 EMP properties
In SQL Developer 1.1 this behavior has changed. If you double click a row a button with the text ... appears. Another new feature is changing the order by of a column by double clicking on the column header.

SQL Developer 1.1 all objects report
Click the button and in a new window you can change the Line terminator value.

SQL Developer 1.1 Edit line terminator value
But I don't want to change line terminator value, I want to see the properties of the EMP table. After some trial and error I found the solution: right click on the EMP row and a list with options is shown. One of those options is Go To EMP.

SQL Developer 1.1 all objects report context menu
The right click feature was already available in version 1, but it only showed the Export Data item in the list.

However, I do not understand why you can set the line terminator value at column level. If you try to change the line terminator value by clicking the change button SQL Developer shows the Preferences window where you can set the line terminator value at once for all reports (forget the shortcut Alt-Tools Preferences :-)).


Ajax and the end of the internet

While surfing on the internet I found some links concerning Ajax on the IBM website. I tried to tag them with del.icio.us. Unfortunately a window popped up telling me

You've reached the end of the internet

We're in the midst of a scheduled upgrade which will take no more than a couple of hours. Come back after 2 pm (Pacific) today and you will see the del.icio.us you've come to know and love.

In order to save my links, I added then to my blog :-)

You will find links here to the first 8 articles in the serie Mastering Ajax written by Brett McLaughlin. Perform this query to list all articles in this serie.

  • Mastering Ajax, Part 1: Introduction to Ajax
    Ajax, which consists of HTML, JavaScript, DHTML, and DOM, is an outstanding approach that helps you transform clunky Web interfaces into interactive Ajax applications. The author, an Ajax expert, demonstrates how these technologies work together -- from an overview to a detailed look -- to make extremely efficient Web development an easy reality. He also unveils the central concepts of Ajax, including the XMLHttpRequest object.

  • Mastering Ajax, Part 2: Make asynchronous requests with JavaScript and Ajax
    Most Web applications use a request/response model that gets an entire HTML page from the server. The result is a back-and-forth that usually involves clicking a button, waiting for the server, clicking another button, and then waiting some more. With Ajax and the XMLHttpRequest object, you can use a request/response model that never leaves users waiting for a server to respond. In this article, Brett McLaughlin shows you how to create XMLHttpRequest instances in a cross-browser way, construct and send requests, and respond to the server.

  • Mastering Ajax, Part 3: Advanced requests and responses in Ajax
    For many Web developers, making simple requests and receiving simple responses is all they'll ever need, but for developers who want to master Ajax, a complete understanding of HTTP status codes, ready states, and the XMLHttpRequest object is required. In this article, Brett McLaughlin will show you the different status codes and demonstrate how browsers handle each and he will showcase the lesser-used HTTP requests that you can make with Ajax.

  • Mastering Ajax, Part 4: Exploiting DOM for Web response
    The great divide between programmers (who work with back-end applications) and Web programmers (who spend their time writing HTML, CSS, and JavaScript) is long standing. However, the Document Object Model (DOM) bridges the chasm and makes working with both XML on the back end and HTML on the front end possible and an effective tool. In this article, Brett McLaughlin introduces the Document Object Model, explains its use in Web pages, and starts to explore its usage from JavaScript.

  • Mastering Ajax, Part 5: Manipulate the DOM
    Last month Brett introduced the Document Object Model, whose elements work behind the scenes to define your Web pages. This month he dives even deeper into the DOM. Learn how to create, remove, and change the parts of a DOM tree, and take the next step toward updating your Web pages on the fly!

  • Mastering Ajax, Part 6: Build DOM-based Web applications
    Continue to explore how DOM programming fits into interactive Ajax applications as Brett McLaughlin completes his trilogy of articles on DOM programming with a DOM application in practice.

  • Mastering Ajax, Part 7: Using XML in requests and responses
    Brett McLaughlin demonstrates how you can use XML as the data format for sending asynchronous requests.

  • Mastering Ajax, Part 8: Using XML in requests and responses
    In the last article of the series,you saw how your Ajax apps can format requests to a server in XML. You also saw why, in most cases, that isn't a good idea. This article focuses on something that often is a good idea: returning XML responses to a client.