Hello Kevin,

I'm wrapping all my client code in NamespaceAccessToken.begin() and 
NamespaceAccessToken.commit().  After the client code runs, the command-line mysql 
client confirms that the client did make the change.  So the transaction did finish.  
The problem is that the select statement in the JDBCDescriptorsStore doesn't register 
the change when selecting properties for that user.  I think it may have something to 
do with the JDBCDescriptorsStore using a single connection.  The really peculiar thing 
is that this problem goes away (i.e. the select statement in JDBCDescriptorsStore 
registers the properties change) when I revert back to non-transactional tables in 
MySQL.

I'm going to try the J2EEDescriptorsStore and dig around the MySQL and JDBC 
documentation.

Thanks for responding,

Tom

-----Original Message-----
From: Kevin Moran [mailto:[EMAIL PROTECTED]]
Sent: Wednesday, July 03, 2002 1:05 PM
To: Slide Users Mailing List
Subject: Re: Possible bug in JDBCDescriptorStore or MySQL driver?


Hi Tom,
    I don't know if this suggestion is of any
practical use to you, but have you confirmed that your
code is calling NamespaceAccessToken.begin() just
before it tries to update Slide and
NamespaceAccessToken.commit() immediately afterwards? 
You responded a while back to a problem I was having
with caching in JDBCDescriptorsStore; specifically
that it wasn't flushing out data to my Oracle
database.  What fixed my problem -- and I'm just
wondering if it's related to what you're describing --
is that I started calling begin() and commit().  I
didn't need to turn off caching in
AbstractServiceBase, just wrap my transaction in calls
to begin() and commit().  If I didn't call those
methods, I would see the code work for some DBs (e.g.,
HSql) and not others (Oracle).  I'm just wondering if
you're experiencing a similar caching problem.

Best,
-kevin


__________________________________________________
Do You Yahoo!?
Sign up for SBC Yahoo! Dial - First Month Free
http://sbc.yahoo.com

--
To unsubscribe, e-mail:   <mailto:[EMAIL PROTECTED]>
For additional commands, e-mail: <mailto:[EMAIL PROTECTED]>


--
To unsubscribe, e-mail:   <mailto:[EMAIL PROTECTED]>
For additional commands, e-mail: <mailto:[EMAIL PROTECTED]>

Reply via email to