close
Welcome! Wikis are websites that everyone can build together. It's easy!

Data Cartridge

References

The Oracle reference for Data Cartridges can be found in the following online links:

Simple Description

A Data Cartridge is a software package that conforms to a set of programming specifications and uses supplied functions. This allows a software developer to extend the functionality of the Oracle database by incorporating extra knowledge into how data is indexed. A Data Cartridge is put forward as a means for Software Development Companies to sell packaged solutions to clients who are also software developers.

Design Patterns Description

For those of you who are into Design Patterns, a Data Cartridge is a Factory that creates a index type which is a Facade. This index type is then instantiated as a Domain Index.

Example of a Data Cartridge Implementation

With each distribution of Oracle Database Server comes an implementation of Data Cartridge which is called Oracle Text. Further references can be found in:

Hierarchy of Types of Indexing

The hierarchy of types of indexing, in order of increasing complexity, is:
  1. No index (data is accessed by table scans)
  2. Simple index (CREATE INDEX a ON table(column))
  3. Functional index (CREATE INDEX a ON table(function(column)))
  4. Domain index (CREATE INDEX a ON table(column) INDEXTYPE IS type)
Both of the last two (2) require extra work to done before the index can be used.

Recommended Approach to Data Cartridges

  1. Are you sure you want to implement Data Cartridges?
  2. Have a good night's sleep (this is your last chance of getting some)
  3. Are you really sure want to do this?
  4. Read the manual.
  5. Implement the sample code.
  6. Are you still sure?
  7. Use the sample code as a basis for a prototype.
  8. Measure the performance on a substantial amount of data.
  9. Curse the day you were born.
  10. Calm down and review the performance hints.
  11. Reconsider your decision
  12. Update this Wiki entry with your tale of woe.
  13. Implement your design

Performance Hints

  1. Avoid correlated function calls
  2. Use out arrays on ODCIIndexFetch calls
  3. Optimise your internal data structures
  4. Instrument your code
  5. Really instrument your code


Latest page update: made by dfhawthorne , Nov 16 2007, 4:19 AM EST (about this update About This Update dfhawthorne Initial draft - dfhawthorne

364 words added

view changes
- complete history)
Keyword tags: Application Programming Data Cartridge Domain Index
More Info: links to this page

Threads

Anonymous  (Get credit for your thread)
Started By Thread Subject Replies Last Post
rwhomer Chemistry Data Cartridges 0 Jan 15 2008, 6:47 PM EST by rwhomer
Thread started: Jan 15 2008, 6:47 PM EST  Watch
I have implemented 2 data cartridges and managed the development of a third one. The hard part is if you want to get the Optimizer to make useful choices. With chemistry cartridges at least many queries are highly selective and many more are very very unselective. Communicating this to Oracle isn't all that easy. And forget about using a version earlier than 10g. The 9i version always chose to use the domain index even if there was a much betteer access path.
Its an interesting technology though and for some applications its the best way to integrate complex data with Oracle.
Do you find this valuable?    
Keyword tags: Application Programming Data Cartridge Domain Index

Attachments

Unknown File odci-test.sql (Unknown File - 15k)
posted by marcelo.ochoa   Nov 27 2007, 4:10 PM EST
A simple test case which show how to implement a new Domain Index in Java

Related Content

(what's this?Related ContentThanks to keyword tags, links to related pages and threads are added to the bottom of your pages. Up to 15 links are shown, determined by matching tags and by how recently the content was updated; keeping the most current at the top. Share your feedback on Wetpaint Central.)
Chemistry Data Cartridges

Top Contributors