> That's true, Postgres arrays have never been supported by Pygres, > probably because they were pretty restricted anyway so hardly > anybody was using them (maybe they have become more useful in newer > Postgres versions, though).
Well, useful enough that I'm using them in my app, I guess. > There was an attempt to revamp Pygres about a year ago, and this and > other issues have already been put on the list of things to improve: > http://trac.vex.net:8000/pgtracker/ticket/32 > > However, motivation to work on Pygres dwindled strongly after > psycopg2 changed its license and has become so much better, so there > seems to be no real need for Pygres any more these days. E.g. I > think psycopg2 already supports arrays. Well, it's probably OK to keep developing even in the face of other similar projects--look at Empathy, Chromium, etc. etc. > But resuming Pygres development is still on my todolist, it would be > a shame to let Pygres die. Don't know what others think (D'Arcy?). I agree! It looks like a good bunch of code, my only problem so far has been the array thing. And I'd really like to avoid switching libraries halfway through development. > Maybe if somebody could contribute a nice logo and layout for the > homepage and the trac, that would motivate us again. I made > something a year ago (http://www.vex.net/~cito/logo/) but it's not > so great and since then psycopg2 chose a similar theme. Maybe > somebody with an artistic vein has a fancier and funnier idea? I'm not an artist, but I can at least muddle through the array thing, probably. I'll let y'all know if I figure it out. -- Mark Holmquist Student, Computer Science University of Redlands [email protected] _______________________________________________ PyGreSQL mailing list [email protected] http://mailman.vex.net/mailman/listinfo/pygresql
