blocks|key|2057281|text|我个人使用FMDB，最后一次更新是在昨天。|type|unstyled|depth|inlineStyleRanges|entityRanges|offset|length|data|2057282|entityMap|0|LINK|mutability|MUTABLE|url|https://github.com/ccgus/fmdb^0|5|4|0|0^^$0|@$1|2|3|4|5|6|7|L|8|@]|9|@$A|M|B|N|1|O]]|C|$]]|$1|D|3|-4|5|6|7|P|8|@]|9|@]|C|$]]]|E|$F|$5|G|H|I|C|$J|K]]]]

I personally use <a href="https://github.com/ccgus/fmdb" rel="noreferrer">FMDB</a>, and the last update to it was yesterday.

blocks|key|2057291|text|我也是FMDatabase的粉丝，尽管我不得不定制我自己的版本。我的应用程序在它周围使用了一个我编写的名为ArchDBObject的层，它可以透明地将对象转换为数据库表示形式；我正在考虑以某种形式发布它，但我还没有真正决定如何释放它。|type|unstyled|depth|inlineStyleRanges|entityRanges|data|2057292|在任何情况下，都可以在https://github.com/ccgus/fmdb上使用FMDatabase。|offset|length|2057293|entityMap|0|LINK|mutability|MUTABLE|url|https://github.com/ccgus/fmdb^0|0|B|T|0|0^^$0|@$1|2|3|4|5|6|7|N|8|@]|9|@]|A|$]]|$1|B|3|C|5|6|7|O|8|@]|9|@$D|P|E|Q|1|R]]|A|$]]|$1|F|3|-4|5|6|7|S|8|@]|9|@]|A|$]]]|G|$H|$5|I|J|K|A|$L|M]]]]

I'm also a fan of FMDatabase, although I've had to customize my own version of it. My apps use a layer around it I wrote called ArchDBObject that transparently converts objects to and from a database representation; I'm thinking about releasing it in some form, but I haven't really decided how yet.

In any case, FMDatabase can be had at <a href="https://github.com/ccgus/fmdb" rel="nofollow noreferrer">https://github.com/ccgus/fmdb</a>.

blocks|key|2057302|text|FMDB很好用，因为它是最轻量级的方法，不必处理C调用和类型转换，同时仍为您提供对SQL的完全访问。|type|unstyled|depth|inlineStyleRanges|entityRanges|data|2057303|关于对象关系包装器，我通常不喜欢的一点是，您离生成的SQL太远了，而这正是性能开始受到影响的时候。|2057304|entityMap^0|0|0^^$0|@$1|2|3|4|5|6|7|F|8|@]|9|@]|A|$]]|$1|B|3|C|5|6|7|G|8|@]|9|@]|A|$]]|$1|D|3|-4|5|6|7|H|8|@]|9|@]|A|$]]]|E|$]]

FMDB is nice because it's the lightest way to not have to deal with the C calls and type conversions, while still giving you full access to the SQL.

The thing I generally do not like about object-relational wrappers is that you get too distant from the SQL being generated and that's when performance can start to suffer.

blocks|key|1843189|text|我在http://code.google.com/p/chibiorm/的FDBM上有一个简单的对象关系映射。|type|unstyled|depth|inlineStyleRanges|entityRanges|offset|length|data|1843190|有了它，您可以随时使用原始SQL，以字典列表的形式返回任何SQL，或者使用优秀的OO风格。|1843191|entityMap|0|LINK|mutability|MUTABLE|url|http://code.google.com/p/chibiorm/^0|2|Y|0|0|0^^$0|@$1|2|3|4|5|6|7|N|8|@]|9|@$A|O|B|P|1|Q]]|C|$]]|$1|D|3|E|5|6|7|R|8|@]|9|@]|C|$]]|$1|F|3|-4|5|6|7|S|8|@]|9|@]|C|$]]]|G|$H|$5|I|J|K|C|$L|M]]]]

I have a simple ORM on top of FDBM here <a href="http://code.google.com/p/chibiorm/" rel="nofollow noreferrer">http://code.google.com/p/chibiorm/</a>.

With it, you can use raw SQL when you wish, return any SQL as a dict list, or use the nice OO style.

blocks|key|2057315|text|我花了几个小时来研究这些选项--这些选项还没有投入生产，所以YMMV。|type|unstyled|depth|inlineStyleRanges|entityRanges|data|2057316|我找到的最轻的包装器是：|2057317|http://th30z.netsons.org/2008/11/objective-c-sqlite-wrapper/|offset|length|2057318|我不知道它有没有正式的名字。它只有一个类，它抽象了SQL的糟糕之处，同时保留了直接使用SQLite的价值。假设您已经了解SQL，那么学习曲线是5分钟。由于它很小，我可以想象它很容易修复任何可能出现问题的地方。|2057319|entityMap|0|LINK|mutability|MUTABLE|url^0|0|0|0|1O|0|0|0^^$0|@$1|2|3|4|5|6|7|Q|8|@]|9|@]|A|$]]|$1|B|3|C|5|6|7|R|8|@]|9|@]|A|$]]|$1|D|3|E|5|6|7|S|8|@]|9|@$F|T|G|U|1|V]]|A|$]]|$1|H|3|I|5|6|7|W|8|@]|9|@]|A|$]]|$1|J|3|-4|5|6|7|X|8|@]|9|@]|A|$]]]|K|$L|$5|M|N|O|A|$P|E]]]]

I spent the last few hours looking at the options -- haven't been in production with any of these yet, so YMMV.

The lightest weight wrapper I found was here:

<a href="http://th30z.netsons.org/2008/11/objective-c-sqlite-wrapper/" rel="nofollow noreferrer">http://th30z.netsons.org/2008/11/objective-c-sqlite-wrapper/</a>

I don't know if it has an official name. It's just 1 class, and it abstracts the nastiness of the SQLite api, while leaving the value of working directly with SQL. The learning curve is 5 minutes, assuming you know SQL already. Since it's so small, I can imagine it would be easy to fix anything that might go wrong with it.

blocks|key|1843195|text|如果需要，还可以查看以下存储库，该存储库提供了一组可用于创建SQL语句的类，并提供了一种处理SQLite数据库连接的简单方法。它位于https://github.com/ziminji/objective-c-sql-query-builder|type|unstyled|depth|inlineStyleRanges|entityRanges|offset|length|data|1843196|entityMap|0|LINK|mutability|MUTABLE|url|https://github.com/ziminji/objective-c-sql-query-builder^0|1U|1K|0|0^^$0|@$1|2|3|4|5|6|7|L|8|@]|9|@$A|M|B|N|1|O]]|C|$]]|$1|D|3|-4|5|6|7|P|8|@]|9|@]|C|$]]]|E|$F|$5|G|H|I|C|$J|K]]]]

If you want, you could also have a look at the following repository that provides a set of classes that can be used to create SQL statements and provides a simple way to handle a SQLite database connection. It is located at <a href="https://github.com/ziminji/objective-c-sql-query-builder" rel="nofollow">https://github.com/ziminji/objective-c-sql-query-builder</a>

blocks|key|1843198|text|我找到的最简单的是这个https://github.com/misato/SQLiteManager4iOS|type|unstyled|depth|inlineStyleRanges|entityRanges|offset|length|data|1843199|SQLiteManager作者:+Ester+Sanchez。|1843200|它的使用基本上是这样的：|1843201|NSArray+*results+=+[dbManager+getRowsForQuery:@"SELECT+*+FROM+table+WHERE+id+=+1"];|code-block|syntax|javascript|1843202|results是一个包含字典的数组。每个字典都是一个单独返回的行，其中键是表中每列的名称。|style|CODE|1843203|在此之后，您可以执行以下操作：|1843204|NSDictionary+*aPerson+=+[results+objectAtIndex:0];
NSString+*firstName+=+aPerson[@"firstName"];
NSString+*email+=+aPerson[@"email"];|1843205|entityMap|0|LINK|mutability|MUTABLE|url|https://github.com/misato/SQLiteManager4iOS^0|B|17|0|0|0|0|0|0|7|0|0|0^^$0|@$1|2|3|4|5|6|7|12|8|@]|9|@$A|13|B|14|1|15]]|C|$]]|$1|D|3|E|5|6|7|16|8|@]|9|@]|C|$]]|$1|F|3|G|5|6|7|17|8|@]|9|@]|C|$]]|$1|H|3|I|5|J|7|18|8|@]|9|@]|C|$K|L]]|$1|M|3|N|5|6|7|19|8|@$A|1A|B|1B|O|P]]|9|@]|C|$]]|$1|Q|3|R|5|6|7|1C|8|@]|9|@]|C|$]]|$1|S|3|T|5|J|7|1D|8|@]|9|@]|C|$K|L]]|$1|U|3|-4|5|6|7|1E|8|@]|9|@]|C|$]]]|V|$W|$5|X|Y|Z|C|$10|11]]]]

The simplest I've found is this one <a href="https://github.com/misato/SQLiteManager4iOS" rel="nofollow noreferrer">https://github.com/misato/SQLiteManager4iOS</a>

SQLiteManager by Ester Sanchez.

Using it is basically like this:

<pre><code>NSArray *results = [dbManager getRowsForQuery:@"SELECT * FROM table WHERE id = 1"];
</code></pre>

<code>results</code> is an array containing dictionaries. Each dictionary is a single returned row where the keys are the names of each column in the table.

After that you can do things like this:

<pre><code>NSDictionary *aPerson = [results objectAtIndex:0];
NSString *firstName = aPerson[@"firstName"];
NSString *email = aPerson[@"email"];
</code></pre>

I'm developing for the iPhone and am looking for a good Cocoa/Objective-C library for working with SQLite. I don't want to use the standard procedural SQLite C API. I see options at <a href="http://www.sqlite.org/cvstrac/wiki?p=SqliteWrappers" rel="noreferrer">sqlite.org</a> under the Objective-C section, but am not sure which is the best in terms of library API design, stability, and functionality. I'd like to use something that's actively being developed and hopefully will be around for a while. Anyone have suggestions based on experience using one?

Thanks

Best Cocoa/Objective-C Wrapper Library for SQLite on iPhone

Objective-C

数据库

SQLite

我正在为iPhone开发，并且正在寻找一个好的用于SQLite的Cocoa/Objective-C库。我不想使用标准的过程SQLite C应用程序接口。我在的Objective-C部分看到了一些选项，但我不确定在库API设计、稳定性和功能方面哪一个是最好的。我想用一些正在积极开发中的东西，希望能用上一段时间。有没有人根...

问iPhone上SQLite的最佳Cocoa/Objective-C包装库
EN

社区

活动

资源

关于

腾讯云开发者

热门产品

热门推荐

更多推荐

问iPhone上SQLite的最佳Cocoa/Objective-C包装库EN

社区

活动

资源

关于

腾讯云开发者

热门产品

热门推荐

更多推荐

问iPhone上SQLite的最佳Cocoa/Objective-C包装库
EN