On May 11, 5:00 pm, Luper Rouch luper.ro...@gmail.com wrote:
On May 11, 3:38 pm, Michael Bayer mike...@zzzcomputing.com wrote:
On May 11, 2011, at 8:11 AM, Luper Rouch wrote:
I agree, when a timeout happens, we display an error message and tell
the user its last operation failed
On May 12, 1:04 pm, Luper Rouch luper.ro...@gmail.com wrote:
On May 11, 5:00 pm, Luper Rouch luper.ro...@gmail.com wrote:
On May 11, 3:38 pm, Michael Bayer mike...@zzzcomputing.com wrote:
On May 11, 2011, at 8:11 AM, Luper Rouch wrote:
I agree, when a timeout happens, we
On May 12, 4:17 pm, Michael Bayer mike...@zzzcomputing.com wrote:
On May 12, 2011, at 7:25 AM, Luper Rouch wrote:
I still have the exact same issue when using SessionExtension's
before_flush() and after_flush_postexec() methods, demonstrated here
:http://paste.pocoo.org/show/387444
On May 10, 8:16 pm, Michael Bayer mike...@zzzcomputing.com wrote:
On May 10, 2011, at 2:12 PM, Michael Bayer wrote:
The purpose of events is to provide hooks into points inside of
SQLAlchemy's internal processes that would otherwise be impossible.
Adding events outside of its
On May 10, 8:12 pm, Michael Bayer mike...@zzzcomputing.com wrote:
On May 10, 2011, at 12:48 PM, Luper Rouch wrote:
I often run into problems when working with SA's events.
MapperExtension's methods are called in the middle of a flush, and so
there are things to take care
On May 11, 3:38 pm, Michael Bayer mike...@zzzcomputing.com wrote:
On May 11, 2011, at 8:11 AM, Luper Rouch wrote:
I agree, when a timeout happens, we display an error message and tell
the user its last operation failed. The point is not recovering from
the failure automatically
The keyword for floating point columns is REAL according to the SQLite
documentation (http://www.sqlite.org/datatype3.html), but only FLOAT
is recognized by SQLAlchemy.
This patch corrects the problem.
--~--~-~--~~~---~--~~
You received this message because you
