Have you found yourself thinking: "No, I can't use my object database as a relational database"? Did you come up with a nice way to deal with your persistent model that lends itself naturally to object database technology? Do you think that you can contribute a persistent model pattern that can help developers deal with object databases in an elegant way?

If at least one of the above is affirmative you definitely want to check the latest ODBMS.org's call for submissions on "Common Persistent Model Patterns for Performance and/or Scalability Optimization".

Why is this important or even necessary?

You can't simply deal with object databases using a relational mindset and background (even more so when you need to reach specific levels of performance and scalability).
In Prof. Zicari's own words:

"It is common practice that some database designers treat an Object Database (ODB) like a Relational Database (RDB). That is they are very query intensive rather than model intensive in their design.
Some designers start with a 'relational' model, and then adjust it to a model that is more 'ODB-oriented', or closer to their problem domain, in order to get better results. This task is difficult."

Your submission is welcome and could become an important resource for the object database community.
The pattern with the highest votes will receive special awards!!

For submission details see:
http://www.odbms.org/blog/2009/03/common-persistent-model-patterns-for.html