blocks|key|683167|text|我会选择Sequelize，因为它有很好的文档。这只是一个诚实的观点(我从来没有在Node中使用过那么多MySQL+)。|type|unstyled|depth|inlineStyleRanges|entityRanges|offset|length|data|683168|entityMap|0|LINK|mutability|MUTABLE|url|http://sequelizejs.com/^0|4|9|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 would choose <a href="http://sequelizejs.com/">Sequelize</a> because of it's excellent documentation. It's just a honest opinion (I never really used MySQL with Node that much).

blocks|key|899735|text|首先，请注意，我没有使用它们中的任何一个(但使用了Node.js)。|type|unstyled|depth|inlineStyleRanges|entityRanges|data|899736|这两个库都有很好的文档记录，并且都有稳定的API。然而，persistence.js似乎是used+in+more+projects。不过，我不知道他们是否都还在使用它。|offset|length|899737|sequelize的开发者有时会在blog.depold.com上发表关于它的博客。当您想要使用主键作为外键时，您将需要this+blog+post中描述的补丁。如果你需要persistence.js的帮助，有一个谷歌小组致力于此。|899738|从示例中我可以看出，sequelize比persistance.js更像JavaScript(更甜蜜)，但支持的数据存储更少(只有MySQL，而persistance.js甚至可以使用浏览器内存储)。|899739|我认为sequelize可能是适合你的方式，因为你只需要MySQL支持。但是，如果您需要一些方便的功能(例如搜索)，或者想在以后使用不同的数据库，则需要使用persistence.js。|899740|entityMap|0|LINK|mutability|MUTABLE|url|http://persistencejs.org/users|1|http://blog.depold.com/|2|http://www.hiddentao.com/archives/2011/11/18/primary-key-foreign-key-improvements-to-sequelize-date-js-alternatives/^0|0|19|L|0|0|H|F|1|1O|E|2|0|0|0^^$0|@$1|2|3|4|5|6|7|X|8|@]|9|@]|A|$]]|$1|B|3|C|5|6|7|Y|8|@]|9|@$D|Z|E|10|1|11]]|A|$]]|$1|F|3|G|5|6|7|12|8|@]|9|@$D|13|E|14|1|15]|$D|16|E|17|1|18]]|A|$]]|$1|H|3|I|5|6|7|19|8|@]|9|@]|A|$]]|$1|J|3|K|5|6|7|1A|8|@]|9|@]|A|$]]|$1|L|3|-4|5|6|7|1B|8|@]|9|@]|A|$]]]|M|$N|$5|O|P|Q|A|$R|S]]|T|$5|O|P|Q|A|$R|U]]|V|$5|O|P|Q|A|$R|W]]]]

First off, please note that I haven't used either of them (but have used Node.js).

Both libraries are documented quite well and have a
stable API. However, persistence.js seems to be <a href="http://persistencejs.org/users" rel="noreferrer">used in more projects</a>. I don't know if all of them still use it, though.

The developer of sequelize sometimes blogs about it at <a href="http://blog.depold.com" rel="noreferrer">blog.depold.com</a>. When you'd like to use primary keys as foreign keys, you'll need the patch that's described in <a href="http://www.hiddentao.com/archives/2011/11/18/primary-key-foreign-key-improvements-to-sequelize-date-js-alternatives/" rel="noreferrer">this blog post</a>. If you'd like help for persistence.js there is a google group devoted to it.

From the examples I gather that sequelize is a bit more JavaScript-like (more sugar) than persistance.js but has support for fewer datastores (only MySQL, while persistance.js can even use in-browser stores).

I think that sequelize might be the way to go for you, as you only need MySQL support. However, if you need some convenient features (for instance search) or want to use a different database later on you'd need to use persistence.js.

blocks|key|683288|text|Sequelize和Persistence.js之间的一个主要区别是前者支持STRING数据类型，即VARCHAR(255)。我觉得把所有的东西都变成TEXT真的很不舒服。|type|unstyled|depth|inlineStyleRanges|offset|length|style|CODE|entityRanges|data|683289|entityMap^0|12|6|1E|C|23|4|0^^$0|@$1|2|3|4|5|6|7|H|8|@$9|I|A|J|B|C]|$9|K|A|L|B|C]|$9|M|A|N|B|C]]|D|@]|E|$]]|$1|F|3|-4|5|6|7|O|8|@]|D|@]|E|$]]]|G|$]]

One major difference between Sequelize and Persistence.js is that the former supports a <code>STRING</code> datatype, i.e. <code>VARCHAR(255)</code>. I felt really uncomfortable making everything <code>TEXT</code>.

I'm rewriting a project to use Node.js. I'd like to keep using MySQL as the DB (even though I don't mind rewriting the schema).
I'm looking for a simple-to-use, reasonable-performance ORM, which supports caching, many-to-one and many-to-many relations.
From the MySQL ORMs I could find, <a href="https://github.com/coresmart/persistencejs">persistencejs</a> and <a href="http://sequelizejs.com">sequelize</a> seem the most mature. 
Do you have experience with either? What are the relevant pros and cons I should be aware of in my decision?

Which ORM should I use for Node.js and MySQL?

数据存储

数据库

MySQL

我正在重写一个使用Node.js的项目。我希望继续使用MySQL作为DB (尽管我不介意重写模式)。我正在寻找一种简单易用、性能合理的ORM，它支持缓存、多对一和多对多关系。从我能找到的MySQL ORM中，和似乎是最成熟的。你有使用这两种方法的经验吗？在我的决定中，我应该了解哪些相关的利弊？

问我应该为Node.js和MySQL使用哪种对象/对象模型？
EN

社区

活动

资源

关于

腾讯云开发者

热门产品

热门推荐

更多推荐

问我应该为Node.js和MySQL使用哪种对象/对象模型？EN

社区

活动

资源

关于

腾讯云开发者

热门产品

热门推荐

更多推荐

问我应该为Node.js和MySQL使用哪种对象/对象模型？
EN