[Zope-dev] SQLAlias Memory Leak?

[Dyon Balding]

OK, I've put this into the Collector.  I'm intrigued as to what
the operating procedure is with the Collector though - there appear
to be a large number of Pending jobs.  Does that mean that Digital
Creations haven't even looked at them, or that they just haven't
done anything about them?

http://classic.zope.org:8080/Collector/1772/view

This is causing big problems with our site, and we need to resolve
it pretty desperately.  I guess the another solution would be to ensure
that all calls to SQL columns are the same case as in the database,
but with around 500 ZSQLMethods - that is a daunting task.

-d

On Wed, Dec 06, 2000 at 03:08:33PM -0800, Jon Prettyman wrote:
> I've seen this as well under DCOracle.
> 
> -jon
> 
> Dyon Balding <dyon@devcoder.com.au> writes:
> 
> > OK, I've had more of a hack at this, and I've narrowed the problem
> > down a little.
> > 
> > It appears that any access to an SQLAlias object causes it to not
> > be correctly released.  The SQLAlias objects means that you can
> > access column names using a different case to how they are stored
> > in the database.
> > 
> > For example, we store users in a users table in the database, with
> > column names like USERNAME, but they are accessed with:
> > <dtml-var username>, this causes the SQLAlias objects to stick around.
> > 
> > One solution to our problem is to just do a <dtml-var USERNAME>
> > instead.  However that doesn't solve the problem with this
> > "feature" of being able to call it with a different case.
> > 
> > This is a fairly easy bug to reproduce, on my setup at least :).
> > I have tested it with ZSQLRelay and ZODBDA both talking to SQLServer,
> > and with ZPyGreSQLDA talking to PostgreSQL.
> > 
> > I would appreciate it if someone else can reproduce the bug,
> > and I'll put it in the Collector I guess.
> > 
> > thanks
> > -d
> > 

-- 
Dyon Balding <dyon@devcoder.com.au>