Skip to main content

Want to be a presenter at the Oracle Developers conference?

By

Developers and architects attend Kaleidoscope to find out how to use the new technologies to make their jobs easier. Your expertise and experience are key to our participants getting their questions answered. Click here to submit your abstract to speak at the developer event of the year.

ODTUG Kaleidoscope 2010 at the Marriott Wardman Park Hotel in Washington, D.C. is the conference for Oracle developers and architects. Kaleidoscope has it all - more than 150 technical sessions, day-long symposia, hands-on training, chats with participants and speakers, and even a community service project.

So far the "offical" advertisement. My personal opinion is that Kaleidscope is the place to be for Oracle Developers. Just because it is at a 'somewhat' smaller scale than - for instance - Oracle Open World (last year there where around 700 attendees), you can speak to whoever is there (and 'everyone' is!). Also the content of the presentations is very good. But don't let that discourage you from entering an abstract! If you have a good subject and a good abstract (and a catchy title could help..) you definitely will make a chance!

Hope to see you there (if my abstract gets accepted....).

Comments

Anonymous said…
Hi Roel,
Do you know if presenters get thier conference fees waived?
Thanks,
John
3:38 am
Roel said…
Hi John
Yes they do! So that's another good reason to submit an abstract...
Roel
7:21 am
Post a Comment

Popular posts from this blog

How to create neatly formatted Excel documents using PL/SQL?

By
If there is a requirement to produce output from an application into Excel, you would probably create a CSV (Comma Separated File) with the data and start Excel to show the data - at least that's what I did...until now. The drawback of this solution is that you could only produce data and no nice layout. But Excel is also capable of opening HTML-files and using this you could create Excel files with data and magnificent layout! Let me give an example: 1. Create a procedure to show the data in formatted in an HTML table. CREATE OR REPLACE PROCEDURE display_emp_list IS v_emp_count NUMBER(5); v_empno NUMBER(8); v_ename VARCHAR2(50); v_job emp.job%TYPE; v_sal emp.sal%TYPE; v_bg_color VARCHAR2(10) := ''; CURSOR c_emp IS SELECT empno, initcap(ename), job, sal FROM emp ORDER BY ename; BEGIN SELECT COUNT(*) INTO v_emp_count FROM emp; owa_util.mime_header('application/ms-excel', FALSE); htp.p('Content...
21 comments
Read more

Refresh selected row(s) in an Interactive Grid

By
In my previous post I blogged about pushing changed rows from the dabatase into an Interactive Grid . The use case I'll cover right here is probably more common - and therefore more useful! Until we had the IG, we showed the data in a report (Interactive or Classic). Changes to the data where made by popping up a form page, making changes, saving and refreshing the report upon closing the dialog. Or by clicking an icon / button / link in your report that makes some changes to the data (like changing a status) and ... refresh the report.  That all works fine, but the downsides are: The whole dataset is returned from the server to the client - again and again. And if your pagination size is large, that does lead to more and more network traffic, more interpretation by the browser and more waiting time for the end user. The "current record" might be out of focus after the refresh, especially by larger pagination sizes, as the first rows will be shown. Or (even wors...
Post a Comment
Read more

APEX ReadOnly Pages - The easy way

By
If your Oracle APEX Application requires different types of access - full access or readonly - for different types of users, you can specify a Read Only Condition on Page level (or Region, Item, Button, etc.).  You can set an Authorization Scheme on Application level, so it'll be applied to all pages. So if you have an Authorization Scheme named 'User Can Access Page' defined by a PL/SQL function like this: return apex_authorization.user_can_access_page ( p_app_id  => :APP_ID , p_page_id => :APP_PAGE_ID , p_user    => :APP_USER );  then you can code all the logic in the database using the APEX Repository, your own tables or a combination to define whether a user has access to that page or not. But alas it is not possible to define something similar Application wide for a Read Only condition. You can specify an Authorization Scheme 'User has Read Only Access' using a similar signature as the one above and use that on each and e...
Post a Comment
Read more