Re: [Zope-DB] Unified DA for Zope 2 using SQLAlchemy?
Andreas Jung wrote at 2007-3-25 17:49 +0200: In the Zope 2 worlds we have dedicated database adapters for different databases. Fortunately the Python world made us a wonderful present called SQLAlchemy that abstracts the different databases. In the Zope world we have some wrappers like z3c.zalchemy and z3c.sqlalchemy... basically they deal with connection handling, mapper handling and integration with the Zope transaction system. Would it make sense to replace all different Zope DAs with a generic DA on top of one of the z3c.* wrappers? I think it would not be too hard to write such a DA...or am I missing something? Thoughts? As I think I know you a bit, I would expect that you also want to deprecate the current support and get rid of it altogether within a year. This would get an even greater desaster than the tried removal of zLOG: huge amounts of applications would stop to work -- and many people would stop to use new Zope releases. Otherwise, I would not object against an *additional* SQLAlchemy based adapter. -- Dieter ___ Zope-DB mailing list Zope-DB@zope.org http://mail.zope.org/mailman/listinfo/zope-db
Re: [Zope-DB] Unified DA for Zope 2 using SQLAlchemy?
--On 26. März 2007 22:21:02 +0200 Dieter Maurer [EMAIL PROTECTED] wrote: Andreas Jung wrote at 2007-3-25 17:49 +0200: In the Zope 2 worlds we have dedicated database adapters for different databases. Fortunately the Python world made us a wonderful present called SQLAlchemy that abstracts the different databases. In the Zope world we have some wrappers like z3c.zalchemy and z3c.sqlalchemy... basically they deal with connection handling, mapper handling and integration with the Zope transaction system. Would it make sense to replace all different Zope DAs with a generic DA on top of one of the z3c.* wrappers? I think it would not be too hard to write such a DA...or am I missing something? Thoughts? As I think I know you a bit, I would expect that you also want to deprecate the current support and get rid of it altogether within a year. My posting says *nothing* about deprecating something. So __please__ stop reading between the lines when there is nothing - except whitespaces. This would get an even greater desaster than the tried removal of zLOG: huge amounts of applications would stop to work -- and many people would stop to use new Zope releases. Otherwise, I would not object against an *additional* SQLAlchemy based adapter. That's *exactly* what I am talking about - an *additional* generic DA on top of SA where we don't have to care about the different RDBMS flavours - at least not the ones directly supported through SA. -aj pgp6f2ihWA6Ze.pgp Description: PGP signature ___ Zope-DB mailing list Zope-DB@zope.org http://mail.zope.org/mailman/listinfo/zope-db
Re: [Zope-DB] Unified DA for Zope 2 using SQLAlchemy?
Am 26.03.2007, 22:31 Uhr, schrieb Andreas Jung [EMAIL PROTECTED]: That's *exactly* what I am talking about - an *additional* generic DA on top of SA where we don't have to care about the different RDBMS flavours - at least not the ones directly supported through SA. I'm all for an SQLAlchemy DA (does SQLAlchemy support anything other than PostgreSQL?) and this would help people move from Zope 2 to Zope 3 but it *cannot* replace the other DA's because of the imperfect nature of SQL and the even less perfect nature of RDBMs. :-/ Furthermore, there are many occasions where you want the kind of direct access to a relation you get with the existing DA's. Charlie -- Charlie Clark eGenix.com Professional Python Services directly from the Source Python/Zope Consulting and Support ...http://www.egenix.com/ mxODBC.Zope.Database.Adapter ... http://zope.egenix.com/ mxODBC, mxDateTime, mxTextTools ...http://python.egenix.com/ Try mxODBC.Zope.DA for Windows,Linux,Solaris,MacOSX for free ! eGenix.com Software, Skills and Services GmbH Pastor-Loeh-Str.48 D-40764 Langenfeld, Germany. CEO Dipl.-Math. Marc-Andre Lemburg Registered at Amtsgericht Duesseldorf: HRB 46611 ___ Zope-DB mailing list Zope-DB@zope.org http://mail.zope.org/mailman/listinfo/zope-db
Re: [Zope-DB] Unified DA for Zope 2 using SQLAlchemy?
My posting says *nothing* about deprecating something. So __please__ stop reading between the lines when there is nothing - except whitespaces. But you said about *replacing* all different zope DAs. So I think it is not reading between lines. I agree that this kind of adapter (as additional one) is a nice idea :) -- Maciej Wisniowski ___ Zope-DB mailing list Zope-DB@zope.org http://mail.zope.org/mailman/listinfo/zope-db
[Zope-DB] ZMySQLDA thinks that MySQL has gone away
Hello, I got this error when querying MySQL 5.0.26. I use Zope 2.9.4 and ZMysqlDA 2.0.9b3 (with MySQLdb 1.2.1_p2). MySQL do not gone away. This error only happens after exactly 8 hours of database inactivity. I found some information about this error. It seems is caused because MySQL close the connection after 8 hours, this time is stored at 'wait_timeout' system variable in the MySQL server. I'm doing an application for school where isn't there activity at night. Then db.py don't know this because it feels that connection is alive. Maybe the solution is check the connection before db.query. Something similar in Zope3-Dev: http://mail.zope.org/pipermail/zope3-dev/2005-December/017052.html The solution: http://mail.zope.org/pipermail/checkins/2006-September/004078.html Traceback (innermost last): - Module ZPublisher.Publish, line 194, in publish_module_standard - Module ZPublisher.Publish, line 157, in publish - Module Zope2.App.startup, line 243, in abort - Module transaction._manager, line 107, in abort - Module transaction._transaction, line 507, in abort - Module transaction._transaction, line 580, in abort - Module Shared.DC.ZRDB.TM, line 64, in abort - Module Products.ZMySQLDA.db, line 389, in _abort error: release unlocked lock Other people with the problem: http://mail.zope.org/pipermail/zope/2005-June/159762.html http://dev.plone.org/plone/ticket/6263 It will be possible fix this? If not, how can I do the transactions with MySQL? Maybe with sqlobject o sqlalchemy? Sorry for my English and sorry for create a new thread (*ticino at hccnet.nl *put this question on the list some days ago). Thanks in advance. Peter Lion ___ Zope-DB mailing list Zope-DB@zope.org http://mail.zope.org/mailman/listinfo/zope-db
Re: [Zope-DB] ZMySQLDA thinks that MySQL has gone away
On Mon, Mar 26, 2007, Pedro Le?n L?pez wrote: Hello, I got this error when querying MySQL 5.0.26. I use Zope 2.9.4 and ZMysqlDA 2.0.9b3 (with MySQLdb 1.2.1_p2). MySQL do not gone away. This error only happens after exactly 8 hours of database inactivity. I found some information about this error. It seems is caused because MySQL close the connection after 8 hours, this time is stored at 'wait_timeout' system variable in the MySQL server. I'm doing an application for school where isn't there activity at night. Given that mysql (or any other database) may well be restarted as part of log rotation and cron maintenance, you may well want to not depend on continuously open connections. Bill -- INTERNET: [EMAIL PROTECTED] Bill Campbell; Celestial Software LLC URL: http://www.celestial.com/ PO Box 820; 6641 E. Mercer Way FAX:(206) 232-9186 Mercer Island, WA 98040-0820; (206) 236-1676 ``During times of universal deceit, telling the truth becomes a revolutionary act.'' --George Orwell ___ Zope-DB mailing list Zope-DB@zope.org http://mail.zope.org/mailman/listinfo/zope-db
Re: [Zope-DB] ZMySQLDA thinks that MySQL has gone away
- Original Message - From: Pedro León López [EMAIL PROTECTED] To: zope-db@zope.org Sent: Monday, March 26, 2007 5:56 PM Subject: [Zope-DB] ZMySQLDA thinks that MySQL has gone away Hello, I got this error when querying MySQL 5.0.26. I use Zope 2.9.4 and ZMysqlDA 2.0.9b3 (with MySQLdb 1.2.1_p2). MySQL do not gone away. This error only happens after exactly 8 hours of database inactivity. I found some information about this error. It seems is caused because MySQL close the connection after 8 hours, this time is stored at 'wait_timeout' system variable in the MySQL server. I'm doing an application for school where isn't there activity at night. Then db.py don't know this because it feels that connection is alive. Maybe the solution is check the connection before db.query. Very easy to create a simple DTML routine which accesses MySQL; then set up a cron job to run that DTML routine every few hours. Jonathan ___ Zope-DB mailing list Zope-DB@zope.org http://mail.zope.org/mailman/listinfo/zope-db
Re: [Zope-DB] Unified DA for Zope 2 using SQLAlchemy?
--On 26. März 2007 22:49:21 +0200 Maciej Wisniowski [EMAIL PROTECTED] wrote: My posting says *nothing* about deprecating something. So __please__ stop reading between the lines when there is nothing - except whitespaces. But you said about *replacing* all different zope DAs. So I think it is not reading between lines. Well you know that Zope does not skip with any DA (except the one for Gadyfly). So I am not in the position to replace anything in the Zope core that does not exist :-) Especially I am not in the position to replace any third-party products. So my whole posting has absolutely nothing to with the Zope core. I am just trying to collect feedback - good or bad - for a such a project - *totally independent* of the Zope 2 core. I hope this was clear enough - even for Dieter. I agree that this kind of adapter (as additional one) is a nice idea :) Andreas pgpaD0GiU0l8j.pgp Description: PGP signature ___ Zope-DB mailing list Zope-DB@zope.org http://mail.zope.org/mailman/listinfo/zope-db
