Pros/Cons with CLOB (4000 char limit workaround)

[Wickersty]

Hi folks,

As a basic and limited user of Oracle and databases, I'm wondering what you would suggest as the best workaround for the varchar2 4000 char limit.

Knowing that I will have textual data that needs to be saved that will be more than 4,000 characters, how would you suggest handling that?

The data being stored is used in a Web Authoring Tool which will be later retrieved when rendering web pages. Thus, search engine optimization is a factor, as well as speed.

I dont know much about CLOBs, so I'm wondering if using CLOBs is the best idea - or if using multiple varchar2's and using some kind of identifier to string them together.

Any advice would be greatly appreciated.

Thanks for your time!

Jeff

 

[SantaMufasa]

Jeff,

Your application is the poster child for CLOBs. Use them in good health.

Mufasa
(aka Dave of Sandy, Utah, USA)
[I provide low-cost, remote Database Administration services: www.dasages.com]

 

[Wickersty]

So using CLOBs doesnt mean a negative effect on speed or Search Engine Optimization/Spidering?

 

[SantaMufasa]

I have not noticed any downsides to CLOBs. Oracle has attempted to make CLOB use as "downside-free" as possible. However, all of the above suggestions are subject to:

One test is worth 100 expert opinions.

So, set up your CLOB usage and test it for acceptability.

Mufasa
(aka Dave of Sandy, Utah, USA)
[I provide low-cost, remote Database Administration services: www.dasages.com]