Skip navigation.

Gerd Volberg

Syndicate content
Gerd Volberghttp://www.blogger.com/profile/00634342057996329457noreply@blogger.comBlogger77125
Updated: 54 min 52 sec ago

Blogging via Google Wave - First Test through email

Mon, 2009-10-19 05:49
Google wave is cool. Each day I find new things in this platform.

And now is the time to test the connectivity between google wave and my blog.

In this first test I write an automated email to the blogger-account. And the second test afterwards is from within the wave

I need luck
Gerd

The presentation for the DOAG conference 2009 is finished

Tue, 2009-09-15 10:03
The title is: "Shout out: Oracle Designer vs. SQL Developer Data Modeler".

I'll demonstrate in the presentation the advantages and disadvantages of both tools. I base the demonstration on an EMP / DEPT example, which I design live.

Chapters of the white paper are

- Domains
- ER-Design
- Transfer ER to DataModel
- Data Modeling
- Generating DDL-Scripts
- Reverse Engineering
- Guaranteed Future

The day after the presentation I'll upload the paper to my download-portal on google-code

Gerd

Forms Debugger - hidden Feature

Mon, 2009-08-31 00:18
The Forms 10g debugger is much better than the Forms 6i debugger. He is completly new written and has the ability to debug remote. So you can look into a running session of an user and search for errors. This is in the new web-environments a powerful method to find problems.

And that's only one aspect of the new debugger.


The debugger works in two different modes: The stop-mode is well-known, because you can use there all functions of the debugger. He is active, while you investigate the code. You can work in this work, through a breakpoint e.g.


The run-mode is the other one. He can be found only, while the form is running in the foreground.


And at that point you can press the break-button, which is one of the most interesting features in the debugger. It creates a breakpoint dynamically in the next line of code, which will be executed.

So, if you press the button, nothing happens. If you then return from the Forms Builder back to the runform, the next event in the form starts the debugging-process. And then the debugger shows you the first line of code in that trigger, which will be executed next. So you don't have to think to much, where to set breakpoints and so on... just use the break-button.

That's my tip of the day
Gerd