Diploma topic: creating an ORM in PHP using the latest innovations?

Question

PHP

You need to write a thesis. Came up with a topic: creating an ORM in PHP using the latest innovations (mixins, late static binding, generators, finalizers).
What do you think about this theme?

Answer 1

A good ORM is not at all easy to implement. Yes, and their number is not so small.
Interested in PHP?

Answer 2

Write. The doctrine carries a bunch of bugs and inaccuracies. For example, it is virtually impossible to use the date type as a primary key without redefining the type to your own with __toString. And it also doesn’t have a convenient query-builder, I think it can be done a hundred times better with traits) Just don’t do AR, it’s obviously not so interesting)

Answer 3

since when does php support mixins? traits != mixins, and using them to implement orm is somehow silly.
As the topic of a diploma, well ... against the background of those that I have seen, it is still normal, although somehow boring.

Answer 4

And what is the scientific value of a diploma on such a topic? Here, for example, such “diplomas” were quickly “wrapped” ...

Answer 5

with the latest innovations...

… into what? what innovations?
I would be specific.
And instead of "Creation" can be "Development"?
"Developing an ORM in PHP using One, Two, Three."

Answer 6

I would call it "Developing an object-relational mapping tool in PHP <here in a nutshell about the main difference from others>". From a technical point of view, crap, but in the scientific community, the name is usually reduced to a similar form.
From the literature, only PoEAA pops up in memory. In general, it will not be difficult to fill a list of sources on the topic, mainly from English.
If you get a really good solution, be sure to write a topic) Plus, you can include it in the publication.

Answer 7

Will do. It doesn't matter what your topic is. Even 1+ 1 = 2 will do if you can defend well.

Answer 8

Take tests for the diploma directly from the doctrine site, there are links to the description of technologies and patternons.
New - the main benefit of anonymous functions. On the example of AR, something like this - User::with('comments', function(Query $query) { $query->where('active', '=', 1); })->get();
We inject some code at the request execution stage, before you could use eval, create_function or build your own config parser (Symfony still eats this cactus, just not to use closures).
Doctrine traits are used to extend knplabs.com/blog/knp-doctrine-orm-behaviors/ , but they're actually replacing
class User extends TraitName {}
with
class User { use TraitName; }
Moreover, they are not runtime as mixins, and in the same first doctrine without trais, using Templates was more pleasant.
And in general, new items are mostly syntactic sugar, conceptually they do not change the development. It's better to just write about ORM and DDD, as megahertz advised