Wolodja Wentland wrote:
> On Tue, Nov 03, 2009 at 22:49 +0100, Wolodja Wentland wrote:
>> On Tue, Nov 03, 2009 at 16:29 -0500, Michael Bayer wrote:
>
>> > the error is raised directly by psycopg2.
>
>> I was afraid that the error is with psycopg2. Are you aware of any
>> bugtracker, mailing list o
On Tue, Nov 03, 2009 at 22:49 +0100, Wolodja Wentland wrote:
> On Tue, Nov 03, 2009 at 16:29 -0500, Michael Bayer wrote:
> > the error is raised directly by psycopg2.
> I was afraid that the error is with psycopg2. Are you aware of any
> bugtracker, mailing list or IRC channel that discusses psyc
Wolodja Wentland wrote:
> Hi all,
>
> I have run into a problem with SQLAlchemy r6472 (svn trunk) which might
> be a bug.
the error is raised directly by psycopg2. I'd try taking out the ";" at
the end of the statement, and also checking against a literal string to
see if something weird is hap
On Tue, Nov 03, 2009 at 21:57 +0100, Wolodja Wentland wrote:
> psql_engine = create_engine(
> 'postgresql+psycopg2://babilen:ax8xwymferm...@localhost/typeerr_bug')
^^ oops
Note to self: Double check for sensitive data :-). Guess it is time to
ch
On Tue, Nov 03, 2009 at 16:29 -0500, Michael Bayer wrote:
> the error is raised directly by psycopg2.
I was afraid that the error is with psycopg2. Are you aware of any
bugtracker, mailing list or IRC channel that discusses psycopg2?
> I'd try taking out the ";" at the end of the statement,
Th
