On Thursday 11 December 2008 09:29:36 am Christoph Zwerschke wrote: > johnf schrieb: > > Thanks I have not reviewed the patch. But have you tested your patch > > against postgres 7.4 and against psycopg 1.x? For the moment we are > > still providing ways to support both. I know that postgres 7.4 and > > psycopg 1 are very old but it was a request from Ed. When we started > > 7.4 was the dominant postgres version in use and psycopg 1 was the > > only version. I know this sounds limiting. But if you can test would > > you? I no longer have access to 7.4. > > I haven't used any newer features than those already used in the trunk > (note that the current trunk doesn't run out of the box with Pg 7.4 > anyway, you at least have to manually add the "generate_series" function > to make it work). > > I haven't used any newer psycopg features either. So nothing should be > broken that wasn't broken before. But I noticed the current trunk > already uses DictCursor which seems to be a psycopg2 feature and the > docstring of the __init__ method also says only psycopg2 is supported. > > > That said, I believe we should drop support for postgres 7.4 and > > psycopg 1. > > I strongly agree, since dabo 0.9 now officially requires Python 2.4 > anyway (from the release dates, Py 2.3 goes along with Pg 7.4, while Py > 2.4 goes with Pg 8.0; psycopg 2 beta was available shortly after Py 2.4, > so this all makes sense). > > > And I think we should use all the features that Postgres offers and > > psycopg 2 has to offer. Your example of using the `QuotedString()` is > > only one of several that could be used. > > Btw, I noticed that some of the Python code is a bit old fashioned as > well and can benefit a lot from using Py 2.4 features. > > > You may not be aware but some time in the future Dabo is scheduled to > > move away from the present use of dbPostgres and other database > > interfaces. And move to SQLAchemy or the some other tool to access > > data. Just a FYI. > > That would be great. SQLAlchemy is great, I'm already using it > elsewhere. I think it would be a perfect fit for dabo. The BizObjects > could probably become SQLAlchemy ORM objects directly mapped to tables. > > But dabo will probably need more automated tests to make such large > refactorings possible. > > > Please do not consider these statements in a negative way because I > > do not want to discourage you in anyway. In fact it is nice to see > > someone else that takes the time to help with the interface to > > postgres. Just be aware. > > That's not discouraging at all :) > > -- Christoph Like I said I did not have a chance to review the patch at that time. And to be honest I haven't really taken a close look at dbPostgres for a long time. I've just added patches as someone points out a bug or needed a feature. BTW some version of 7.4 do have "generate_series". I can recall being surprized when someone discovered the problem with an older version of 7.4.
Setting the retrieveal of the system fields to false may not be the best. There are plenty of 7.4 coders that depend on those fields. I don't but when I googled 7.4 code I still see it as a requirement. When I added schema's I set the system tables to False and I can't recall anyone actually saying anything. Maybe we do it and wait for any complaints. We are not going to drop 7.4. The Postgres guys are still supporting the version with updates. What about setting up a bracket around 7.4 stuff? DictCursor is now a moot question - but I think it was added in version 1. I just got permission to drop support for psycopg 1. So if you are inclined go for it. Let your fingers sing! And thanks for the help. -- John Fabiani _______________________________________________ Post Messages to: [email protected] Subscription Maintenance: http://leafe.com/mailman/listinfo/dabo-dev Searchable Archives: http://leafe.com/archives/search/dabo-dev This message: http://leafe.com/archives/byMID/[email protected]
