Query Languages For In Memory Objects

"Native Queries for Persistent Objects -- a concise and type-safe way to express queries directly as Java and C# methods"

• "Native Queries for Persistent Objects, A Design White Paper" by William Cook and Carl Rosenberger
  • http://www.odbms.org/download/010.01%20Cook%20Native%20Queries%20for%20Persistent%20Objects%20August%202005.pdf
  • http://www.db4o.com/about/productinformation/whitepapers/Native%20Queries%20Whitepaper.pdf (from http://www.db4o.com/about/productinformation/whitepapers/default.aspx#nq)

---

Implementations:

for DotNet:

• .NET implementation: LanguageIntegratedQueryProject (to be in production in "Orcas" release -- around 2007???)
• DbForObjects
• "Add Support for "Set" Collections to .NET", an implementation of "Sets" for .NET by JasonSmith? -- http://www.codeproject.com/csharp/sets.asp

for Java:

• The JavaGenericLibrary (JGL) is a Java library providing collections and generic algorithms to perform various operations on those collections. (ClosedSource)
• JavaAlgorithmLibrary
• ApacheCommonsFunctor
• Generic Libraries for Java (JGL� Toolkit) - http://www.recursionsw.com/jgl.htm (ClosedSource; ~$99)
• DbForObjects
• POJQ ("PlainOldJavaQueries?") - http://pojq.dev.java.net/
• JoSql - "SQL for Java Objects"
• "The Data Structures Library in Java" - http://www.cs.brown.edu/cgc/jdsl/about.html

---

Articles:

• "Functional programming in the Java language" -- http://www-128.ibm.com/developerworks/library-combined/j-fp.html

---

Why make a distinction between RAM and disk? I suppose one could argue that RAM is getting large and cheap enough, but still it would be nice to scale up when needed without changing query languages.

---

See Also: NimbleDatabase, ProgrammingWithoutRamDiskDichotomy, MinimalTable