[tornado] Request for feedback: Momoko 1.0.0b1

Showing 1-8 of 8 messages
[tornado] Request for feedback: Momoko 1.0.0b1 Frank Smit 12/16/12 12:52 PM

I made time for finishing Momoko's rewrite and most of it is done now.
Enough for a first beta. There are some more advanced feature I would
like to add like asynchronous notifications, named cursors and COPY TO
and COPY FROM, but I'm not sure if any one would use these. Not me at
the moment.

It hasn't been uploaded to PyPi yet, because the lack of documentation
and testing. The unit test all run, but that doesn't make it
production ready.

The changes for this beta release are listed here:

And example code here:
Re: [tornado] Request for feedback: Momoko 1.0.0b1 Frank Smit 1/19/13 9:40 AM
Ok, I'll make that the last feature to implement before the stable
release. After that's done only some documentation is left.

Thanks for the feedback!

On Sat, Jan 19, 2013 at 5:50 AM, mrobellard <mi...@robellard.com> wrote:
> COPY FROM would be most useful as it is the fastest way to bulk insert
> records into the database. Out of the features you listed I would put this
> at the top.
> Thanks for all your hard work. I have been using Momoko with my apps I have
> been working on for a few months now, and haven't run into any major issues.
Re: [tornado] Request for feedback: Momoko 1.0.0b1 Frank Smit 1/19/13 4:46 PM
I've looked into this feature and it's harder than I thought. I only
examined the "COPY FROM" part, because the "COPY TO" is not much
different (from a high-level viewpoint). And I did not examine
everything in detail, but just enough to see how it basically works.

COPY FROM/TO using a file path should work fine, but the file would be
read or written by the database server and not the client. Would be
nicer if you can open a file in Python and feed it to the database
like you can do in "normal" Psycopg2.

What Psycopg2 does in case of COPY FROM is using STDIN and not a file
path. And uses `PQputCopyData` from libpq to write the data from the
file to the connection. This functionality is not exposed to Python
(couldn't find it). That's problem one. The Second problem is you
can't read or write files in a non-blocking way in Tornado.
Re: [tornado] Request for feedback: Momoko 1.0.0b1 Frank Smit 2/28/13 11:24 AM

I've tagged the second beta. Why another beta? I replaced the dynamic
pool with a static one. I think it needs some more testing.

This will be the last beta and I'll start working on new features soon.

-   Tested on CPython 2.6, 2.7, 3.2, 3.3 and PyPy with Psycopg2,
psycopg2ct and psycopg2cffi.
-   Add and remove a database connection to and from the IOLoop for
each operation. See pull request 38 and commits 189323211b and
92940db0a0 for more information.
-   Replaced dynamic connection pool with a static one.
-   Add support for hstore.

Download: https://github.com/FSX/momoko/archive/v1.0.0b2.tar.gz
Documentation: https://momoko.readthedocs.org/en/latest/index.html
Re: [tornado] Request for feedback: Momoko 1.0.0b1 Peter Bengtsson 3/1/13 1:54 PM
Isn't `momoko.Pool` deprecated now?

I'm looking at the "Boilerplate" section on
where it does `application.db = momoko.Pool(`
Re: [tornado] Request for feedback: Momoko 1.0.0b1 Peter Bengtsson 3/1/13 2:26 PM
Ignore me. I got the wrong version installed and got all confused.
Re: [tornado] Request for feedback: Momoko 1.0.0b1 Frank Smit 3/1/13 3:39 PM
> --
> You received this message because you are subscribed to the Google Groups
> "Tornado Web Server" group.
> To unsubscribe from this group and stop receiving emails from it, send an
> email to python-tornad...@googlegroups.com.
> For more options, visit https://groups.google.com/groups/opt_out.
Re: [tornado] Request for feedback: Momoko 1.0.0b1 Frank Smit 5/1/13 1:15 AM
I've uploaded 1.0.0 on PyPi.