[pylons-discuss] New Package for Integrating Mongodb

[Jonathan Mackenzie]

After being dissatisfied with existing mongodb projects:

* pyramid_mongo
* pyramid_mongodb
* pyramid_mongoengine

These only allow a single database to be integrated and don't offer a
debugtoolbar and are very simple to setup and configure.

I extracted the code I made for my own projects and made it into a pair of
packages:

https://github.com/JonnoFTW/pyramid_mongodb2
https://github.com/JonnoFTW/pyramid_mongodb2_debugtoolbar

I apologise for the poor naming, but I hope someone finds these useful,
especially the debugtoolbar which took a while to get right.

Any feature suggestions or feedback (except for that fact that they lack
tests) would be greatly appreciated. If you're interested in a database
layout for your application, I also wrote:

https://github.com/JonnoFTW/mongo-schema-export

Which allows you to export a schema from an existing application (or you
could hand write it), so you don't have to write scripts that setup
collections, indexes and validators whenever you deploy your application!

[Jonathan Vanasco]

any reason why you decided to split the toolbar into a separate package,
instead of including it?

[Jonathan Mackenzie]

Lack of thought I guess, I should probably merge them and use a config
variable to turn debugging on..

Post by Jonathan Vanasco
any reason why you decided to split the toolbar into a separate package,
instead of including it?

[Jonathan Vanasco]

Post by Jonathan Mackenzie
Lack of thought I guess, I should probably merge them and use a config
variable to turn debugging on..

IMHO I really like the idea of Pyramid packages that ship with a built-in
debug_toolbar support.

[Michael Merickel]

You don't really need a config variable if done correctly, other than what
pyramid_debugtoolbar already supports. The panel should be enabled only if
a user does something like `debugtoolbar.includes =
pyramid_mongodb.debugtoolbar`.

Post by Jonathan Mackenzie
Lack of thought I guess, I should probably merge them and use a config
variable to turn debugging on..

Post by Jonathan Vanasco
any reason why you decided to split the toolbar into a separate package,
instead of including it?

--
You received this message because you are subscribed to the Google Groups
"pylons-discuss" group.
To unsubscribe from this group and stop receiving emails from it, send an
To view this discussion on the web visit
https://groups.google.com/d/msgid/pylons-discuss/b3bde938-0ce6-4e3a-91fd-f10d1d2c44b0%40googlegroups.com
<https://groups.google.com/d/msgid/pylons-discuss/b3bde938-0ce6-4e3a-91fd-f10d1d2c44b0%40googlegroups.com?utm_medium=email&utm_source=footer>
.
For more options, visit https://groups.google.com/d/optout.

[Jonathan Mackenzie]

Cool, I'll do that.

Post by Michael Merickel
You don't really need a config variable if done correctly, other than what
pyramid_debugtoolbar already supports. The panel should be enabled only if
a user does something like `debugtoolbar.includes =
pyramid_mongodb.debugtoolbar`.

Post by Jonathan Mackenzie
Lack of thought I guess, I should probably merge them and use a config
variable to turn debugging on..

Post by Jonathan Vanasco
any reason why you decided to split the toolbar into a separate package,
instead of including it?

--
You received this message because you are subscribed to the Google Groups
"pylons-discuss" group.
To unsubscribe from this group and stop receiving emails from it, send an
<javascript:>.
To view this discussion on the web visit
https://groups.google.com/d/msgid/pylons-discuss/b3bde938-0ce6-4e3a-91fd-f10d1d2c44b0%40googlegroups.com
<https://groups.google.com/d/msgid/pylons-discuss/b3bde938-0ce6-4e3a-91fd-f10d1d2c44b0%40googlegroups.com?utm_medium=email&utm_source=footer>
.
For more options, visit https://groups.google.com/d/optout.

[Jonathan Mackenzie]

I've updated the package now,

https://github.com/jonnoFTW/pyramid_mongodb2

Everything is integrated into a single package. And now you can alias
database names to make testing easier.

Post by Jonathan Mackenzie
Cool, I'll do that.

Post by Michael Merickel
You don't really need a config variable if done correctly, other than
what pyramid_debugtoolbar already supports. The panel should be enabled
only if a user does something like `debugtoolbar.includes =
pyramid_mongodb.debugtoolbar`.

Post by Jonathan Mackenzie
Lack of thought I guess, I should probably merge them and use a config
variable to turn debugging on..

Post by Jonathan Vanasco
any reason why you decided to split the toolbar into a separate
package, instead of including it?

--
You received this message because you are subscribed to the Google
Groups "pylons-discuss" group.
To unsubscribe from this group and stop receiving emails from it, send
To view this discussion on the web visit
https://groups.google.com/d/msgid/pylons-discuss/b3bde938-0ce6-4e3a-91fd-f10d1d2c44b0%40googlegroups.com
<https://groups.google.com/d/msgid/pylons-discuss/b3bde938-0ce6-4e3a-91fd-f10d1d2c44b0%40googlegroups.com?utm_medium=email&utm_source=footer>
.
For more options, visit https://groups.google.com/d/optout.

[Jonathan Vanasco]

Post by Jonathan Mackenzie
I've updated the package now,
https://github.com/jonnoFTW/pyramid_mongodb2
Everything is integrated into a single package. And now you can alias
database names to make testing easier.

wow, the toolbar features are amazingly useful!