Shibboleth Developers

[giacomo tenaglia <>]

On Fri, Jan 18, 2008 at 10:07:27AM -0500, Scott Cantor wrote:
> > Yes, probably it's better also to change the update code. I'll work at
> > it.
> 
> You can pull the latest copy, I already did the work, now I just have to
> debug it all. I'm also having problems with the statement handles getting
> freed twice. Possibly because SQLPrepare is doing something bad when it
> fails on me.

Regarding updateRow, I think that you need to close the cursor
associated to the statement handle, because it was opened for the
SQLExecDirect at the beginning of the method, by using something like:

SQLFreeStmt(stmt, SQL_CLOSE);

I modified updateRow in a way equivalent to your and got this error (but
the application worked fine):

2008-01-18 15:07:58 ERROR XMLTooling.StorageService [2]: SQLPrepare failed 
(t=texts, c=NameID, 
)
2008-01-18 15:07:58 ERROR XMLTooling.StorageService [2]: ODBC Error: 
24000:1:0:[unixODBC][Driver Manager]Invalid cursor state
2008-01-18 15:07:58 ERROR Shibboleth.SessionCache [2]: error storing back 
mapping of NameID for logout: ODBC StorageService failed to update record.

Now I'll see if SQLFreeStmt will fix it.

> > I'm searching if this also apply to select statements, in order to see
> > if also readRow can cause problems.
> 
> I read long text using a loop the way you're supposed to, and that seems to
> work. It's statement prep that seems to be buggy.

Maybe it's the same cursor problem.

giacomo

-- 
giacomo tenaglia
Technical Student at CERN IT/DES-SIS
CNR Biblioteca d'Area di Bologna - http://biblio.bo.cnr.it
Phone +41 76 5003376 - 
sip: