Official MongoDB support
#1
Posted 11 March 2011 - 09:29 AM
The new thing is expandability and interoperability and I can't thing of a better way to do it.
-S
#2
Posted 16 March 2011 - 05:43 PM
sivann, on 11 March 2011 - 09:29 AM, said:
The new thing is expandability and interoperability and I can't thing of a better way to do it.
-S
I agree, native mongoDB support would be great!
#3
Posted 30 April 2011 - 11:18 AM
For a long time I didn't know what to think about all the NoSQL/schemaless DB buzz as I was used to MySQL and never had any real problems with using it. But I am currently working on a project where I want users to be able to add attributes to objects on the fly. This sounds terrible from an RDBMS point of view (usually enabled with EAV modelling which is known to be awfully slow) but is a perfect example for the usage of schemaless databases like MongoDB.
I think that applications like that (crowd sourced and flexible) aren't a trend only but a new variant of designing applications as a whole.
I definitely think that adding an ActiveRecord like approach to connect to MongoDB, CoachDB or whatever would be highly beneficial for the whole Yii project. The only problem I see is that they all use completely different APIs as far as I know so adding DB-drivers could be a pain.
My extensions:
ActiveResource for Yii - the RESTful equivalent to ActiveRecord | Neo4Yii - wrapper for the Neo4j graph database | EPhpThumb - a simple, lightweight wrapper for the phpThumb library
Get social:
Circle me on Google Plus
Follow me on Twitter
#4
Posted 01 May 2011 - 05:13 AM
extensions/?tag=mongodb
yiimongodbsuite is what you need.
#5
Posted 02 May 2011 - 03:10 AM
jacmoe, on 01 May 2011 - 05:13 AM, said:
extensions/?tag=mongodb
yiimongodbsuite is what you need.
I know and use this extension already and it is extremely useful and well written. But I personally think that this whole topic is too big to be handled by an extension only approach. Building your whole application on top of an extension can be pretty scary for some businesses I think.
The benefits of a core implementation would be official documentation, additional tests when a new version of Yii is released, a solid team behind it fixing bugs or whatever. With an extension you will always have the problem of different versions of the same thing or "key developers" abandoning the project etc.
My extensions:
ActiveResource for Yii - the RESTful equivalent to ActiveRecord | Neo4Yii - wrapper for the Neo4j graph database | EPhpThumb - a simple, lightweight wrapper for the phpThumb library
Get social:
Circle me on Google Plus
Follow me on Twitter
#6
Posted 08 July 2011 - 03:26 AM
#7
Posted 19 July 2011 - 12:39 AM
MySQL just for structured data focus on col.
MongoDB most like file system focus on row.
#9
Posted 06 March 2012 - 09:17 PM
If yiimongodbsuite is a good candidate, why not merging it with code, as suggested by kernel.
#11
Posted 21 March 2012 - 06:45 PM
There are key value storage, document based, bigtable solutions.
I dont want yii to adopt and merge an extension code or even think that way at all. What I want to see is a solid api supporting more than 1 solutions even if it not so featured with development happiness.
For example dao would be sufficient in the beggining. And by dao I mean a solid layer, with a consistent api that would give my the ability to transparently change from the one nosql to the other by changing the connection string and a little or no more effort.
in the other hand I am not sure how an activerecord could be usefull on something schemaless.
#13
Posted 18 September 2012 - 03:48 AM
#14
Posted 01 November 2012 - 04:11 AM
It's more important for the framework to be modular and have it's components interchangeable than support every technology (new or old), because people will build what they need and share it with the community.
Web Developer
Quote
#15
Posted 10 June 2013 - 08:26 AM
mongoDB as mySQL is a living project, which means it has to be maintained also in the code sometimes.
The problem is what to do if there are 10 extensions for using only mongoDB?
Which to use? Which one will be up to date all the time and compatible with the newest mongoDB specs?
Until you do not choose one project for an official, it can happen that in some time you will have to
- change the mongoDB extension which might be a stick in your head
- update existing yourself which you might not have time for
And that's only cause someone stopped to maintain his extension
F
Andy Rusu, on 01 November 2012 - 04:11 AM, said:
It's more important for the framework to be modular and have it's components interchangeable than support every technology (new or old), because people will build what they need and share it with the community.

Help
















