Search icon CANCEL
Subscription
0
Cart icon
Your Cart (0 item)
Close icon
You have no products in your basket yet
Arrow left icon
Explore Products
Best Sellers
New Releases
Books
Videos
Audiobooks
Learning Hub
Conferences
Free Learning
Arrow right icon
Arrow up icon
GO TO TOP
Oracle Application Express 3.2 - The Essentials and More

You're reading from   Oracle Application Express 3.2 - The Essentials and More Develop Native Oracle database-centric web applications quickly and easily with Oracle APEX

Arrow left icon
Product type Paperback
Published in Jun 2010
Publisher Packt
ISBN-13 9781847194527
Length 644 pages
Edition 1st Edition
Languages
Arrow right icon
Toc

Table of Contents (30) Chapters Close

Oracle Application Express 3.2
Credits
About the Authors
About the Reviewers
1. Preface
1. An Introduction to APEX FREE CHAPTER 2. What we need to know to effectively use APEX 3. APEX Basic Concepts 4. The Application Builder Basic Concepts and Building Blocks 5. APEX Items 6. APEX Buttons 7. APEX Computations 8. APEX Validations 9. APEX Processes 10. APEX Branches 11. APEX SQL Workshop 12. APEX Forms 13. APEX Reports 14. Tabular Forms 15. Calendars 16. Interactive Reports 17. AJAX with APEX 18. Globalization and Localization With APEX Applications 19. Right-To-Left Support in APEX 20. Deploying APEX Applications 21. The APEX Runtime Environment 22. Security 23. Application Conversion 24. APEX Best Practices APEX Installation, Upgrade, and Configuration Tips

Use AL32UTF8 in your DAD


The character set segment of the PlsqlNLSLanguage parameter in the DAD (Database Access Descriptor) file must be set to AL32UTF8. This setting is mandatory regardless of your database character set. This setting is crucial for the correct and smooth operation of both the APEX IDE and the applications we are developing with it, especially (but not only) if we are using AJAX (and the APEX IDE massively uses AJAX).

Oracle recommends using the AL32UTF8 character set as the default choice when installing a new database. If you have plans to develop for a multi-lingual environment, then this is the obvious and simplest choice. Using AL32UTF2, in both the database and the DAD, will save you a lot of character set conversions in the way in and out of the database.

APEX is using AL32UTF8 (Unicode UTF-8) as the default encoding for all the exported files from the Application Builder, and won't even give you an option of changing it.

Note

Bear in mind:

Using any other character set in your DAD, especially one that matches your (local) database character set will not stop APEX from working, and in some cases, it can even appear as it works well. In all likelihood, this is a false and misleading, and it's only a question of when problems start to emerge. Installation and configuration problems are hard enough to diagnose and solve as it is. Don't add another hardship by using a faulty configuration from the start.

lock icon The rest of the chapter is locked
Register for a free Packt account to unlock a world of extra content!
A free Packt account unlocks extra newsletters, articles, discounted offers, and much more. Start advancing your knowledge today.
Unlock this book and the full library FREE for 7 days
Get unlimited access to 7000+ expert-authored eBooks and videos courses covering every tech area you can think of
Renews at $19.99/month. Cancel anytime
Banner background image