Hi all, I'm trying to use APE (yesterday CVS version) on Zope 2.7.0 and Postgresql, but I'm not able to make it work. With some minor changes in datatypes.py (change loadConf for load_conf), it works fine using FSConnection, but DBAPIConnection seems not to be ready to work together with ZConfig machinery. Is there any way to have a working config for postgresql and zope 2.7 ? Or everybody is working with FileSystem storages and SQL storages are just working with zope 2.6 ? Thanks in advance Santi Camps http://zetadb.sourceforge.net
santi@zetadb.com wrote:
I'm trying to use APE (yesterday CVS version) on Zope 2.7.0 and Postgresql, but I'm not able to make it work.
You could do with being a bit more explicit about the problems you encountered. Exception type, value and traceback please... Chris -- Simplistix - Content Management, Zope & Python Consulting - http://www.simplistix.co.uk
santi@zetadb.com wrote:
Is there any way to have a working config for postgresql and zope 2.7 ? Or everybody is working with FileSystem storages and SQL storages are just working with zope 2.6 ?
Thanks for reporting this. I just now brought the ZConfig schema up to date. See the updated component.xml for an example of setting up a connection to Postgres. Shane
Shane Hathaway escribió:
santi@zetadb.com wrote:
Is there any way to have a working config for postgresql and zope 2.7 ? Or everybody is working with FileSystem storages and SQL storages are just working with zope 2.6 ?
Thanks for reporting this. I just now brought the ZConfig schema up to date. See the updated component.xml for an example of setting up a connection to Postgres.
Shane
Thanks a lot for your answer !! It works fine :-) Let me make a suggestion: In next releases, leave SQLMultiTableProperties option as default. That's what all Zope newbies are looking for, I think. I meet a lot of developers that like Zope, but they are disturbed if data aren't in a relational database, but also if data aren't in a relational way (just what SQLMultiTableProperties does). It could seems a silliness, but it's real, and stops a lot of people to use Zope. I think Ape will help a lot to expand Zope. I will begin to intesively use Ape with SQLMultiTableProperties option over Postgresql. Of course, I will report eventual bugs in the collector. Thanks again Santi Camps
Santi Camps wrote:
Let me make a suggestion: In next releases, leave SQLMultiTableProperties option as default. That's what all Zope newbies are looking for, I think. I meet a lot of developers that like Zope, but they are disturbed if data aren't in a relational database, but also if data aren't in a relational way (just what SQLMultiTableProperties does). It could seems a silliness, but it's real, and stops a lot of people to use Zope. I think Ape will help a lot to expand Zope. I will begin to intesively use Ape with SQLMultiTableProperties option over Postgresql. Of course, I will report eventual bugs in the collector.
Ok, I think you may be right. However, SQLMultiTableProperties still needs some work. The table names that it chooses can potentially overlap or run over the limit that some databases place on table names. To fix this, it needs to manage the table names in a small table. I don't think it will be hard to do. Shane
participants (4)
-
Chris Withers -
Santi Camps -
santi＠zetadb.com
-
Shane Hathaway