From phd at phd.pp.ru Sun Apr 11 19:09:25 2010 From: phd at phd.pp.ru (Oleg Broytman) Date: Sun, 11 Apr 2010 21:09:25 +0400 Subject: [DB-SIG] SQLObject 0.11.5 Message-ID: <20100411170925.GC20481@phd.pp.ru> Hello! I'm pleased to announce version 0.11.5, a minor bugfix release of 0.11 branch of SQLObject. What is SQLObject ================= SQLObject is an object-relational mapper. Your database tables are described as classes, and rows are instances of those classes. SQLObject is meant to be easy to use and quick to get started with. SQLObject supports a number of backends: MySQL, PostgreSQL, SQLite, Firebird, Sybase, MSSQL and MaxDB (also known as SAPDB). Where is SQLObject ================== Site: http://sqlobject.org Development: http://sqlobject.org/devel/ Mailing list: https://lists.sourceforge.net/mailman/listinfo/sqlobject-discuss Archives: http://news.gmane.org/gmane.comp.python.sqlobject Download: http://cheeseshop.python.org/pypi/SQLObject/0.11.5 News and changes: http://sqlobject.org/News.html What's New ========== News since 0.11.4 ----------------- * Fixed a bug in replacing _connection in a case when no previous _connection has been set. For a more complete list, please see the news: http://sqlobject.org/News.html Oleg. -- Oleg Broytman http://phd.pp.ru/ phd at phd.pp.ru Programmers don't die, they just GOSUB without RETURN. From phd at phd.pp.ru Sun Apr 11 19:11:22 2010 From: phd at phd.pp.ru (Oleg Broytman) Date: Sun, 11 Apr 2010 21:11:22 +0400 Subject: [DB-SIG] SQLObject 0.12.3 Message-ID: <20100411171122.GG20481@phd.pp.ru> Hello! I'm pleased to announce version 0.12.3, a minor bugfix release of branch 0.12 of SQLObject. What is SQLObject ================= SQLObject is an object-relational mapper. Your database tables are described as classes, and rows are instances of those classes. SQLObject is meant to be easy to use and quick to get started with. SQLObject supports a number of backends: MySQL, PostgreSQL, SQLite, Firebird, Sybase, MSSQL and MaxDB (also known as SAPDB). Where is SQLObject ================== Site: http://sqlobject.org Development: http://sqlobject.org/devel/ Mailing list: https://lists.sourceforge.net/mailman/listinfo/sqlobject-discuss Archives: http://news.gmane.org/gmane.comp.python.sqlobject Download: http://cheeseshop.python.org/pypi/SQLObject/0.12.3 News and changes: http://sqlobject.org/News.html What's New ========== News since 0.12.2 ----------------- * Fixed a bug in replacing _connection in a case when no previous _connection has been set. For a more complete list, please see the news: http://sqlobject.org/News.html Oleg. -- Oleg Broytman http://phd.pp.ru/ phd at phd.pp.ru Programmers don't die, they just GOSUB without RETURN. From master_shonuff at yahoo.com Fri Apr 9 16:42:50 2010 From: master_shonuff at yahoo.com (master_shonuff) Date: Fri, 9 Apr 2010 07:42:50 -0700 (PDT) Subject: [DB-SIG] Multivalue database access - non-SQL In-Reply-To: <4B78C49B.3060207@gmail.com> References: <4B78C49B.3060207@gmail.com> Message-ID: <28191051.post@talk.nabble.com> I've begun writing a native RPC connector for UniData/UniVerse and will post something as soon as it's worthy. slestak wrote: > > Norm, > > I have been looking at this as well. Thinking about using swig to wrap > the Intercall library so code can be written independently of the ODBC > driver. > > How far have you gotten so far. I would definitely like to help on this. > > Steve > _______________________________________________ > DB-SIG maillist - DB-SIG at python.org > http://mail.python.org/mailman/listinfo/db-sig > > -- View this message in context: http://old.nabble.com/Multivalue-database-access---non-SQL-tp25158216p28191051.html Sent from the Python - db-sig mailing list archive at Nabble.com. From serge.adourian at ubisoft.com Mon Apr 12 19:09:13 2010 From: serge.adourian at ubisoft.com (Serge Adourian) Date: Mon, 12 Apr 2010 13:09:13 -0400 Subject: [DB-SIG] Python 2.4 db connection to MySQL 5.1 Message-ID: <9E4A58AAF133E74A9114B0FA0F2FCC6B777865AD@MDC-MAIL-CMS01.ubisoft.org> Hello, Does Python 2.4 and MySQLdb connections to MySQL 5.1 use persistent or non-persistent connections? Is this the right place to ask this question? Thank you -------------- next part -------------- An HTML attachment was scrubbed... URL: From farcepest at gmail.com Tue Apr 13 22:03:01 2010 From: farcepest at gmail.com (Andy Dustman) Date: Tue, 13 Apr 2010 16:03:01 -0400 Subject: [DB-SIG] Python 2.4 db connection to MySQL 5.1 In-Reply-To: <9E4A58AAF133E74A9114B0FA0F2FCC6B777865AD@MDC-MAIL-CMS01.ubisoft.org> References: <9E4A58AAF133E74A9114B0FA0F2FCC6B777865AD@MDC-MAIL-CMS01.ubisoft.org> Message-ID: On Mon, Apr 12, 2010 at 1:09 PM, Serge Adourian wrote: > Hello, > > > > Does Python 2.4 and MySQLdb connections to MySQL 5.1 use persistent or > non-persistent connections? Connections are persistent until closed for all DB-API databases. > Is this the right place to ask this question? It is now. -- Patriotism means to stand by the country. It does not mean to stand by the president. -- T. Roosevelt MANDATED GOVERNMENT HEALTH WARNING: Government mandates may be hazardous to your health. This message has been scanned for memes and dangerous content by MindScanner, and is believed to be unclean. From skremer at uoguelph.ca Wed Apr 21 20:00:02 2010 From: skremer at uoguelph.ca (Stefan C. Kremer) Date: Wed, 21 Apr 2010 14:00:02 -0400 Subject: [DB-SIG] PEP 249 clarification Message-ID: <75A1DD78-C0D7-491F-B7B0-33F8D227F18B@uoguelph.ca> Hi, The "fetchall()" command returns a list. Lists are mutable objects in python. Could a valid implementation return the same list object (with different contents) for multiple calls to fetchall() (with potentially different preceding execute queries)? e.g. cursor.execute( """SELECT * FROM table1;""" ); result = cursor.fetchall(); print result; cursor.execute("""SELECT * FROM table2;""" ); junk = cursor.fetchall(); print result; Is it possible, in a valid implementation, for the two print statements to generate different output (which would be the case if, for example, the fetchall method used an internal list which is a member variable of the cursor object in its return)? It seems to me that it is important for implementors and users of a DBI to understand the implications of this. Thanks, Stefan -- Dr. Stefan C. Kremer Dept. of Computing & Information Science skremer at uoguelph.ca * 519-824-4120x58913 From mal at egenix.com Wed Apr 21 23:20:49 2010 From: mal at egenix.com (M.-A. Lemburg) Date: Wed, 21 Apr 2010 23:20:49 +0200 Subject: [DB-SIG] PEP 249 clarification In-Reply-To: <75A1DD78-C0D7-491F-B7B0-33F8D227F18B@uoguelph.ca> References: <75A1DD78-C0D7-491F-B7B0-33F8D227F18B@uoguelph.ca> Message-ID: <4BCF6C31.1070700@egenix.com> Stefan C. Kremer wrote: > Hi, > > The "fetchall()" command returns a list. Lists are mutable objects in python. Could a valid implementation return the same list object (with different contents) for multiple calls to fetchall() (with potentially different preceding execute queries)? That would be a very unusual behavior in Python. Mutable objects are normally not shared between function/method calls. If they are shared, this needs to be documented. It is possible (and common) to share immutable objects, though. The DB-API uses the latter to implement am optimization in the .execute() method: if you pass in the same command string object in subsequent calls, the implementation can choose to reuse the previously prepared access plan. Some other examples (these are all True): dict(some_dict) is not some_dict list(some_list) is not some_list tuple(some_tuple) is some_tuple str(some_str) is some_str -- Marc-Andre Lemburg 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 our new mxODBC.Connect Python Database Interface 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 http://www.egenix.com/company/contact/