你对Doctrine ORM有什么经验? [英] What's your experience with Doctrine ORM?

查看:97
本文介绍了你对Doctrine ORM有什么经验?的处理方法,对大家解决问题具有一定的参考价值,需要的朋友们下面随着小编来一起学习吧!

问题描述

您在原则中的体验是什么?
我从来没有像ORM那样的人,我主要管理一些像adodb这样的基本的数据库抽象层。

What's your experience with doctrine? I've never been much of an ORM kind of guy, I mostlymanaged with just some basic db abstraction layer like adodb.

但我了解了所有的概念和好处。所以当一个项目出现时,需要一个ORM,我以为我会给一个ORM框架一个尝试。

But I understood all the concepts and benifits of it. So when a project came along that needed an ORM I thought that I'd give one of the ORM framework a try.

我必须在学说和推动之间做出决定,所以我选择教义,因为我不想处理这个需求。

I've to decide between doctrine and propel so I choose doctrine because I didn't want to handle the phing requirement.

我不知道我做错了什么我进来了正确的心态。我绝对不是一个初级php小孩。但是我一直在为系统中的每一步做出反应。有很多文档,但都感觉有点混乱。而简单的东西,像YAML到db表创建只是不会工作,只是bork出来,甚至没有错误或任何东西。很多其他的东西工作起来有点时髦,只需要额外的一些调整工作之前。

I don't know what I did wrong. I came in with the right mindset. And I am by no means a 'junior' php kiddie. But I've been fighting the system each step of the way. There's a lot of documentation but it all feels a little disorganize. And simple stuff like YAML to db table creation just wouldn;t work and just bork out without even an error or anything. A lot of other stuff works a little funky require just that extra bit of tweaking before working.

也许我在这里做了一些愚蠢的新手假设,一旦我发现了什么我会有一个哈哈的时刻。但是现在我完全不喜欢这个系统。

Maybe I made some soft of stupid newbie assumption here that once I found out what it is I'll have the aha moment. But now I'm totally hating the system.

有没有人可以提供一些提示,也可能指出我有一个关于这个问题的资源或一些权威网站/人对这个?或者也许只是推荐另一个只是工作的ORM框架?

Is there maybe some tips anyone can give or maybe point me to a good resource on the subject or some authoritative site/person about this? Or maybe just recommend another ORM framework that 'just works"?

推荐答案

我有混合的感觉,我是SQL的主人因为它很容易验证,您可以快速测试SELECT语句,直到得到正确的结果,重构是一个简单的例子。

I have mixed feelings. I am a master at SQL only because it is so easy to verify. You can test SELECT statements quickly until you get the results right. And to refactor is a snap.

在Doctorine或任何ORM中,有很多层次的抽象,它几乎似乎是OCD(强迫/强迫),在我最新的项目中,我尝试了Doctrine,我打了几个墙壁,花了我几天找出一个我知道的解决方案在SQL中写了几分钟,这是非常令人沮丧的。

In Doctorine, or any ORM, there are so many layers of abstraction it almost seems OCD (obsessive/compulsive). In my latest project, in which I tried out Doctrine, I hit several walls. It took me days to figure out a solution for something that I knew I could have written in SQL in a matter of minutes. That is soooo frustrating.

我很脾气,SQL的社区是巨大的,社区/对Doctrine的支持是当然你可以看看来源,试图弄清楚...那些是需要几天时间才能确定的问题。

I'm being grumpy. The community for SQL is HUGE. The community/support for Doctrine is minuscule. Sure you could look at the source and try to figure it out ... and those are the issues that take days to figure out.

底线:不要在很多时间内进行规划,试用教义或任何ORM你自己自己玩吧。

Bottom line: don't try out Doctrine, or any ORM, without planning in a lot of time for grokking on your own.

这篇关于你对Doctrine ORM有什么经验?的文章就介绍到这了,希望我们推荐的答案对大家有所帮助,也希望大家多多支持IT屋!

查看全文
登录 关闭
扫码关注1秒登录
发送“验证码”获取 | 15天全站免登陆