People use pg8000? ;-)
I jest, but under what circumstances does pg8000 make a better choice
that psycopg2?
Chris
On 07/10/2016 14:40, mike bayer wrote:
FYI pg8000 raises ProgrammingError on these
On 10/07/2016 08:56 AM, Mike Bayer wrote:
On 10/07/2016 02:36 AM, Chris Withers wrote:
FYI pg8000 raises ProgrammingError on these
On 10/07/2016 08:56 AM, Mike Bayer wrote:
On 10/07/2016 02:36 AM, Chris Withers wrote:
On 06/10/2016 15:04, Mike Bayer wrote:
So Mortar seems to be a heavily SQLAlchemy-integrated product.
It has a very small user base ;-)
I'd like
to point
On 10/07/2016 02:36 AM, Chris Withers wrote:
On 06/10/2016 15:04, Mike Bayer wrote:
So Mortar seems to be a heavily SQLAlchemy-integrated product.
It has a very small user base ;-)
I'd like
to point out that whenever we do these year-long release cycles, I put
out a lot of betas very
On 06/10/2016 15:04, Mike Bayer wrote:
So Mortar seems to be a heavily SQLAlchemy-integrated product.
It has a very small user base ;-)
I'd like
to point out that whenever we do these year-long release cycles, I put
out a lot of betas very early on that hopefully contain all the biggish
On 10/06/2016 03:58 AM, Chris Withers wrote:
Hi All,
Since 1.1.0 was released yesterday, one of my library's nightly builds
have started failing:
https://travis-ci.org/Mortar/mortar_mixins/jobs/165422873
Error was:
AssertionError: CompileError(u"Column 'model.period' is marked as a
member
Hi All,
Since 1.1.0 was released yesterday, one of my library's nightly builds
have started failing:
https://travis-ci.org/Mortar/mortar_mixins/jobs/165422873
Error was:
AssertionError: CompileError(u"Column 'model.period' is marked as a
member of the primary key for table 'model', but has
