I re-worked my test a little bit to use logging, and to switch table
definitions based on a command line argument.
I was able to trim down my schema to just the two tables in question,
although the behavior is the same regardless
of the related table, and attached is that schema along with some
Thanks for taking time on this one. That definitely fixes the problem. I
entered it in as Ticket #1556.
I am willing to write a test for this defect, but have no idea how to
check for this other than to turn
on engine.echo and spot it on the console.
I have a theory what this is. Can you try
David Gardner wrote:
Thanks for taking time on this one. That definitely fixes the problem. I
entered it in as Ticket #1556.
I am willing to write a test for this defect, but have no idea how to
check for this other than to turn
on engine.echo and spot it on the console.
oh its fine I can
So I have applied the patch on my development box, but my production
server is still running 0.5.6 un-patched.
Can you think of any reason that defining the column as PGText won't
work as a temporary workaround?
oh its fine I can do it. we have a testing style that is like this:
def go():
