Testing with concurrent sessions
in [PgSql]
|
From: "Kevin Grittner" on 15 Jan 2010 10:47 Markus Wanner <markus(a)bluegap.ch> wrote: > Second: at the very end of pg_dtester.py, you find the line: > reporter = StreamReporter() > > Try a CursesReporter() instead, it gives much nicer output! When I try to do that, Kate complains (I'm even copying their typo): You are trying to save a python file as non ASCII, without specifiying a correct source encoding line for encoding "utf-8" It offers these options: Insert: # -*- coding: utf-8 -*- Save Nevertheless Cancel Should that coding line be in there? -Kevin -- Sent via pgsql-hackers mailing list (pgsql-hackers(a)postgresql.org) To make changes to your subscription: http://www.postgresql.org/mailpref/pgsql-hackers
From: "Greg Sabino Mullane" on 15 Jan 2010 11:33 -----BEGIN PGP SIGNED MESSAGE----- Hash: RIPEMD160 > Dead or not, it still works, even against 8.4. I have many programs > that use it. It's simply a wrapper around the libpq interface and as > long as the libpq interface remains stable (which we go to great pains > to do), so will this module. Well, I stand corrected. Good to know. > Given the talk of importing some perl module into the postgresql tree > it just seemed more logical to me to take something that was close to > libpq and had no external dependancies than taking a module with an > external dependancy (namely DBI). Yes, I could see that. Actually, I just came across another one by Hiroyuki OYAMA and Aaron Crane. This was last updated January 10, 2010! : http://search.cpan.org/~arc/DBD-PgPP-0.08/ Still requires DBI of course, but no Perl library or compiling required as DBD::Pg does. So we've not got three valid options. :) - -- Greg Sabino Mullane greg(a)turnstep.com PGP Key: 0x14964AC8 201001151129 http://biglumber.com/x/web?pk=2529DF6AB8F79407E94445B4BC9B906714964AC8 -----BEGIN PGP SIGNATURE----- iEYEAREDAAYFAktQmI0ACgkQvJuQZxSWSsgNugCgjwkT9QwGpvhcIXCNYhRcTwSW JZcAnjvrsjwpO/QvJ1LzU+cUZ4UqajxV =bu4q -----END PGP SIGNATURE----- -- Sent via pgsql-hackers mailing list (pgsql-hackers(a)postgresql.org) To make changes to your subscription: http://www.postgresql.org/mailpref/pgsql-hackers
From: Markus Wanner on 15 Jan 2010 13:20 Hi, Kevin Grittner wrote: > Not sure what's relevant there. Entire file tarball attached. Due to reasons mentioned in this thread as well, I've decided to use psql to connect to the database. dtester is parsing its output and checks that against expectations. Hawever, that has its own pitfalls, so in the end I'm almost about to change back to using libpq or implementing the bare minimum protocol (that might have its own merits within the twisted world, if implemented in the required async fashion). Strangely, your log has escape codes in it, which I'm assuming makes the parsing choke. Is that something special to your installation? My psql never colors its outputs... However, the quickest way forward probably is to filter out escape sequences. Turning off tty is not really an option, because dtester doesn't have a chance to capture all necessary events, in that mode. > Yes I can. Any queries you'd like me to run in there? It looks like psql can connect, too. It's just the parsing of outputs which fails. Regards Markus -- Sent via pgsql-hackers mailing list (pgsql-hackers(a)postgresql.org) To make changes to your subscription: http://www.postgresql.org/mailpref/pgsql-hackers
From: Markus Wanner on 15 Jan 2010 13:23 Hi, Kevin Grittner wrote: > You are trying to save a python file as non ASCII, without > specifiying a correct source encoding line for encoding "utf-8" I wasn't aware I had non-ascii characters in there. Inserting an encoding line seems fine. I'll fix that for the upcoming version 0.1. Regards Markus -- Sent via pgsql-hackers mailing list (pgsql-hackers(a)postgresql.org) To make changes to your subscription: http://www.postgresql.org/mailpref/pgsql-hackers
From: "Kevin Grittner" on 15 Jan 2010 13:33
Markus Wanner <markus(a)bluegap.ch> wrote: > I wasn't aware I had non-ascii characters in there. Inserting an > encoding line seems fine. I'll fix that for the upcoming version > 0.1. Yeah, I couldn't find any, either. I just tried creating a minimal python file in Kate, and it gave me that even though I *know* it was all ASCII characters right off my keyboard. I guess Kate is being overly picky. On the other hand, if it silences an annoying message sometimes, maybe that's reason enough to add it. -Kevin -- Sent via pgsql-hackers mailing list (pgsql-hackers(a)postgresql.org) To make changes to your subscription: http://www.postgresql.org/mailpref/pgsql-hackers |