Re: [sqlalchemy] 1.1.0b1: construct has no default compilation handler.

2016-06-28 Thread Mike Bayer
On 06/28/2016 12:07 PM, Martijn van Oosterhout wrote: On 28 June 2016 at 15:47, Mike Bayer > wrote: On 06/28/2016 09:09 AM, Martijn van Oosterhout wrote: That sqlite reference looks a bit weird, did I miss some

Re: [sqlalchemy] 1.1.0b1: construct has no default compilation handler.

2016-06-28 Thread Martijn van Oosterhout
On 28 June 2016 at 15:47, Mike Bayer wrote: > > > On 06/28/2016 09:09 AM, Martijn van Oosterhout wrote: > >> >> That sqlite reference looks a bit weird, did I miss some initialisation >> somewhere? >> > > It looks like the @compiles system is in place, which SQLAlchemy

Re: [sqlalchemy] 1.1.0b1: construct has no default compilation handler.

2016-06-28 Thread Martijn van Oosterhout
On 27 June 2016 at 16:22, Mike Bayer wrote: > Not really sure, that URL itself won't allow a psycopg2 connection to even > occur. Yeah, I noticed that. psql has sensible defaults here that psycopg2 apparently doesn't have. In this case I'd just stripped the

Re: [sqlalchemy] 1.1.0b1: construct has no default compilation handler.

2016-06-27 Thread Mike Bayer
Not really sure, that URL itself won't allow a psycopg2 connection to even occur. The error means that the construct is trying to be generated as a string, like in a print statement. But 1.1 has a new feature that allows default stringification of pg.ARRAY and other constructs to actually

[sqlalchemy] 1.1.0b1: construct has no default compilation handler.

2016-06-27 Thread Martijn van Oosterhout
When trying out 1.1.0b1 (to look at the new events) I got the $SUBJECT error from our test cases. I'm not sure what exactly is going on, because when I run the script below line-by-line in the django shell, it breaks, but if I run it from the command-line it works. But that's probably more to