<?xml version="1.0" encoding="UTF-8"?>
<rdf:RDF xmlns:rdf="http://www.w3.org/1999/02/22-rdf-syntax-ns#" xmlns="http://purl.org/rss/1.0/" xmlns:taxo="http://purl.org/rss/1.0/modules/taxonomy/" xmlns:dc="http://purl.org/dc/elements/1.1/" xmlns:syn="http://purl.org/rss/1.0/modules/syndication/" xmlns:admin="http://webns.net/mvcb/">
  <channel rdf:about="http://blog.gmane.org/gmane.comp.python.sqlobject">
    <title>gmane.comp.python.sqlobject</title>
    <link>http://blog.gmane.org/gmane.comp.python.sqlobject</link>
    <description/>
    <syn:updatePeriod>hourly</syn:updatePeriod>
    <syn:updateFrequency>1</syn:updateFrequency>
    <syn:updateBase>1901-01-01T00:00+00:00</syn:updateBase>
    <items>
      <rdf:Seq>
        <rdf:li rdf:resource="http://comments.gmane.org/gmane.comp.python.sqlobject/10713"/>
        <rdf:li rdf:resource="http://comments.gmane.org/gmane.comp.python.sqlobject/10709"/>
        <rdf:li rdf:resource="http://comments.gmane.org/gmane.comp.python.sqlobject/10707"/>
        <rdf:li rdf:resource="http://comments.gmane.org/gmane.comp.python.sqlobject/10704"/>
        <rdf:li rdf:resource="http://comments.gmane.org/gmane.comp.python.sqlobject/10700"/>
        <rdf:li rdf:resource="http://comments.gmane.org/gmane.comp.python.sqlobject/10697"/>
        <rdf:li rdf:resource="http://comments.gmane.org/gmane.comp.python.sqlobject/10695"/>
        <rdf:li rdf:resource="http://comments.gmane.org/gmane.comp.python.sqlobject/10693"/>
        <rdf:li rdf:resource="http://comments.gmane.org/gmane.comp.python.sqlobject/10692"/>
        <rdf:li rdf:resource="http://comments.gmane.org/gmane.comp.python.sqlobject/10689"/>
        <rdf:li rdf:resource="http://comments.gmane.org/gmane.comp.python.sqlobject/10685"/>
        <rdf:li rdf:resource="http://comments.gmane.org/gmane.comp.python.sqlobject/10684"/>
        <rdf:li rdf:resource="http://comments.gmane.org/gmane.comp.python.sqlobject/10680"/>
        <rdf:li rdf:resource="http://comments.gmane.org/gmane.comp.python.sqlobject/10658"/>
        <rdf:li rdf:resource="http://comments.gmane.org/gmane.comp.python.sqlobject/10656"/>
        <rdf:li rdf:resource="http://comments.gmane.org/gmane.comp.python.sqlobject/10646"/>
        <rdf:li rdf:resource="http://comments.gmane.org/gmane.comp.python.sqlobject/10645"/>
        <rdf:li rdf:resource="http://comments.gmane.org/gmane.comp.python.sqlobject/10644"/>
        <rdf:li rdf:resource="http://comments.gmane.org/gmane.comp.python.sqlobject/10632"/>
        <rdf:li rdf:resource="http://comments.gmane.org/gmane.comp.python.sqlobject/10631"/>
      </rdf:Seq>
    </items>
    <image rdf:resource="http://gmane.org/img/gmane-25t.png"/>
    <textinput rdf:resource=""/>
  </channel>
  <image rdf:about="http://gmane.org/img/gmane-25t.png">
    <title>Gmane</title>
    <url>http://gmane.org/img/gmane-25t.png</url>
    <link>http://gmane.org</link>
  </image>
  <item rdf:about="http://comments.gmane.org/gmane.comp.python.sqlobject/10713">
    <title>Example of SQLObject with web.py</title>
    <link>http://comments.gmane.org/gmane.comp.python.sqlobject/10713</link>
    <description>&lt;pre&gt;In case anyone needs help getting SQLObject caching to play well with
web.py (particularly with a multi-process implementation like a
typical WSGI setup), I've posted some example code for my solution on
GitHub:

https://github.com/RhubarbSin/example-sqlobject-webpy

------------------------------------------------------------------------------
Try New Relic Now &amp;amp; We'll Send You this Cool Shirt
New Relic is the only SaaS-based application performance monitoring service 
that delivers powerful full stack analytics. Optimize and monitor your
browser, app, &amp;amp; servers with just a few lines of code. Try New Relic
and get this awesome Nerd Life shirt! http://p.sf.net/sfu/newrelic_d2d_may
&lt;/pre&gt;</description>
    <dc:creator>Rhubarb Sin</dc:creator>
    <dc:date>2013-05-23T21:50:31</dc:date>
  </item>
  <item rdf:about="http://comments.gmane.org/gmane.comp.python.sqlobject/10709">
    <title>Cache Question</title>
    <link>http://comments.gmane.org/gmane.comp.python.sqlobject/10709</link>
    <description>&lt;pre&gt;I recently upgraded an application to the newest version of SQLObject
(previously it was using a version from early 2012).  This app was caching
SQLObject objects in Redis to avoid querying the database for commonly used
data.  But after upgrading, a bug fix released as part of SQLObject 1.2.3
broke the caching after running into unpickling errors.  With the new
version of SQLObject, it was refusing to unpickle objects that were already
in SQLObject's cache.  An example of the error message I received is below
(which comes from main.py:1692)

eg. "Cannot unpickle User row with id=1 - a different instance with the id
already exists in the cache"


I've already worked around this to keep my caching working but I was
wondering what the bug was that was fixed in 1.2.3 that necessitated this
change. The site only says "Fixed a bug in cache handling while
unpickling." which I found ironic because it broke caching in my app. Was
the bug a memory leak due to having multiple instances with the same ID in
memory or was there something else? I ask because my app never seemed to
experience any adverse side effects from taking advantage of this "bug".


Andrew
------------------------------------------------------------------------------
Try New Relic Now &amp;amp; We'll Send You this Cool Shirt
New Relic is the only SaaS-based application performance monitoring service 
that delivers powerful full stack analytics. Optimize and monitor your
browser, app, &amp;amp; servers with just a few lines of code. Try New Relic
and get this awesome Nerd Life shirt! http://p.sf.net/sfu/newrelic_d2d_may_______________________________________________
sqlobject-discuss mailing list
sqlobject-discuss&amp;lt; at &amp;gt;lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/sqlobject-discuss
&lt;/pre&gt;</description>
    <dc:creator>Andrew Trusty</dc:creator>
    <dc:date>2013-05-22T23:46:40</dc:date>
  </item>
  <item rdf:about="http://comments.gmane.org/gmane.comp.python.sqlobject/10707">
    <title>SQLObject 1.4.0</title>
    <link>http://comments.gmane.org/gmane.comp.python.sqlobject/10707</link>
    <description>&lt;pre&gt;Hello!

I'm pleased to announce version 1.4.0, the first stable release of branch
1.4 of SQLObject.


What's new in SQLObject
=======================

Features &amp;amp; Interface
--------------------

* Support for PostgreSQL 8.1 is dropped. The minimal supported version of
  PostgreSQL is 8.2 now.

* Optimization in PostgresConnection: use INSERT...RETURNING id
  to get the autoincremented id in one query instead of two
  (INSERT + SELECT id).

* Changed the way to get if the table has identity in MS SQL.

* NCHAR/NVARCHAR and N''-quoted strings for MS SQL.

Contributors for this release are Ken Lalonde and Andrew Ziem.


For a more complete list, please see the news:
http://sqlobject.org/News.html


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:
https://pypi.python.org/pypi/SQLObject/1.4.0

News and changes:
http://sqlobject.org/News.html

Oleg.
&lt;/pre&gt;</description>
    <dc:creator>Oleg Broytman</dc:creator>
    <dc:date>2013-05-18T10:06:13</dc:date>
  </item>
  <item rdf:about="http://comments.gmane.org/gmane.comp.python.sqlobject/10704">
    <title>SQLObject 1.4.0 beta1</title>
    <link>http://comments.gmane.org/gmane.comp.python.sqlobject/10704</link>
    <description>&lt;pre&gt;Hello!

I'm pleased to announce version 1.4.0b1, the first beta of the upcoming
release of branch 1.4 of SQLObject.


What's new in SQLObject
=======================

Features &amp;amp; Interface
--------------------

* Support for PostgreSQL 8.1 is dropped. The minimal supported version of
  PostgreSQL is 8.2 now.

* Optimization in PostgresConnection: use INSERT...RETURNING id
  to get the autoincremented id in one query instead of two
  (INSERT + SELECT id).

* Changed the way to get if the table has identity in MS SQL.

* NCHAR/NVARCHAR and N''-quoted strings for MS SQL.

Major contributor for this release is Andrew Ziem,

For a more complete list, please see the news:
http://sqlobject.org/News.html


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:
https://pypi.python.org/pypi/SQLObject/1.4.0b1dev-r4593

News and changes:
http://sqlobject.org/News.html

Oleg.
&lt;/pre&gt;</description>
    <dc:creator>Oleg Broytman</dc:creator>
    <dc:date>2013-05-04T16:01:47</dc:date>
  </item>
  <item rdf:about="http://comments.gmane.org/gmane.comp.python.sqlobject/10700">
    <title>MySQL: Commands out of sync;you can't run this command now</title>
    <link>http://comments.gmane.org/gmane.comp.python.sqlobject/10700</link>
    <description>&lt;pre&gt;Hello list,

I'm running into a problem when running a small web app in webpy with
sqlobject. The app is a REST interface which handles URLs such as:

GET /pkgdb/rest/srv4/7793c4a5ecd6494b25d475632618e44c/pkg-stats/ HTTP/1.1

and

PUT /releases/catalogs/unstable/i386/SunOS5.9/7793c4a5ecd6494b25d475632618e44c/
HTTP/1.1

When called with PUT, it does a few checks and inserts a row into a
table. When the application runs, it initially works for a minute or
two, but eventually gets into state in which it always fails with this
exception:

Traceback (most recent call last):
  File "/opt/csw/lib/python/site-packages/web/application.py", line
239, in process
    return self.handle()
  File "/opt/csw/lib/python/site-packages/web/application.py", line
230, in handle
    return self._delegate(fn, self.fvars, args)
  File "/opt/csw/lib/python/site-packages/web/application.py", line
420, in _delegate
    return handle_class(cls)
  File "/opt/csw/lib/python/site-packages/web/application.py", line
396, in handle_class
    return tocall(*args)
  File "/home/maciej/src/opencsw-gar/lib/web/releases_web.py", line 187, in PUT
    srv4 = models.Srv4FileStats.selectBy(md5_sum=md5_sum).getOne()
  File "/opt/csw/lib/python/site-packages/sqlobject/sresults.py", line
277, in getOne
    results = list(self)
  File "/opt/csw/lib/python/site-packages/sqlobject/sresults.py", line
181, in __iter__
    return iter(list(self.lazyIter()))
  File "/opt/csw/lib/python/site-packages/sqlobject/sresults.py", line
189, in lazyIter
    return conn.iterSelect(self)
  File "/opt/csw/lib/python/site-packages/sqlobject/dbconnection.py",
line 471, in iterSelect
    return select.IterationClass(self, self.getConnection(),
  File "/opt/csw/lib/python/site-packages/sqlobject/dbconnection.py",
line 336, in getConnection
    conn = self.makeConnection()
  File "/opt/csw/lib/python/site-packages/sqlobject/mysql/mysqlconnection.py",
line 71, in makeConnection
    conn.ping(True) # Attempt to reconnect. This setting is persistent.
ProgrammingError: (2014, "Commands out of sync; you can't run this command now")

This state persists until I restart the web server ‒ any query which
requires a connection to the database will fail with the same error,
visible as 500 Internal Server Error on the HTTP client side.

From reading the mysqlconnection.py source code, this function only
intends to throw SqlObject exceptions, and not exceptions specific to
the database engine. I'm guessing that it isn't expected that
conn.ping() could throw an exception?

The failing function in my app starts here:
https://sourceforge.net/apps/trac/gar/browser/csw/mgar/gar/v2/lib/web/releases_web.py#L143

Does it look like a problem with my application, or does it look like
something that should be handled on the SqlObject side? Or should I
check for the state of the connection at the start of this function?

Versions of software I'm using:
SqlObject 1.3.2
Python 2.6.8
MySQL Server 5.5.30
MySQLdb python module 1.2.3
Apache 2.2.22
Oracle Solaris 10 9/10 s10x_u9wos_14a X86

Maciej

------------------------------------------------------------------------------
Precog is a next-generation analytics platform capable of advanced
analytics on semi-structured data. The platform includes APIs for building
apps and a phenomenal toolset for data science. Developers can use
our toolset for easy data analysis &amp;amp; visualization. Get a free account!
http://www2.precog.com/precogplatform/slashdotnewsletter
_______________________________________________
sqlobject-discuss mailing list
sqlobject-discuss&amp;lt; at &amp;gt;lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/sqlobject-discuss
&lt;/pre&gt;</description>
    <dc:creator>Maciej (Matchek) Bliziński</dc:creator>
    <dc:date>2013-04-16T09:52:29</dc:date>
  </item>
  <item rdf:about="http://comments.gmane.org/gmane.comp.python.sqlobject/10697">
    <title>specifying schema for mssql</title>
    <link>http://comments.gmane.org/gmane.comp.python.sqlobject/10697</link>
    <description>&lt;pre&gt;With SQLObject 1.3.2 and mssql backend, how do you specify the schema
equivalent to the command 'use foo'?  I want to use a schema that is
neither 'dbo' not the default for the user.  I don't see how to do it
using the URI after glancing over the documentation and code.


Andrew

------------------------------------------------------------------------------
Everyone hates slow websites. So do we.
Make your web apps faster with AppDynamics
Download AppDynamics Lite for free today:
http://p.sf.net/sfu/appdyn_d2d_jan
&lt;/pre&gt;</description>
    <dc:creator>Andrew Z</dc:creator>
    <dc:date>2013-02-04T21:20:59</dc:date>
  </item>
  <item rdf:about="http://comments.gmane.org/gmane.comp.python.sqlobject/10695">
    <title>running tests</title>
    <link>http://comments.gmane.org/gmane.comp.python.sqlobject/10695</link>
    <description>&lt;pre&gt;I read http://www.sqlobject.org/DeveloperGuide.html#testing and am
still unclear on exactly how to run a test.  Sorry, this may be a
basic question, but I hope the Developer Guide could be more explicit.

After installing py.test, I basically did this:

$ svn co http://svn.colorstudy.com/SQLObject/trunk SQLObject
$ cd SQLObject
$ python sqlobject/tests/test_unicode.py  -D sqlite:///tmp/foo.db

However:
Traceback (most recent call last):
  File "sqlobject/tests/test_unicode.py", line 1, in &amp;lt;module&amp;gt;
    from sqlobject import *
ImportError: No module named sqlobject

I also tried something like and got basically the same error

$ pytest sqlobject/tests/test_unicode.py  -D sqlite:///tmp/foo.db




Andrew

------------------------------------------------------------------------------
Everyone hates slow websites. So do we.
Make your web apps faster with AppDynamics
Download AppDynamics Lite for free today:
http://p.sf.net/sfu/appdyn_d2d_jan
&lt;/pre&gt;</description>
    <dc:creator>Andrew Z</dc:creator>
    <dc:date>2013-02-03T02:44:23</dc:date>
  </item>
  <item rdf:about="http://comments.gmane.org/gmane.comp.python.sqlobject/10693">
    <title>INSERT INTO and cursor</title>
    <link>http://comments.gmane.org/gmane.comp.python.sqlobject/10693</link>
    <description>&lt;pre&gt;Any good reason why this code should fail to insert while the underlying query in mysql shell works?
cursor=cbx.conn.cursor()
cursor.execute(u"INSERT INTO notes (message, author) VALUES ('test', 'test');")
Furthermore, this fails silently, so no error to give me a clue.
Selects still work as expected, but somehow, all the old legacy code I've got that uses statements of the above type have stopped working.
As always, thanks much for the advice,
--Markos Kapes


------------------------------------------------------------------------------
Master Visual Studio, SharePoint, SQL, ASP.NET, C# 2012, HTML5, CSS,
MVC, Windows 8 Apps, JavaScript and much more. Keep your skills current
with LearnDevNow - 3,200 step-by-step video tutorials by Microsoft
MVPs and experts. ON SALE this month only -- learn more at:
http://p.sf.net/sfu/learnnow-d2d
&lt;/pre&gt;</description>
    <dc:creator>Markos Kapes</dc:creator>
    <dc:date>2013-01-22T20:21:06</dc:date>
  </item>
  <item rdf:about="http://comments.gmane.org/gmane.comp.python.sqlobject/10692">
    <title>SourceForge's Allura</title>
    <link>http://comments.gmane.org/gmane.comp.python.sqlobject/10692</link>
    <description>&lt;pre&gt;Hello!

   SourceForge insisted on upgrading registered projects to their new
backend called Allura, so I allowed them to upgrade the project.
See http://sourceforge.net/projects/sqlobject/
   The most notable changes are:
administrative interface: https://sourceforge.net/p/sqlobject/admin/
tickets: http://sourceforge.net/p/sqlobject/_list/tickets
and wiki: http://sourceforge.net/p/sqlobject/wiki/Home/
   Not sure how to use the new wiki to the benefits of the community.

Oleg.
&lt;/pre&gt;</description>
    <dc:creator>Oleg Broytman</dc:creator>
    <dc:date>2013-01-18T20:46:15</dc:date>
  </item>
  <item rdf:about="http://comments.gmane.org/gmane.comp.python.sqlobject/10689">
    <title>passwords hashed using pgcrypto (in the database)</title>
    <link>http://comments.gmane.org/gmane.comp.python.sqlobject/10689</link>
    <description>&lt;pre&gt;Hi,

I'm learning SQLObject - checking if we could use it on our projects, 
and I got stuck at hashing passwords inside the database.

Imagine a simple table with info about users:

CREATE TABLE users (
     id       INT PRIMARY KEY,
     login    TEXT NOT NULL UNIQUE,
     pwdhash  TEXT NOT NULL
)

where "pwdhash" is a hashed password. We're using PostgreSQL and we 
usually handle this inside the database using a pgcrypto module, that 
provides various hash/crypto functions. An insert into the table then 
looks like this

     INSERT INTO users VALUES (1, 'login', crypt('mypassword', 
gen_salt('bf')))

which generates a salt, computes the hash and stores that into a single 
text column (salt+hash). The authentication then looks like this:

     SELECT id, login FROM users WHERE login = 'login' AND pwdhash = 
crypt('mypassword', pwdhash)

which reuses the salt stored in the column.

I'm investigating if we could do this with SQLObject, but it seems to 
me the answer is 'no'. I see it's possible to define magic attributes, 
but that's not enough as I need to rewrite the SQL (to add the calls to 
the crypt/gen_salt functions). I've done similar evaluations with 
SQLAlchemy and it supports 'hybrid values' and 'type decorators' to do 
this.

Is it possible to do something similar in SQLObject or do I have to 
move the functionality to the application level?

regards
Tomas

------------------------------------------------------------------------------
Master Visual Studio, SharePoint, SQL, ASP.NET, C# 2012, HTML5, CSS,
MVC, Windows 8 Apps, JavaScript and much more. Keep your skills current
with LearnDevNow - 3,200 step-by-step video tutorials by Microsoft
MVPs and experts. ON SALE this month only -- learn more at:
http://p.sf.net/sfu/learnmore_123012
&lt;/pre&gt;</description>
    <dc:creator>Tomas Vondra</dc:creator>
    <dc:date>2012-12-30T20:46:00</dc:date>
  </item>
  <item rdf:about="http://comments.gmane.org/gmane.comp.python.sqlobject/10685">
    <title>freezes with multi-threading ?</title>
    <link>http://comments.gmane.org/gmane.comp.python.sqlobject/10685</link>
    <description>&lt;pre&gt;Hi

I'm using sqlobjects with webware for python on my website in production
since 2007.
Since about one year ago (maybe more...), from time to time (about every
week/month), the python process completely freezes under high load.

I upgraded to sqlobject 1.3.2 with latest mysqlDB, and still have the
problem.

All signals are ignored.  it can only be killed with a kill -9.
strace show the python process is stuck in a futex kernel call.

Recently, I tried to gdb the frozen python process: All threads are waiting
for a semaphore, except one, that is waiting probably for a mysql response,
in the _mysql.so object of python-mysql.

unfortunately, the gdb pystack macro doesn't work for me. So I can't get
the python stack. It seems that gdb cpu gets all cpu dureing a very very
long time. I haven't waited enough...

All threads waiting for a semaphore. I don't know if it is the python GIL
or another mysql or sqlobject related lock. The GIL would explain that
signals are ineffective.


#0  0x00110416 in __kernel_vsyscall ()
#1  0x005a8865 in sem_wait&amp;lt; at &amp;gt;&amp;lt; at &amp;gt;GLIBC_2.1 () from /lib/libpthread.so.0


#2  0x0067eafb in PyThread_acquire_lock (lock=0x8dc7028, waitflag=1) at
Python/thread_pthread.h:349
#3  0x00682eb8 in lock_PyThread_acquire_lock (self=0x854c430,
args=0xb7f3102c) at Modules/threadmodule.c:46

#4  0x0060d7ed in PyCFunction_Call (func=0x8eeb0ec, arg=0xb7f3102c, kw=0x0)
at Objects/methodobject.c:108
#5  0x0065ac72 in PyEval_EvalFrameEx (f=0x93d7ff4, throwflag=0) at
Python/ceval.c:3564

#6  0x00659fcd in PyEval_EvalFrameEx (f=0x8e2e53c, throwflag=0) at
Python/ceval.c:3650
#7  0x0065b6bf in PyEval_EvalCodeEx (co=0x8922410, globals=0x891e3e4,
locals=0x0, args=0x9cfa2dc, argcount=1, kws=0x9cfa2e0,

    kwcount=0, defs=0x891af18, defcount=1, closure=0x0) at
Python/ceval.c:2831
#8  0x00659844 in PyEval_EvalFrameEx (f=0x9cfa12c, throwflag=0) at
Python/ceval.c:3660

#9  0x00659fcd in PyEval_EvalFrameEx (f=0x8dccfa4, throwflag=0) at
Python/ceval.c:3650
#10 0x0065b6bf in PyEval_EvalCodeEx (co=0x87ad848, globals=0x87a924c,
locals=0x0, args=0x8d43818, argcount=2, kws=0x0,
....

except one thread: ( I still have to check all 25 threads...)
#0  0x00110416 in __kernel_vsyscall ()
#1  0x005a952b in read () from /lib/libpthread.so.0


#2  0x00295338 in vio_read () from /usr/lib/mysql/libmysqlclient_r.so.15
#3  0x002953ae in vio_read_buff () from
/usr/lib/mysql/libmysqlclient_r.so.15


#4  0x002967ab in ?? () from /usr/lib/mysql/libmysqlclient_r.so.15
#5  0x00296b9b in my_net_read () from /usr/lib/mysql/libmysqlclient_r.so.15


#6  0x0028fe39 in cli_safe_read () from
/usr/lib/mysql/libmysqlclient_r.so.15
#7  0x00290c35 in ?? () from /usr/lib/mysql/libmysqlclient_r.so.15


#8  0x0028f1e4 in mysql_real_query () from
/usr/lib/mysql/libmysqlclient_r.so.15
#9  0x00243f53 in _mysql_ConnectionObject_query (self=0x941160c,
args=0x978138c) at _mysql.c:2008

#10 0x0060d7ed in PyCFunction_Call (func=0x9c300cc, arg=0x978138c, kw=0x0)
at Objects/methodobject.c:108
#11 0x0065ac72 in PyEval_EvalFrameEx (f=0x940d924, throwflag=0) at
Python/ceval.c:3564

#12 0x00659fcd in PyEval_EvalFrameEx (f=0x9b12c64, throwflag=0) at
Python/ceval.c:3650
#13 0x00659fcd in PyEval_EvalFrameEx (f=0x9b7cdf4, throwflag=0) at
Python/ceval.c:3650

#14 0x0065b6bf in PyEval_EvalCodeEx (co=0x8d2ead0, globals=0x8d304f4,
locals=0x0, args=0x9240fec, argcount=2, kws=0x9240ff4,
    kwcount=0, defs=0x8d37358, defcount=1, closure=0x0) at
Python/ceval.c:2831
...

Note: I also get some "ProgrammingError: Commands out of sync; you can't
run this command now" errors from time to time.

This is why I'm suspecting a wrong connection management between my threads.

Could it be related to the fact that I'm using the sqlHub.processConnection
feature of SqlObject?
Reading the code, I don't understand the call path from dbConnection to the
SqlHub.

How is the connection pool managed?
Is it thread safe?

Thanks in advance for your support

Best regards
------------------------------------------------------------------------------
LogMeIn Rescue: Anywhere, Anytime Remote support for IT. Free Trial
Remotely access PCs and mobile devices and provide instant support
Improve your efficiency, and focus on delivering more value-add services
Discover what IT Professionals Know. Rescue delivers
http://p.sf.net/sfu/logmein_12329d2d_______________________________________________
sqlobject-discuss mailing list
sqlobject-discuss&amp;lt; at &amp;gt;lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/sqlobject-discuss
&lt;/pre&gt;</description>
    <dc:creator>Sophana K</dc:creator>
    <dc:date>2012-12-04T12:02:52</dc:date>
  </item>
  <item rdf:about="http://comments.gmane.org/gmane.comp.python.sqlobject/10684">
    <title>SQLObject 1.3.2 and 1.2.4</title>
    <link>http://comments.gmane.org/gmane.comp.python.sqlobject/10684</link>
    <description>&lt;pre&gt;Hello!

I'm pleased to announce versions 1.3 2 and 1.2.4, minor bugfix releases
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://pypi.python.org/pypi/SQLObject/1.3.2
http://pypi.python.org/pypi/SQLObject/1.2.4

News and changes:
http://sqlobject.org/News.html


What's New
==========

* Fixed a bug in sqlbuilder.Select.filter - removed comparison with
  SQLTrueClause.

* Neil Muller fixed a number of tests.

For a more complete list, please see the news:
http://sqlobject.org/News.html

Oleg.
&lt;/pre&gt;</description>
    <dc:creator>Oleg Broytman</dc:creator>
    <dc:date>2012-10-20T09:25:09</dc:date>
  </item>
  <item rdf:about="http://comments.gmane.org/gmane.comp.python.sqlobject/10680">
    <title>Slow/Large cache</title>
    <link>http://comments.gmane.org/gmane.comp.python.sqlobject/10680</link>
    <description>&lt;pre&gt;Hi

We have a RPC server which CPU usage increases over time, after a week
it will max out one core.

is spend in:

file "/usr/lib/pymodules/python2.6/turbogears/database.py", line 275, in
commit
    self.threadingLocal.connection.commit()
  File
"/usr/local/lib/python2.6/dist-packages/SQLObject-1.3.1-py2.6.egg/sqlobject/dbconnection.py",
line 802, in commit
    subCaches = [(sub[0], sub[1].allIDs()) for sub in
self.cache.allSubCachesByClassNames().items()]
  File
"/usr/local/lib/python2.6/dist-packages/SQLObject-1.3.1-py2.6.egg/sqlobject/cache.py",
line 263, in allIDs
    for id, value in self.expiredCache.items():

Currently the overhead for each commit and rollback is around 2-3 seconds.

Almost all of our tables have caching disabled via 'sqlmeta: cacheValues
= False'.

No state is kept in memory between requests and we typically write
significantly more rows to the DB than what is read, ie. A lot of writes
which are not read often and a few hundred rows which are read often and
that can be changed by other processes.

Does anyone have a suggestion on how to mitigate or further debug the
problem?

Regards
Gert Burger

------------------------------------------------------------------------------
Live Security Virtual Conference
Exclusive live event will cover all the ways today's security and 
threat landscape has changed and how IT managers can respond. Discussions 
will include endpoint security, mobile security and the latest in malware 
threats. http://www.accelacomm.com/jaw/sfrnl04242012/114/50122263/
&lt;/pre&gt;</description>
    <dc:creator>Gert Burger</dc:creator>
    <dc:date>2012-08-27T08:32:50</dc:date>
  </item>
  <item rdf:about="http://comments.gmane.org/gmane.comp.python.sqlobject/10658">
    <title>ViewSQLObject ID's</title>
    <link>http://comments.gmane.org/gmane.comp.python.sqlobject/10658</link>
    <description>&lt;pre&gt;Hi,

I decided to try the ViewSQLObject class in an attempt to speed up my 
system by letting the server do some of the table joins in single queries,
instead of joining in python on the client side.

But I get stuck at the id.  I assume that ViewSQLObject objects
need an immutable and unique ID (is that right?).  All the examples 
I have seen just copies the ID from one of the constituent SQLObject-s. 
In my case I am joining on a many-to-many relationship, so I assume
I need to aggregate multiple ID fields into one.  Can anyone offer 
a quick example showing how this could be done?

TIA
&lt;/pre&gt;</description>
    <dc:creator>Hans Georg Schaathun</dc:creator>
    <dc:date>2012-06-21T07:25:03</dc:date>
  </item>
  <item rdf:about="http://comments.gmane.org/gmane.comp.python.sqlobject/10656">
    <title>Vacation</title>
    <link>http://comments.gmane.org/gmane.comp.python.sqlobject/10656</link>
    <description>&lt;pre&gt;I am offline till June 20.

Oleg.
&lt;/pre&gt;</description>
    <dc:creator>Oleg Broytman</dc:creator>
    <dc:date>2012-06-04T10:25:42</dc:date>
  </item>
  <item rdf:about="http://comments.gmane.org/gmane.comp.python.sqlobject/10646">
    <title>PostgreSQL warnings filling up the logs with PickleCol</title>
    <link>http://comments.gmane.org/gmane.comp.python.sqlobject/10646</link>
    <description>&lt;pre&gt;Hi all,

I am getting a warning in the Postgres log for every time a PickleCol is 
written to the database. Since my app uses a pickled col extensively in one of 
the more frequently used tables, the Postgres logs are filled with these 
warnings:

----------------------
WARNING:  nonstandard use of \\ in a string literal at character 50
HINT:  Use the escape string syntax for backslashes, e.g., E'\\'.
----------------------

This is with SQLObject v1.3.0, but it has been there from at least v0.12.4 
from which I am upgrading to 1.3.0 now.

PostgresSQL is v8.4.11 on Debian Squeeze.

An example test case to illustrate the problem is inline below.

Any help on how to solve this so I can get my log files cleaned up, in order 
to debug another connection problem, would be greatly appreciated.


Thanks,
 Tom



-------------------------------
from sqlobject import *

db = dict(user='tomc',
          passw='',
          host='',
          dbname='tomc')
dbURI = "postgres://%(user)s:%(passw)s&amp;lt; at &amp;gt;%(host)s/%(dbname)s" % db

connection = connectionForURI(dbURI)
sqlhub.processConnection = connection

# Default pickled data - try to use as many object types as possible for tests
defaultConfig = dict(ports=2,
                     remote=False,
                     logger=None,
                     services=['web', 'database'],
                     dns=dict(hostname=None,
                              domain='foo.bar')
                     )

# Define the sampe table with a pickled column
class Server(SQLObject):
    name = StringCol()
    config = PickleCol(notNull=True, default=defaultConfig)

# Drop and create table
Server.dropTable(ifExists=True)
Server.createTable()

# Turn on SQLObejct debugging
connection.debug=True

# Add test records while tailing the postgresql log files
s1 = Server(name='foo')
-------------------------------


------------------------------------------------------------------------------
Live Security Virtual Conference
Exclusive live event will cover all the ways today's security and 
threat landscape has changed and how IT managers can respond. Discussions 
will include endpoint security, mobile security and the latest in malware 
threats. http://www.accelacomm.com/jaw/sfrnl04242012/114/50122263/
&lt;/pre&gt;</description>
    <dc:creator>Tom Coetser</dc:creator>
    <dc:date>2012-05-31T06:08:42</dc:date>
  </item>
  <item rdf:about="http://comments.gmane.org/gmane.comp.python.sqlobject/10645">
    <title>SQLObject 1.3.1</title>
    <link>http://comments.gmane.org/gmane.comp.python.sqlobject/10645</link>
    <description>&lt;pre&gt;Hello!

I'm pleased to announce version 1.3.1, the first bug-fix release of branch
1.3 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://pypi.python.org/pypi/SQLObject/1.3.1

News and changes:
http://sqlobject.org/News.html


What's New
==========

* Fixed a minor bug in PostgreSQL introspection: VIEWs don't have
  PRIMARY KEYs - use sqlmeta.idName as the key.

* Fixed a bug in cache handling while unpickling.

For a more complete list, please see the news:
http://sqlobject.org/News.html

Oleg.
&lt;/pre&gt;</description>
    <dc:creator>Oleg Broytman</dc:creator>
    <dc:date>2012-05-25T19:43:50</dc:date>
  </item>
  <item rdf:about="http://comments.gmane.org/gmane.comp.python.sqlobject/10644">
    <title>SQLObject 1.2.3</title>
    <link>http://comments.gmane.org/gmane.comp.python.sqlobject/10644</link>
    <description>&lt;pre&gt;Hello!

I'm pleased to announce version 1.2.3, a bugfix release of branch
1.2 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://pypi.python.org/pypi/SQLObject/1.2.3

News and changes:
http://sqlobject.org/News.html


What's New
==========

* Fixed a minor bug in PostgreSQL introspection: VIEWs don't have
  PRIMARY KEYs - use sqlmeta.idName as the key.

* Fixed a bug in cache handling while unpickling.

For a more complete list, please see the news:
http://sqlobject.org/News.html

Oleg.
&lt;/pre&gt;</description>
    <dc:creator>Oleg Broytman</dc:creator>
    <dc:date>2012-05-25T19:43:33</dc:date>
  </item>
  <item rdf:about="http://comments.gmane.org/gmane.comp.python.sqlobject/10632">
    <title>Select Single Random Record</title>
    <link>http://comments.gmane.org/gmane.comp.python.sqlobject/10632</link>
    <description>&lt;pre&gt;What is the best way to select a single random record from a table and
falls within the "where" criteria i have defined? I don't want to return a
huge result set each time and then pick a random one, as the database is
located outside of my network and accessed over the internet.


&lt;/pre&gt;</description>
    <dc:creator>Adam Berg</dc:creator>
    <dc:date>2012-04-18T16:30:10</dc:date>
  </item>
  <item rdf:about="http://comments.gmane.org/gmane.comp.python.sqlobject/10631">
    <title>connectionForURI is not defined</title>
    <link>http://comments.gmane.org/gmane.comp.python.sqlobject/10631</link>
    <description>&lt;pre&gt;Everything was running fine last night.  Came in this morning and my 
test system is acting weird.  I'm doing my best to find the answer but 
in the meantime, if someone knows what this is, I could use a bit of help.

Thanks,

Glenn


Today:
 &amp;gt;&amp;gt;&amp;gt; from sqlobject import *
Traceback (most recent call last):
   File "&amp;lt;stdin&amp;gt;", line 1, in &amp;lt;module&amp;gt;
   File "sqlobject.py", line 8, in &amp;lt;module&amp;gt;
     conn = connectionForURI(connection_string)
NameError: name 'connectionForURI' is not defined


System Setup:

Python 2.7.2 on Windows XP
Path = c:\python27;c:\python27\Scripts;C:\Python27\Lib\site-packages


Installed pymssql
Installed SQLObject 1.3.0




 &amp;gt;easy_install -U SQLObject
Searching for SQLObject
Reading http://pypi.python.org/simple/SQLObject/
Reading http://sqlobject.org
Reading http://sqlobject.org/
Reading http://sqlobject.org/devel/
Best match: SQLObject 1.3.0
Downloading 
http://pypi.python.org/packages/2.7/S/SQLObject/SQLObject-1.3.0-py2.7.egg#md5=42e649b0c1
08b75a1bec8f22e84270fa
Processing SQLObject-1.3.0-py2.7.egg
creating c:\python27\lib\site-packages\SQLObject-1.3.0-py2.7.egg
Extracting SQLObject-1.3.0-py2.7.egg to c:\python27\lib\site-packages
Adding SQLObject 1.3.0 to easy-install.pth file
Installing sqlobject-admin script to c:\python27\Scripts
Installing sqlobject-convertOldURI script to c:\python27\Scripts

Installed c:\python27\lib\site-packages\sqlobject-1.3.0-py2.7.egg
Processing dependencies for SQLObject
Finished processing dependencies for SQLObject







------------------------------------------------------------------------------
For Developers, A Lot Can Happen In A Second.
Boundary is the first to Know...and Tell You.
Monitor Your Applications in Ultra-Fine Resolution. Try it FREE!
http://p.sf.net/sfu/Boundary-d2dvs2
&lt;/pre&gt;</description>
    <dc:creator>Glenn Rutkowski</dc:creator>
    <dc:date>2012-04-13T16:01:31</dc:date>
  </item>
  <item rdf:about="http://comments.gmane.org/gmane.comp.python.sqlobject/10625">
    <title>SQLObject 1.3.0</title>
    <link>http://comments.gmane.org/gmane.comp.python.sqlobject/10625</link>
    <description>&lt;pre&gt;Hello!

I'm pleased to announce version 1.3.0, the first stable release of branch
1.3 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://pypi.python.org/pypi/SQLObject/1.3.0

News and changes:
http://sqlobject.org/News.html


What's New
==========

Features &amp;amp; Interface
--------------------

* PostgresConnection performs translation of exceptions to standard
  SQLObject's hierarchy of exceptions.

* Major update of FirebirdConnection: introspection was completely
  rewritten and extended; ``charset`` was renamed to ``dbEncoding``;
  a longstanding bug was fixed - pass port to connect().

For a more complete list, please see the news:
http://sqlobject.org/News.html

Oleg.
&lt;/pre&gt;</description>
    <dc:creator>Oleg Broytman</dc:creator>
    <dc:date>2012-03-31T11:42:38</dc:date>
  </item>
  <textinput rdf:about="http://search.gmane.org/?group=$group=gmane.comp.python.sqlobject">
    <title>Search Engine</title>
    <description>Search the mailing list at Gmane</description>
    <name>query</name>
    <link>http://search.gmane.org/?group=$group=gmane.comp.python.sqlobject</link>
  </textinput>
</rdf:RDF>
