The leaking SQLAlias I see is coming from:
Shared.DC.ZRDB.Results
I'm going to try the same type of fix in there and see what happens.
-jon
"Brian Lloyd" [EMAIL PROTECTED] writes:
oops - I sent that before I had my coffee. I should
have attached the checkin version, not the broken
one
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?
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?
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.
I've seen this as well under DCOracle.
-jon
Dyon Balding [EMAIL PROTECTED] 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
