I have started working on creating an Object database supported by RDBMS on backend.我已开始工作，创造一个对象数据库的支持RDBMS的对后端。 No it is not an ORM layer.没有，这是不是一个ORM的ORM层。 It is a pure object database to the user.这是一个纯对象数据库给用户。 Behind the scenes the actual data is stored in the relational database with a simple schema.幕后的实际数据存储在关系型数据库的一个简单的架构。 Primary object access mechanisms will be through Query by template object and by implementing SODA.小学物件存取机制，将通过查询模板对象，并执行苏打水。 Currently I am 40% done with the object saving code.目前我做了40 ％ ，与对象节省代码。
Much has been my pain with available ODB’s to force me to embark on this journey.已有不少我的疼痛与现有odb的，迫使我走上这方面的征程。 Few steps I am taking to remove the pains I faced with existing tools are as below:几个步骤我考虑，以消除痛苦， i面临与现有的工具如下：

  1. Ability to migrate data easily when the underlying data model changes.能力迁移数据时，很容易背后的数据模型的变化。 Type narrowing is handled automatically.类型缩小是自动处理。 Field removal is handled, so is field addition.外地免职处理，所以是外地此外。 More complex cases can be mapped with an in-built mapper.较复杂的个案可以映射与一在建映射。
  2. Relational schema is easily readable and understandable(not Klingonese)关系模式是很容易阅读和理解的（不klingonese ）
  3. Easy to use.易于使用。 No complex XML file to setup (which requires you to understand enough of RDBMS to kill the joy of using ODB).没有复杂的XML文件来安装（这需要您了解足够的RDBMS的杀人的喜悦，用odb ） 。
  4. No artifical requirement of using only the methods to access data, no need to declare serializable(may change it later)任何人为的要求，只用方法来存取资料，没有需要申报序列（可能会改变它后来）
  5. Very simple API, very low learning curve.很简单，空气污染指数，非常低的学习曲线。 In fact you can live by knowing only four method call事实上，你可以活知道只有4个方法调用

I am looking forward to know your experience and frustrations (and enjoyments of course) with Object databases.我期待着知道你的经验和挫折（和享受，当然）与对象的数据库。 I will try to see if I can address the defects and make it more suitable for your and my needs.我会尝试看看，如果我能解决的缺陷，使它更适合您和我的需要。