SQLiteDB和ContentProvider的最佳实践-BestpracticesforSQLiteDBandContentProvider

16  

We have been tuning ORMLite on Android for a while now and it is working well. ORMLite supports Android with native database calls and also supports other databases via JDBC. You annotate your classes/fields and use base DAO classes to persist to SQLite.

我们已经在Android上对ORMLite进行了一段时间的调试，并且运行良好。ORMLite通过本地数据库调用支持Android，并通过JDBC支持其他数据库。您可以注释您的类/字段，并使用基础DAO类来持久化到SQLite。

• CREATE TABLE statements are handled my ORMLite's utility classes. Most SQL is taken care of by the DAO classes.
• CREATE TABLE语句是处理我的ORMLite的实用程序类的。大多数SQL都由DAO类处理。
• The Android section of the online documentation explains the class hierarchy. You implement a DatabaseHelper which helps create an update your database. Your activities extend OrmLiteBaseActivity (or service or tab) which gives access to helper and DAOs.
• 在线文档的Android部分解释了类层次结构。实现一个DatabaseHelper，它可以帮助创建更新数据库。您的活动扩展了OrmLiteBaseActivity(或服务或选项卡)，该活动允许访问helper和DAOs。
• ORMLite does not provide a solution for merging with remote REST servers.
• ORMLite没有提供与远程REST服务器合并的解决方案。

Hope this is somewhat helpful.

希望这能有所帮助。

1  

For now, I'm mainly curious to hear how you structure your Android apps with what's available in the standard SDK.

现在，我主要想知道如何用标准SDK中可用的方式来构建Android应用程序。

I'm not a real fan of SQL and the way that it's handled in android, so I use the object database NeoDatis. It basically just lets you store / retrieve Java objects into a flat file stored on the device very easily. db40 is also another alternative Object Database that will work on android.

我不太喜欢SQL，也不喜欢android中处理SQL的方式，所以我使用对象数据库NeoDatis。它基本上只允许您将Java对象存储/检索到存储在设备上的平面文件中。db40也是android上的另一种对象数据库。

Haven't had any issues using this approach, you may want to note that including the NeoDatis library will increase your APK size by ~700kb.

使用这种方法没有任何问题，您可能需要注意，包括NeoDatis库将使APK大小增加大约700kb。

0  

I don't know that I have an answer, other than I don't really like how this is handled, I find it very messy as well. I usually follow the pattern given in the notepad example that comes w/ the SDK.

我不知道我有答案，除了我不喜欢这个怎么处理，我觉得它也很乱。我通常遵循来自w/ SDK的notepad示例中的模式。

Due to this I am working on my own mini ORM framework, using annotation and managing all of this. So far things are working ok, but I haven't worked everything out yet.

因此，我正在开发我自己的迷你ORM框架，使用注释并管理所有这些。到目前为止一切正常，但我还没有把所有的事情都解决。

0  

You could also have a look at Androrm. It is an open source orm tool designed espacially for android. It should help you with all database related stuff.

你也可以看看仙女座。它是一个开源的orm工具，专门为android设计。它将帮助您处理所有与数据库相关的内容。

0  

Just to complete the list more and more ... Another ORM is the ORM solution provided with the BARACUS Framework. It is not inteded to build enterprise sized databases, its more for storing a couple of entities in the database and make it accessible by the app. There is no codegeneration approach inside of it; you simply write your entity pojo, a rowmapper and your table def. Therefore you can make use of DAOs, Dependency Injection, IOC style lifecycle support and much more.

只是为了越来越多地完成这个列表……另一个ORM是由BARACUS框架提供的ORM解决方案。它不是为了构建企业规模的数据库，而是为了在数据库中存储两个实体，并使其可以通过应用程序访问。您只需编写实体pojo、rowmapper和表def，因此可以使用dao、依赖注入、IOC样式的生命周期支持等等。

ORM Features so far :

ORM特性:

• Lazy Loading (Collections + Lazy References)
• 延迟加载(集合+延迟引用)
• CRUD operations for free
• CRUD操作免费
• Query by example
• 实例查询
• a couple of aspects (autotimestamp etc)
• 几个方面(自动时间戳等)
• Persistence layer lifecycle support across multiple application releases
• 跨多个应用程序版本的持久性层生命周期支持

For the more sophisticated database stuff (using the ORM is a little bit hand work like in good old spring rowmapper time) I am currently thinking about adding ormlite integration.

对于更复杂的数据库内容(使用ORM是一种手工操作，就像以前的spring rowmapper时代一样)，我目前正在考虑添加ormlite集成。

For more code details just check the tutorial application on github

有关更多的代码细节，请查看github上的教程应用程序。