Hi all,
I'm investigating some issues, where data stored to a text column in mysql
is silently truncated if it's too big.
It appears that the default configuration of mysql, and the sessions
established via sqlalchemy is to simply warn on truncation rather than
raise an error.
This seems to me
Hi Steven,
Nice catch! This is not the first time MySQL has played a joke on us...
I think, we can fix this easily by adding a callback function, which will
set the proper sql_mode value, when a DB connection is retrieved from a
connection pool.
We'll provide a fix to oslo-incubator soon.
On 09/11/2013 11:09 AM, David Ripton wrote:
On 09/11/2013 06:37 AM, Steven Hardy wrote:
I'm investigating some issues, where data stored to a text column in
mysql
is silently truncated if it's too big.
It appears that the default configuration of mysql, and the sessions
established via
Excerpts from Steven Hardy's message of 2013-09-11 03:37:40 -0700:
Hi all,
I'm investigating some issues, where data stored to a text column in mysql
is silently truncated if it's too big.
It appears that the default configuration of mysql, and the sessions
established via sqlalchemy is
On 09/11/2013 06:37 AM, Steven Hardy wrote:
I'm investigating some issues, where data stored to a text column in mysql
is silently truncated if it's too big.
It appears that the default configuration of mysql, and the sessions
established via sqlalchemy is to simply warn on truncation rather
On 09/11/2013 12:28 PM, Monty Taylor wrote:
On 09/11/2013 11:09 AM, David Ripton wrote:
On 09/11/2013 06:37 AM, Steven Hardy wrote:
I'm investigating some issues, where data stored to a text column in
mysql
is silently truncated if it's too big.
It appears that the default configuration of
