从Django访问Neo4j的最佳方式是什么？

问题描述

似乎我发现让我困惑的东西;我找到两个Neo4j下载到python，第一个是：

，第二个是：

两者有什么区别？第一个似乎是大（大小），这是否意味着如果我使用它，我不需要neo4j社区发布（里程碑）？

当我'安装了第一个，并尝试测试一个django示例，似乎名为model的目录缺少？那么有什么区别，谁将会更好地与Django一起使用？

这个是什么？

解决方案

我是开始更新，但我会尝试公平=）

您跳过了另一个重要的图书馆 - ，Python REST绑定。 neo4django基于此库，并分享了一大堆 。特别是，REST客户端将始终比本地客户端慢，但它允许轻松使用远程数据库。

neo4django与Django非常紧密的集成。与标准ORM相比，，并有一些很酷的好东西，如查询索引支持，并与关系数据库一起工作。我很喜欢它，但如果你不使用远程数据库，性能损失可能会太高。我正在努力工作，所以！

我相信上面的svn链接（）是旧的本机Python绑定。新的更好从我所看到的（更不用说头痛，更新），所以除非你想给旧的捆绑的Django集成一个尝试，否则会更容易避免。

第一个链接（）是较新的集成。我不认为模型是包含在发行版中，因为它还没有与Django集成。如果您需要认真的表现，并且可以删除Django风格的数据定义语言，那就是要走的路。

将来，我希望得到neo4django与本地和REST客户端工作...我们将看到会发生什么！

it seems that i found something that let me confused; i've found two Neo4j to download to python, the first one is:

• http://pypi.python.org/pypi/neo4j-embedded

and the second one is:

• https://svn.neo4j.org/components/neo4j.py/trunk/

what's the difference between the two? the first one seems to be big (size), so does this mean that if i use it i'll not need the neo4j community release (milestone)?

when i've installed the first one, and tried to test a django example, it seems that the directory named "model" https://svn.neo4j.org/components/neo4j.py/trunk/src/main/python/neo4j/model/ is missing? so what's the difference, and who will be better to use with Django?

and what about that one?

• http://pypi.python.org/pypi/neo4django/

解决方案

I'm part of the team that began updating neo4django from Tobias's original integration, but I'll try to be fair =)

You skipped another important library- neo4j-rest-client, the Python REST binding. neo4django is based on this library, and shares a bunch of its advantages and disadvantages. In particular, a REST client will always be slower than a native client, but it allows the easy use of a remote database.

neo4django is a pretty tight integration with Django. It's very similar to the standard ORM, and has some cool goodies like queries with index support and working alongside a relational DB. I like it alot, but if you aren't using a remote database, the performance penalty might be too high. I'm working on it, though, so keep posted!

I believe the svn link above (https://svn.neo4j.org/components/neo4j.py/trunk/) is the old native Python binding. The new one is way better from what I've seen (less of a headache, updated), so unless you want to give the old bundled Django integration a try, it'd be easier to avoid it.

The first link (http://pypi.python.org/pypi/neo4j-embedded) is the newer integration. I don't think 'model' is included in the distro, because it doesn't yet come with Django integration. If you need serious performance and you're okay with dropping the Django-style data-definition-language, it's the way to go.

In the future, I hope to get neo4django working with the native and REST clients... we'll see what happens!

这篇关于从Django访问Neo4j的最佳方式是什么？的文章就介绍到这了，希望我们推荐的答案对大家有所帮助，也希望大家多多支持！