Doubt the free sandbox is the problem, as I assume mongoWorkBench is
powered by the same java API as the one which powers openBD mongo
functionality. And in OpenBD I am developing right now on a sandbox
collection. Oh well, would be happy to see it fixed, but as you have
seen already, the mongoHQ online interface is also fairly well done
(though it lacks badly in certain areas) so I guess that compared to
most I/we aren't that badly in need of something like mongoWorkBench.
Greetings,
David
Op 5/2/2013 3:51 PM, Alan Williamson schreef:
i have reached out to them.
it may be their free sandbox account is what is tripping me up.
On 02/05/2013 09:45, David Mulder wrote:
Hmm, I have been constantly making collections by just doing inserts
into them. And yeah, thought that was the case as I said in the
issue, however as long as it's possible to connect, it's fine with
some of the commands just failing with an error message as long as
the allowed stuff keeps working (primarily testing selection objects
and browsing the stored data). We have been using mongohq in
production now for a few projects with more to come and it's working
very well and aside of the fact that I need to connect straight to a
specific database, I never encountered any other limitations.
--
--
online documentation: http://openbd.org/manual/
http://groups.google.com/group/openbd?hl=en
---
You received this message because you are subscribed to the Google Groups "Open BlueDragon" group.
To unsubscribe from this group and stop receiving emails from it, send an email
to [email protected].
For more options, visit https://groups.google.com/groups/opt_out.
