Framework: Mongo DB in core

[gauravtiwari]

This is a feature not a bug. It will be good to have MongoDB in the core and work with Eloquent ORM.

[andrewryno]

While I'd love it in Eloquent by default, Mongo is much different than SQL so it would be difficult to just write a simple wrapper for it. LMongo is a great extension of Eloquent to allow for almost all functionality from Mongo.

[taylorotwell]

This is something that can be discussed by the team during the upcoming planning phase for release 4.1.

[gauravtiwari]

Thanks Taylor. It will be great addition to Laravel out of the box.
@andrewryno Thanks. Yes I have looked at it before and it seemed very good to me but I think it would be good to remove all those configurations and setup to do after installing the wrapper. I mean if its works just like mysql configuration and everything is available there then its less confusing to use it. I hope you understand, its just my opinion.

[Anahkiasen]

I'd very much appreciate something in favor of Mongo in Laravel.

[gauravtiwari]

@taylorotwell @Anahkiasen @andrewryno Yeah more like rails & Mongoid GEM.

[gauravtiwari]

@taylorotwell Thank you so much for consideration.

[julien-c]

LMongo is ok, but it's more of a literal port of Eloquent (with query builder, etc.) that doesn't really account for the essential conceptual differences between Mongo and SQL.

Here's a more lightweight (and I think, closer to the spirit of both Laravel and Mongo) wrapper to the driver, that @Anahkiasen and I wrote over the last couple of weeks : https://github.com/julien-c/mongovel

Mongovel implements the Eloquent syntax without abstracting away anything from Mongo – for instance:

• you can access items like objects, not arrays (i.e. $user->name),
• you can call static functions on collections: i.e. $users = User::find();. Let us know what you think!

[gauravtiwari]

@julien-c I agree on LMongo. The github repo gave in the link looks really great and less confusing than others. At the moment I see one findOne, will other Laravel methods work as normal? It will be great to have good documentation on this.

I think its really great something like MongoID for rails.

[julien-c]

Yes, Mongovel always at least proxies calls to the underlying MongoCollections and MongoCursors.

I've updated the README to explicitly document that.

[RSully]

I'd love to see a elegant solution in the Laravel core that adds MongoDB support. Right now I am researching solutions like @navruzm's LMongo, @jenssegers Laravel-MongoDB, and @Zizaco's MongoLid.

It looks like LMongo is the only solution that has support for Auth/Sessions/Validation/etc as separate modules.

[jenssegers]

The reason why I created https://github.com/jenssegers/Laravel-MongoDB is because existing packages did not respect the Eloquent interface. I wanted to be able to switch the database driver from mysql to mongodb (or the other way around) without having to change anything in models.

The current Eloquent code is pretty modular, but still tightly coupled to a sql syntax.

[julien-c]

Hi Ryan,

Have you checked out http://github.com/julien-c/Mongovel?

On Tue, Aug 6, 2013 at 3:11 PM, Ryan [email protected] wrote:

I'd love to see a elegant solution in the Laravel core that adds MongoDB
support. Right now I am researching solutions like @navruzmhttps://github.com/navruzm's
LMongo, @jenssegers https://github.com/jenssegers Laravel-MongoDB, and
@Zizaco https://github.com/Zizaco's MongoLid.

It looks like LMongo is the only solution that has support for
Auth/Sessions/Validation/etc as separate modules.

—
Reply to this email directly or view it on GitHubhttps://github.com/laravel/framework/issues/465#issuecomment-22177351
.

[RSully]

@julien-c Right now LMongo is the only serious candidate given my need for out-of-the-box session support.

Edit: Laravel-MongoDB has session support now and it might be a better fit given that it respects Eloquent's interface.

[flow99]

+1 to mongoDB , what is the problem with mongoDB ?

[jenssegers]

I my opinion, MongoDB is too different from the current database implementation which uses PDO. It wouldn't be a great match. Also, not everyone needs MongoDB, so if there's packages for those people, why not just use the packages?

[flow99]

yes jenssegers you gave a very nice explanation about the Technical details ...but i want to be sure that mongoDB will be alaways Updated , optimized and secure to the all laravel versions in the future .
and to ensure that case i dont think thier is other way ??

this is An open question ?

thank you jenssegers about your work this is great.

[flow99]

And not everyone needs SQLITE :)

[hackel]

I know this bug has been dead for a while, but I wanted to raise the issue again. MongoDB really is a mainstream product for web development these days. I believe that either MySQL/PDO and all other DB drivers should be removed and put into separate packages, or MongoDB support should be included in the core. MySQL and MongoDB each have their strengths and weaknesses, but for the majority of object-oriented web development applications, MongoDB is just more suited to the task.

I am currently using @jenssegers' excellent laravel-mongodb package, but unfortunately it still has quite a few bugs and limitations that I believe could be eliminated if it were made a 1st-class-citizen in Laravel, got more eyes on the code, and more than one main contributor to the project. I hope this can at least facilitate a discussion about this! Thanks.

[crynobone]

but unfortunately it still has quite a few bugs and limitations that I believe could be eliminated if it were made a 1st-class-citizen in Laravel

You should know that even Laravel bugs are not explicitly solved by the contributors, and mainly require the community to send in bugfixes (there are many example where bug report being closed without any solution). Unless the things that the contributors use explicitly. So, the scenario wouldn't be much different, unless you can somehow make the contributors to actually use MongoDB.

Classic example is MsSQL support on Laravel.

[NoelDeMartin]

This has been dead for a while, but the last "official" news I can see from this thread is Taylor's comment about that team meeting 4 years ago. Which was the outcome of that meeting?. Also, what ended up happening is what @flow99 said, the other packages have been accumulating bugs and I don't think they meet Laravel standards.

@taylorotwell What's your opinion on this at the moment? Is there a possibility to include MongoDB on the core (or even if it isn't the core, as an official laravel extension)?

[juanpscotto]

Please, I want to know what happend too. What are the offical news?. Thanks

[NoelDeMartin]

I have tried multiple times to get a clear response as to what the status is. The closer I got was this: https://twitter.com/taylorotwell/status/972448506765078528 It's still not a clear answer nor do I know why the decision was made, but I think it's 99% clear that there are no short nor long term plans to add it. So my conclusion at least is that next time I have to start a Laravel project with Mongo, I will probably do it from scratch... If it shapes up to be something nice I may release it as open source, but it's not likely to get more popular nor better than existing solutions, so my conclusion is that MongoDB is a big hole in the Laravel ecosystem that will remain open for a long time. Until there aren't any "official" news about it, I think that's a fair assumption to make.

[juanpscotto]

@NoelDeMartin. Yes that's too sad. I think it's very important to add it to the core. Because php phalcon already has an ODM for mongodb.

[vahidalvandi]

pls add mongodb in core

[vahidalvandi]

https://github.com/jenssegers/laravel-mongodb